Fully Server Side

ResourceWorldResetter plugin should not affect the client side. It is purely a server-side plugin that deals with world management, such as resetting and recreating resource worlds. Here's a breakdown of how it works:

Server-Side Plugin

• Server-Side Impact Only: The plugin manages worlds and resets them on the server. It doesn't interact directly with the Minecraft client's files or settings.

• Works Independently of Client Versions: Players can connect using older or newer client versions, as long as they are compatible with the server version. The plugin’s functionality, such as world resets, will still work on the server side regardless of what client version the player is using.

Key Notes:

1. Client Versions: As long as the server version is up to date (and the plugin is compatible with it), players using different versions of the client (older or newer) won't be affected by the plugin directly. The only client concern is if their version is compatible with the server version.

2. Plugin Operation: The plugin resets worlds and teleports players before the reset. The client only sees what the server sends, like the new state of the world after it’s been reset. It doesn't change anything on the players’ local Minecraft installations.

3. Cross-Version Play: If you're using a cross-version plugin (like ViaVersion or ProtocolSupport), which allows players on older clients to connect to a newer server, the ResourceWorldResetter plugin will still operate as intended on the server without causing client-side issues.

Summary:

• No impact on player clients (whether old or new Minecraft versions).

• Server-side only: The plugin works as long as the server is up to date and the plugin configuration is correct.

• Compatibility: Players using older or newer client versions will see the server-generated world reset, but it won't directly affect their client-side experience.

Exception:

• The only possible client-side issue would arise if a player is on a version of Minecraft that’s incompatible with the server version itself. In that case, it's not related to the plugin but to Minecraft version mismatches.