EpicLMS Last Man Standing Tournament v1.9.8

fixed all bug pls reset your config

A new EpicLMS update is now available.

This update focuses on fixing Team LMS countdown behavior and improving the team filling logic for 2v2, 3v3, and 4v4 events.

What Was Fixed​

Team LMS Countdown Fixed​

Team LMS no longer waits for all 24 teams to fill before starting.

Previously, when starting an event such as:

/lms start 2v2
the system could wait in the lobby because it was treating the maximum team count as a required team count.

This has now been fixed.

New Team Start Logic​

Team LMS now uses 24 teams as the maximum capacity, not as the required amount to start.

The event will now start the countdown when the minimum required number of full teams is reached.

Default requirement:

team:
min-teams-to-start: 2
Legacy compatibility:

party:
min-teams-to-start: 2

Example​

For a 2v2 event:

/lms start 2v2
The event opens with up to 24 teams available.

The countdown will start when:

Team 1 has 2 players
Team 2 has 2 players
So only 4 players are required to start a 2v2 event by default.

Team Filling Improved​

The team filling system has also been improved.

Players are now placed into teams in order:

Team 1 fills first
Team 2 fills second
Team 3 fills next
...
This prevents players from being spread across too many empty teams and blocking the countdown from starting.

Improvements​

• Fixed Team LMS countdown not starting
• Added minimum team requirement for Team LMS
• Improved team auto-fill logic
• Fixed 24-team capacity being treated as a start requirement
• Improved /lms forcestart team validation
• Updated Team LMS configuration defaults
• Improved 2v2 / 3v3 / 4v4 event flow

Recommended Update Steps​

1. Stop your server completely.
2. Replace the old EpicLMS jar with the new version.
3. Start your server.
4. Check your settings.yml.
5. Run /lms doctor.
6. Test Team LMS before using it in a live event.

Suggested Test​

/lms start 2v2
/lms join
/lms join
/lms join
/lms join
Expected result:

Two full teams are created.
The countdown starts automatically.

Notes​

This update is recommended for all servers using Team LMS events.

new EpicLMS update has been released.

This update focuses on improving spectator mode reliability, especially for normal non-OP players.

What Was Fixed​

Spectator Mode Guard Added​

Some servers had an issue where admins or OP players entered spectator mode correctly after elimination, but normal players did not.

This could happen when another plugin tried to change eliminated players back to survival/adventure mode or cancelled their gamemode change after death.

EpicLMS now protects eliminated players from being moved out of spectator mode while the LMS event is still running.

Improved Spectator Handling​

EpicLMS now checks gamemode changes for eliminated LMS players.

If an eliminated player is supposed to be in spectator mode:

• Spectator mode changes are allowed
• Survival/adventure changes are blocked during the event
• Spectator mode is enforced again after a short delay
• Both Solo LMS and Team LMS are supported

Affected Systems​

This update improves:

• Solo LMS spectator handling
• Team LMS spectator handling
• Normal player elimination flow
• Compatibility with protection/combat/spawn plugins
• Spectator stability after death or respawn

Recommended Update Steps​

1. Stop your server completely.
2. Replace the old EpicLMS jar with the new version.
3. Start your server.
4. Run /lms doctor.
5. Test with a normal non-OP player.

Suggested Test​

Solo LMS:

/lms start
/lms join
/lms forcestart
Team LMS:

/lms start 2v2
/lms join
/lms forcestart
Then eliminate a normal non-OP player.

Expected result:

The eliminated player should remain in spectator mode.

Notes​

This update is recommended for servers where eliminated normal players were not staying in spectator mode, while OP/admin players worked correctly.

new EpicLMS update is now available.

This update focuses on fixing spectator mode behavior for normal players and making the elimination system more reliable during real LMS matches.

What Was Fixed​

Spectator Mode Fixed for Normal Players​

In previous versions, admin or OP players could enter spectator mode correctly after being eliminated, but normal players sometimes did not switch to spectator mode properly.

This issue has now been fixed.

Improved Lethal Damage Handling​

EpicLMS now handles lethal damage more safely.

Instead of relying only on the normal Minecraft death/respawn flow, EpicLMS now detects lethal damage, prevents the broken death flow, and directly runs the LMS elimination system.

Expected behavior:

Lethal damage
→ Player is eliminated
→ Player is moved to spectator mode
→ Spectator mode is enforced again if another plugin changes it

Stronger Spectator Enforcement​

Spectator mode is now enforced more reliably for both Solo LMS and Team LMS.

The system now uses:

• Bukkit API spectator mode
• Console gamemode fallback
• Multiple delayed checks
• Respawn-safe enforcement

This helps prevent other plugins from changing eliminated players back to survival mode.

Team LMS Spectator Fix​

The same spectator fix has also been applied to Party/Team LMS.

Normal players eliminated during 2v2, 3v3, or 4v4 events should now properly enter spectator mode.

Improvements​

• Fixed normal players not entering spectator mode
• Improved Solo LMS elimination flow
• Improved Team LMS elimination flow
• Added stronger spectator fallback handling
• Reduced issues caused by death screen / respawn timing
• Better compatibility with servers using other protection or combat plugins

Recommended Update Steps​

1. Stop your server completely.
2. Replace the old EpicLMS jar with the new version.
3. Start your server.
4. Run /lms doctor.
5. Test Solo LMS with a normal player account.
6. Test Team LMS with a normal player account.

Suggested Test​

Solo LMS:

/lms start
/lms join
/lms forcestart
Team LMS:

/lms start 2v2
/lms join
/lms forcestart
Then eliminate a normal, non-OP player.

Expected result:

The eliminated player should immediately enter spectator mode.

Notes​

This update is recommended for all servers using EpicLMS, especially servers where normal players were not switching to spectator mode correctly after elimination.

A new EpicLMS update is now available.

This update focuses on display configuration, nametag behavior, TAB compatibility, and safer default settings for servers using TAB/Neznamy.

What’s New​

Enemy Nametag Display Fixed​

Solo LMS now properly shows players with an [ENEMY] prefix above their name when nametags are enabled.

Default solo display settings:

pvp:
use-isolated-scoreboard: true

nametag:
enabled: true
show-over-head: true
change-player-list-name: true
prefix: "&c[ENEMY] &f"
tab-prefix: "&c[ENEMY] &f"

TAB List Enemy Prefix​

Solo LMS now also applies the [ENEMY] prefix in the player list using Bukkit’s player list name system.

This avoids risky TAB commands while still showing the correct LMS enemy identity.

Party LMS Display Improvements​

Party LMS display settings have been improved.

Team members can keep their team prefix, while enemy players can be marked with [ENEMY].

Default party display settings:

party:
nametag:
enabled: true
viewer-scoreboard: true
show-ally-over-head: true
show-enemy-over-head: true
ally-prefix: "&a[%team%] &f"
enemy-prefix: "&c[ENEMY] &f"
change-player-list-name: true

Safer TAB Integration​

TAB integration is still supported, but EpicLMS no longer sends risky automatic TAB commands by default.

This helps prevent issues with TAB 5.5.0, including console errors caused by player property cleanup or reset commands.

Safe default TAB configuration:

tab-integration:
enabled: true
neznamy:
enabled: true
command-mode: false
reset-on-end: false
reset-commands: []

Config Migration​

A new config migration has been added.

If you are using an older settings.yml, EpicLMS will automatically update the important display-related settings using:

config-version: 185

Improvements​

• Fixed enemy nametag display in Solo LMS
• Improved Party LMS ally/enemy name display
• Added safer player list prefix handling
• Reduced dependency on TAB commands
• Improved compatibility with TAB/Neznamy
• Cleaned and validated default configuration files
• Added safer display defaults for older configs

Recommended Update Steps​

1. Stop your server completely.
2. Replace the old EpicLMS jar with the new version.
3. Start your server.
4. Check settings.yml.
5. Run /lms doctor.
6. Test Solo LMS and Party LMS display behavior.

Test Commands​

Solo LMS:

/lms start
/lms join
/lms forcestart
Team LMS:

/lms start 2v2
/lms join
/lms forcestart

Notes​

Per-viewer TAB list names are limited by Minecraft/Bukkit without packet-level systems. EpicLMS now uses a safer Bukkit-based display approach by default and avoids risky TAB reset or cleanup commands.

This update is recommended for servers using TAB, nametag systems, or Team LMS events.

fix tab error

A new EpicLMS update is now available.

This update focuses on stability, full system cleanup, Totem of Undying support, safer spectator handling, TAB cleanup improvements, and overall production-readiness.

What’s New​

Totem of Undying Support Fixed​

Totem of Undying now works correctly during LMS matches.

Previously, players could receive a totem in their offhand, but when they took lethal damage, they were eliminated immediately and moved to spectator mode before the vanilla totem pop animation could happen.

This has now been fixed.

Expected behavior:

• If a player has a Totem of Undying, the vanilla totem animation will trigger normally.
• The player will not be eliminated when the totem activates.
• The totem will be consumed naturally by Minecraft.
• If the player has no totem, lethal damage will eliminate them and move them to spectator mode.

Improved Lethal Damage Handling​

The lethal damage detection system has been improved for both Solo LMS and Team LMS.

This makes spectator transitions more reliable while still allowing vanilla mechanics such as Totem of Undying to work correctly.

Force Start Safety​

/lms forcestart is now safer.

The command can no longer bypass the event opening flow. An LMS event must be properly opened before it can be force-started.

TAB Cleanup Improvements​

TAB cleanup behavior has been improved.

If TAB integration is disabled, EpicLMS will no longer run TAB reset commands. This prevents unnecessary command execution and reduces unwanted console output.

Join Gate Fixes​

The event join gate system has been improved.

If an event start attempt fails or there are no valid players, the join state will now be cleaned properly instead of remaining open incorrectly.

Full System Audit​

This version includes a full review of:

• Solo LMS flow
• Team LMS flow
• Join and start logic
• Force start behavior
• Spectator handling
• Totem support
• Inventory lock protection
• Anti-dupe behavior
• Quit and kick cleanup
• TAB integration cleanup
• PlayerMoveEvent performance
• Config and language files
• Plugin resource loading
• 1.16.5+ compatibility

Recommended Update Steps​

1. Stop your server completely.
2. Replace the old EpicLMS jar with the new version.
3. Start the server.
4. Check your settings.yml.
5. Run /lms doctor.
6. Test Solo LMS and Team LMS before using it in a live event.

Suggested Test Commands​

Solo LMS:

/lms start
/lms join
/lms forcestart
Team LMS:

/lms start 2v2
/lms join
/lms forcestart
Setup commands:

/lms setlocation spawn
/lms setlocation lobby
/lms setlocation arena
/lms setkit

/lms setlocation party spawn
/lms setlocation party lobby
/lms setlocation party arena
/lms setkit party

Totem Test​

To test Totem of Undying support:

1. Give a player a totem in the offhand.
2. Start an LMS match.
3. Let the player take lethal damage.
4. The totem should pop normally.
5. The player should remain in the match.
6. If the player has no totem, they should be eliminated and moved to spectator mode.

Notes​

This update is recommended for all servers, especially servers using kits with Totems of Undying or servers running Team LMS events.

Thank you for using EpicLMS.

A new EpicLMS update has been released.

This update focuses on improving TAB integration behavior and removing unnecessary TAB cleanup messages from the console.

What Changed​

TAB Reset System Improved​

EpicLMS no longer uses the full TAB player data removal command when an event ends or when a player leaves an LMS event.

Previously, TAB could print messages such as:

All data has been successfully removed from player <player>
This has now been fixed.

Safer TAB Cleanup​

Instead of completely removing a player’s TAB data, EpicLMS now only resets the values it changes during the event.

New reset behavior:

tab-integration:
neznamy:
clear-on-end: true
reset-commands:
- "tab player %player% tabprefix &r"
- "tab player %player% tagprefix &r"
- "tab player %player% customtabname %player%"
- "tab player %player% customtagname %player%"
This keeps TAB cleaner and avoids unnecessary console messages.

Improvements​

• Removed full TAB player data removal command
• Improved TAB reset handling
• Reduced unnecessary console output
• Safer cleanup after LMS events
• Better compatibility with servers using Neznamy TAB
• Cleaner event stop and player leave handling

Recommended Update Steps​

1. Stop your server completely.
2. Replace the old EpicLMS jar with the new version.
3. Start the server.
4. Check your settings.yml TAB section.
5. Test a full LMS event and confirm that TAB prefixes reset correctly.

Notes​

If you previously used custom TAB commands, check the tab-integration.neznamy.reset-commands section in settings.yml.

This update is recommended for all servers using EpicLMS with TAB integration enabled.