Solved “Next Round Starts In” UI Stays After Leaving Arena

Return to plugin
Recent First Highest Voted
By the way I noticed your bots, I assume these are meant to be stationary bots. If that's the case I would recommend creating one spawn point per bot, with a radius of 0, so they spawn exactly at the center and only one bot appears. That way you can achieve the typical stationary bot setup used in aim train arenas
 
Upvote 0 Downvote
I assume these are meant to be stationary bots
Click to expand...

I did intend them to run around, I thought that would add to the realism. It would be cool if the player could toggle whether or not they're stationary if you're open to that.

creating one spawn point per bot, with a radius of 0, so they spawn exactly at the center and only one bot appears
Click to expand...

nice ty for the info! yeah, we just started running a minigame server so there's definitely some configuration tweaks to be made
 
Upvote 0 Downvote
idk if this helps, but it seems I don't even have to join the other ones for this to happen. On fresh boot, I joined aim train, played just fine, then I left to lobby and it started to do the countdown. If I join again, it resets the aim train arena, then stays there at 00 (second image)
1752052161416.png

1752052356981.png
 
Upvote 0 Downvote
You must log in or register to reply here.
  • About us
    Game4Freak is a Rust plugin marketplace and modding platform offering free and premium plugins for server owners looking to improve and take their servers to the next level.
  • Our
  • Your
Back
Top
Chat commands start with a /, while console commands can be entered directly in the F1 console or server console. Use find <keyword> in console to search for available commands related to the plugin. Parameters in < > are required, while [ ] are optional.
This plugin uses Oxide's permission system. Grant or revoke permissions using oxide.grant and oxide.revoke. You can assign them to individual players or groups using their Steam id or group name.
Settings are stored in the config file found under the config/ directory. You can edit this file manually, then reload the plugin to apply your changes.
Persistent data is saved in the data/ directory. This includes things like saved settings, usage stats, or player progress depending on the plugin. Deleting a data file will reset stored progress or customizations.
Language files are located in the lang/ folder. To translate messages, copy the en.json file into your target language folder (e.g. fr, de) and edit the values. Reload the plugin after changes to apply new messages.
This section lists public methods exposed by the plugin for use in other plugins. You can call these via the CallHook method. Ensure the plugin is loaded before calling its API to avoid null reference errors.
These are custom hooks that other plugins can listen for. Simply define a method with the same name and expected parameters in your plugin to handle the event. Hooks are triggered at key moments and are useful for extending or reacting to plugin behavior.
These hooks are injected into the game's code using Harmony. They let the plugin run code at key points in the game's internal logic. You can return values to block or modify behavior. Use with caution — these are powerful and can affect core mechanics.
Cart

Cart

Total -