I tried to ease the administration of dedicated servers, and enhance the player experience with autohosts. However, since people are really used to Springie, I had to implement wrappers for main Springie commands that had been replaced in Spads.
These wrapped commands aren't the best way to use Spads, but I understand one doesn't want to read through all the help messages just to start a game. That's why I wrote this very minimal list of tips:
- You shouldn't need to use "!balance", "!fixcolors" and "!autolock" commands with Spads (they are just here so that people don't think the autohost lacks these functionalities...). Instead, you just have to tell Spads what is the structure of the battle you want to play (only if it changed since last game). For instance if you want to play a 4v4v4 game, you can type:Then, if configured so, Spads will automatically manage the battle for this structure: balance, fixcolors, autolock, autospec, even ring or pvMsg according to user's preferences (per-user configurable ring spam protection)...
Code: Select all
!set nbTeams 3 !set teamSize 4
- There is no !voteexit, !voteforce, !votekick... command in Spads, just a !callvote command that takes any command as parameter, so any command can be voted
- In the same way, there is no !listbans, !listmaps, !listpresets... command in Spads, just a !list command (for instance: !list maps, !list bans, !list users...)
- You don't need to use the !callvote command explicitly, you can call the requested command directly, and Spads will automatically call a vote if needed
- When you call a vote, you don't need to vote just after, Spads considers you already voted for the command since you started the vote
- Use "!list presets" for available presets, and "!list settings", "!list hSettings", and "!list bSettings" for various tunable parameters lists