Command Storm 2.8 - Mrbt0907/Weather2-Remastered GitHub Wiki

The /storm command is used to refresh certain configurations, create storms, kill storms and particles, and test certain features. This command does have tab completions, and has five sub commands that can be used.

Notice: As of version 2.9, the command was renamed to /weather2 .

/storm config currently only allows you to refresh certain lists internally. Use this if you need to refresh the dimension list config, the block grab list, the block replace list, the storm stage list, the wind resistance list, or the sound system. Sub commands are as follows:

• all - Refreshes all of the above lists
• dimensionlist - Refreshes the dimension rules for weather2
• grablist - Refreshes the block grab list
• replacelist - Refreshes the block replace list
• sounds - Stops all weather2 sounds and restarts the weather2 sound system
• stagelist - Refreshes the storm stage list; used to determine what stage a tornado/hurricane can go up to
• windlist - Refreshes the block wind resistance list; used to determine how strong a block is

Uses of these commands is limited, but can be used to fix some issues that may happen in the game.

/storm create allows you to spawn any type of storm that weather2 provides. This includes clouds, rainstorms, thunderstorms, hurricanes, and even tornados. In this update, you have more customizability, allowing you to spawn things like EF3 firenados, gigantic EF1s, or even an EF6 and above!

The overall format is as follows: /storm create <Storm Type> <X Position> <Z Position> <Flags>. You do not need to add coords to spawn a storm, but if you do provide coords, you must have X and Z inputted. Also, to add flags, or storm modifiers, you also have to have X and Z inputted.

Valid flags are listed below:

• alwaysprogress - The storm will ignore max stage and continue to progress
• direction=<#/north/south/east/west> - Sets the storm's movement to move only in the specified angle or direction
• dontconvert - The storm will not convert to a hurricane when over the ocean
• isfirenado - The storm will be engulfed in flames, spreading fire and glowing red
• ishailing - The storm will start with hail
• isnatural - The storm will revert to a rainstorm and progress up to the specified storm type
• isviolent - The storm will start violent, allowing it to reach 1 stage higher and spin faster
• name=<Word> - Gives the storm a name that will appear on radar. Spaces are not supported
• neverdissipate - The storm will not die when it reaches the max stage, and will remain at that stage forever
• revives=<#> - Sets the amount of times the storm can revive upon death up to the specified number
• size=<#> - Sets the storm's size multiplier to the specified number. 1 = 1%
• speed=<#> - Sets the storm's speed in which it will travel. This is in meters per tick I believe. 1 = Ender Dragon speed

Examples:

• /storm create ef1 - Creates an EF1 tornado at the player's coordinates
• /storm create f1 - Also creates an EF1 tornado at the player's coordinates
• /storm create c3 ~ ~ - Creates a category 3 hurricane at the player's coordinates
• /storm create F6 ~256 ~-50 - Creates an EF6 tornado at the player's coordinates, but offset by 256 blocks east of the player, and 50 blocks north of the player
• /storm create F10 5000 5000 isfirenado - Creates an EF10 firenado exactly at the coordinates 5000, 5000.

/storm kill is used both for killing storms and particles. Unfortunately there is no way to kill specific storms yet.

Sub commands are as follows:

• all - Kills all storms and sandstorms
• particles - Kills all particles on your client

Storm test is mainly used for development purposes. You may use these if you wish. Sub commands are as follows:

• class - Reveals all variables for the specified class file. Used for reflection purposes in code
• volcano - Summons a volcano at the player's current location

Does nothing yet, just like the command says. However, this is an upcoming feature for the gui update. This will show a screen with all the storms in the world for admins. Stay tuned!