I am switching to your module in favor of AMP’s built in because it’s got more granual control over the options as well as an option to implement Carbon.
Question: The original Template got alot of ways to schedule stuff that integrates into the rust server, for example:
That’s not in my control, that’s added via AMP’s code. There is no current way to add scheduler tasks via the generic module unfortunately
That said, most of the specific scheduler tasks in the AMP Rust module already have equivalents (eg “start the application” is the same as “start the Rust server”) or can be replicated pretty easily, eg sending messages and banning/kicking players just requires sending a command to RCON/console. The only real difference is the wipe scheduler task, and I’m not sure that works very well or at all in the AMP Rust module anyway
Most of those ones that AMP have are just wrappers around “Send a command to rcon/console” that run a pre-set command. So “Save the map and player inventories” is just the “Send a command to rcon/console” with the command being “save.all”. So all you need to do is read up on the commands Rust accepts to get the same result.
That makes sense, is there any way to check what the commands in the original rust module does with the wipe automation (in schedule).
I’ve actually made a couple reports about oxide not working in the original module, hence the switch to yours
@Greelan
Makes sense, well at least thank you for creating this module, it adds support for way more cool features.
Only thing I’d wish, not sure if possible, it to have the option “wipe on update” under wipe be a bit more configurable, so it doesn’t wipe on small updates, only on monthly updates
