✨ DeACoudre | 1.19 - 1.21 | 1.0.3

Hello, The plugin is great, thank you for your work on it. I was not able to contact you via Discord or the Discussions tab, so I’m leaving this message here in the reviews. Right now, I have no way to disable the feature that modifies the TAB, even when the world is not specified in the config. The plugin still affects the TAB. Could you please add an ON/OFF option for TAB integration? This is currently preventing me from using the plugin in production. Another problem is the playerCap used as both minimum and maximum players Currently, the playerCap option is used for both the maximum number of players in the arena and the number of players required to start the game. The countdown before the game only starts once the playerCap value is reached. This means that to automatically start a game, the arena must be completely full (at max players). If we want to start a game with fewer players than playerCap, we are forced to use /dac forcestart, which is not ideal in practice. It would be much more flexible to have separate options, for example: minPlayersToStart (or similar) maxPlayers (current playerCap behavior) So that: The arena can start automatically when minPlayersToStart is reached maxPlayers still limits the maximum number of players allowed to join No possibility for dead players to spectate Another issue: when a player dies in the arena, they cannot stay to spectate the game. It looks like an execution timer or end logic is triggered, and the player is just removed instead of being put into a spectator state. It would be very useful to have a proper spectator system for players who are out of the game (for example, switching them to spectator mode or teleporting them to a spectator area while the game continues). Both points are important for game flow and player experience: Separate min/max player logic for cleaner automatic starts A spectator option for eliminated players Thank you for considering these changes and again for your work on the plugin.