During the "External Walls" event, where players defend against waves of Piglins and Ghasts, the server fails to process the enemy check correctly after a wave is completed. As a result, the next wave does not start, and players do not receive their rewards (Emeralds and XP). The issue repeats after a few waves. If players manually restart the event by breaking the gates, the problem reappears after another 1-2 waves. This significantly impacts gameplay, forcing players to use unintended methods to continue the event.
Steps to Reproduce:
1. Join the "External Walls" event.
2. Complete the first wave by eliminating all enemies.
3. Observe that the server does not start the next wave.
4. The issue occurs after 1-3 waves when the server gets stuck checking for remaining enemies.
Expected Behavior:
After a wave is completed and all enemies are eliminated, the server should:
Check that no enemies remain in the area.
Start the next wave.
Grant rewards (Emeralds & XP).
Observed Behavior:
The server freezes during the enemy check, preventing the next wave from starting and blocking rewards. Players must restart the event manually.
Possible Fixes (For Developers):
1. Enable Debug Logging:
Add debug logging to the event handling scripts to track execution flow and identify errors.
2. Fix Enemy Detection:
Ensure the game correctly detects all mobs in range:
"conditions": [
{
"test": "has_component",
"subject": "self",
"operator": "==",
"value": "minecraft:mob"
}
]
Prevent enemies from getting stuck outside the detection area.
3. Auto-Wave Timeout:
Add a 30-second fallback timer to automatically progress if no mobs are detected:
{
"event": "wave_timeout",
"value": {
"time": 30,
"action": "next_wave"
}
}
4. Optimize Event Scripts:
Check for dependent triggers that may be blocking the next wave. Ensure all conditions for progressing the event are properly configured.
Attachments
Comments 0
No comments.
