Commands and Permissions
Syntax: /mw …
Aliases: /missilewars
Permission: -
This is the main command of the MissileWars plugin. Without specifying any arguments, it displays the available commands based on the user's permissions.
Syntax: /mw mapmenu
Aliases: votegui
Permission: mw.mapmenu
This command can be used to open the Map-Vote Menu. This is an inventory menu that displays the available arenas there are can be voted for and allows executing the corresponding Map-Vote command through item interaction.
Note: The menu can be partially reconfigured. All details can be found here.
Syntax: /mw vote <arena>
Aliases: -
Permission: mw.vote
This command can be used to vote for the desired arena-map in the game-phase "Lobby", if more than one map is available for the game and the map_choose_procedure is set to MAPVOTING in the arena config. If the command is used multiple times in the same game, the previous vote is overwritten.
Syntax: /mw teammenu
Aliases: changegui
Permission:
-
mw.teammenu- Permission to open the menu -
mw.change.team.player- Permission to see the two "player-team" items -
mw.change.team.spectator- Permission to see the "spectator-team" item
This command can be used to open the Team-Selection Menu. This is an inventory menu that displays the available teams (Team 1, Team 2 and Spectator) and allows executing the corresponding Team-Change command through item interaction.
Note: The menu can be partially reconfigured. All details can be found here.
Syntax: /mw change <1|2|spec>
Aliases: switch, team
Permission:
-
mw.change.use- Basic Permission to use the command -
mw.change.team.player- Permission to switch in one of the "player-teams" -
mw.change.team.spectator- Permission to switch in the "spectator-team"
This command can be used to change the team. This is possible in the game-phase "Lobby" and (if the arena setting teamchange_ongoing_game is enabled) in the game-phase "Ingame". The anti-spam interval (antispam_intervall.team_change_command) from the config.yml is used here so that the command cannot be used too quickly in succession. In the game-phase "Ingame", with executing the command the plugin checks whether the requested team-change is fair (in the lobby, the game simply does not start in this case). The maximum values for the game and the teams are also validated.
Syntax: /mw quit
Aliases: leave
Permission: mw.quit
You can use this command to leave a game if you are in one. It doesn't matter whether you are currently in a player team or watching in a spectator team. This command teleports you to the configured fallback_spawn position.
Warn: The stats system is outdated and will be reworked in the future.
Syntax: /mw stats [from] [arena]
Aliases: -
Permission: mw.stats
Shows stats.
Syntax: /mw stats recommendations [from] [arena]
Aliases: -
Permission: mw.stats.recommendations
Shows recommendations.
Syntax: /mw stats players [from] [arena]
Aliases: -
Permission: mw.stats.players
Shows player list.
Syntax: /mw stats list [from] [arena]
Aliases: -
Permission: mw.stats.list
Lists history of games.
Syntax: /mw listgames
Aliases: list, games
Permission: mw.listgames
This command lists the currently running games and shows important basic information about it.
Syntax: /mw move <player> <1|2|spec>
Aliases: -
Permission: mw.move
This command can be used to move a specific player to another team. This is possible in the game-phase "Lobby" and "Ingame". Unlike the normal Team-Change command, some conditions are not checked here, as it is a staff command and should only be used if necessary. The command can only be executed for players who are online and in the corresponding MissileWars game. In addition, the target player must not be alone in his team.
Syntax: /mw paste <missile> [flags, e.g. '-tempblock:true']
Aliases: -
Permission: mw.paste
This command can be used to manually paste a Missile schematic. The command can only be executed in one of the Arena Areas and only allows the Missile schematics that have been configured for this arena. The Missiles are pasted in the direction of player-view and with the corresponding down and dist offset-setting from the arena configuration located in /MissileWars/arenas/. The paste also displays information about the Updater‐Block in the chat.
Warn: The command does not execute a normal Player-WorldEdit command and therefore cannot currently be undone with "//undo". The command should therefore be used with care.
| Flag-Argument | Value-Type | Description | Recommendation for WorldEdit | Recommendation for FAWE | Default value in the config.yml
|
|---|---|---|---|---|---|
tempblock |
Boolean | Is there a Updater-Block in the schematic that should be used and replaced? The block is only replaced if the option is activated. |
false if not Updater-Block is inclused in the schematic. If the schematic already contains an Updater-Block, this option must set to true so that the block does not remain at the paste-location. |
true (FAWE paste asynchronously. Without the Updater-Block, the Missile does not fly off. The schematics needs an Updater-Block at the right position.) |
true |
tempblock_material |
Bukkit Material name | What is the bukkit material of this block in the schematic? | All solid block materials usable, if it's not a part of an normal Missile construction. | All solid block materials usable, if it's not a part of an normal Missile construction. | NOTE_BLOCK |
tempblock_delay |
Integer | After how many ticks should the block be removed? |
4 - If the value is too small, the Updater-Block remain at the paste-location. If the value is too large, this can lead to double circuit updates or the Updater-Block already flies with the Missile and will no longer be removed. |
0 - Higher values are possible, but do not appear to be necessary in most cases, as FAWE works asynchronously. |
0 |
tempblock_radius |
Integer | Each schematic has an Origin-Block from which everything is calculated. How large should the radius be around this Origin-Block to search for one or more Updater-Blocks? | Dependend on the schematic. | Dependend on the schematic. | 8 |
Syntax: /mw start [lobby]
Aliases: -
Permission: mw.start
This command sets the Lobby Wait-Time (based on the lobby_time setting from the lobby configuration) to "0" sec., so that the map vote (if active) is evaluated and the game starts instantly. The command can of course only be used in the game-state "Lobby".
Syntax: /mw stop [lobby]
Aliases: -
Permission: mw.stop
This command ends the current game with a draw.
Syntax: /mw appendrestart [lobby]
Aliases: -
Permission: mw.appendrestart
This command appends a server stop and restart (if possible) after the next game ends. This command works independent of the restart_after_fights setting in the config.yml.
Syntax: /mw reload
Aliases: -
Permission: mw.reload
This command reloads all configuration files.
Note: Changes are only applied to games when they are restarted. This happens at the latest after the game-end. You can also force a game-restart with the Force-Stop or Restart-All command.
Syntax: /mw debug
Aliases: -
Permission: mw.debug
This debug command prints parts of the configuration into the server-log file.
Warn: This command does not output all information. This command must be revised / replaced in the future. If you have a problem, depending on the case, you should provide all the necessary information to help us identify / reproduce the error.
Syntax: /mw restartall
Aliases: -
Permission: mw.restartall
This command restarts all active MissileWars games.
Syntax: /mw version
Aliases: -
Permission: mw.version
This command shows the currently installed plug-in version.
Syntax: /mw setup <main|lobby|arena> …
/mw setup main fallbackspawn <set|teleport>/mw setup lobby <spawnpoint|aftergamespawn> <set|teleport> <lobby>/mw setup lobby area <pos1|pos2> <set|teleport> <lobby>/mw setup arena <team1spawn|team2spawn|spectatorspawn> <set|teleport> <lobby>/mw setup arena area <pos1|pos2> <set|teleport> <lobby>
Aliases: -
Permission: mw.setup
With this command, you can customize the most important areas and positions of your MissileWars setup and teleport to them.
Note: Cubic areas are of course defined with two points ("Position 1" and "Position 2"). It doesn't matter where you set which position. (They are sorted afterwards in the config.)
| Location / Area | Type | Description |
|---|---|---|
| Main Fallback-Spawn | Position | The player comes here after a game-quit or the MissileWars plugin deactivation, after the player is not allowed to enter the game or after rejoining the server within the "Lobby Area" / "Arena Area". The position should be located outside every "Arena Area" and ideally outside every "Lobby Area", to avoid errors caused by automatic teleports. The server spawn may be a good location for that. |
| Lobby Spawnpoint | Position | When the player enters the lobby arena and has been accepted, they will be teleported here. This should always be within the lobby arena. |
| Lobby After-Game-Spawn | Position | This is the position to which the players are teleported at the end of the game. This can also be within the lobby area. They are then automatically included in the restarted game. |
| Lobby Area | Area | This is the area to enter the game. When the player steps into this area, the plugin checks the conditions for entry and teleports the player to the "Lobby Spawnpoint". |
| Arena Team1 & Team2 Spawn | Position | This is the position to which the team member of team 1 or team 2 is teleported at the game-start / team-join or after respawn from a death. This should always be within the "Arena Area". |
| Arena Spectator Spawn | Position | This is the position to which the team member of the spectator-team is teleported at the game-start / team-join. This is typically further up outside the "Arena Area" between the two team spawns. But it is not important. |
| Arena Area | Area | This is the arena within which the players may be located during the game. |
