- All of wrecking ball commands, but improved.
- Configurable settings for how bases should be clustered and defined.
- An easy to use static API for interaction with the game at low cost.
- A non-static API for interaction with pre-processed data.
Due to an issue with the current AutoBuild on the website, releases are available on GitHub directly. Once the AutoBuild is switched to Jenkins and works, the releases will be available from ImperialPlugins.
This plugin uses a modified version of PlayerInfoLibrary which is NOT COMPATIBLE with any data from older versions of the plugin. If you plan on using this plugin, you will have to either manually migrate the old PlayerInfoLib data, or simply get rid of it and let it be re-created by the plugin.
|N/A||Note that this will temporarily hang the server, so it should only be used if tracking of buildables failed.|
|Finds and returns the amount of buildables specified with the arguments (all if no arguments are specified).|
|Similar to |
|Teleports to a random buildable that satisfies the arguments provided.|
|Teleports to a random cluster on the map, or a random one that is held by the specified player as the most common owner.|
|Lists the top 5 players with the highest amount of buildables on the map.|
|N/A||Lists the top 5 players with the highest common ownerships on clusters.|
|Queues a wreck clusters action with the specific filters.|
|Aborts/confirms a previously queued wreck clusters action.|
|Queues a wreck buildables action with the specific filters.|
|Aborts/confirms a previously queued wreck buildables action.|
|N/A||Wrecks all of the buildables that are on a vehicle that you are facing. Does not require confirmation.|
Arguments are special
All of the arguments can be on any order. For example:
/wreck pusta bed 50.0 is the same as
/wreck 50.0 bed pusta
[b | s | v] is the first set of filtering arguments. It specifies whether it should filter for JUST barricades (
b), for JUST structures (
s) or to INCLUDE buildables on vehicles (
[player] is rather self explanatory, and it accepts both the player name AND the player steam64id.
[item] is also self-explanatory, and it also accepts the item name AND the item ID.
[radius] is kind of self-explanatory, but it should be kept in mind, that for it to not be confused as an item ID, you should ALWAYS end it with
.0 (see example command above). Note that you cannot run the command from console when specifying a radius.
[abort | confirm] are text options, you have to write exactly
confirm in order for it to be accepted. It doesn't do much other than abort/confirm the previous action.
Other StuffDefault Configuration: TBP
Default Translations: TBP
If you need to contact me, please send an email @ [email protected]