Skip to content
This repository has been archived by the owner on Feb 2, 2022. It is now read-only.

Command Blocks are Broken #647

Closed
Owehttamy opened this issue Nov 2, 2021 · 2 comments
Closed

Command Blocks are Broken #647

Owehttamy opened this issue Nov 2, 2021 · 2 comments

Comments

@Owehttamy
Copy link
Contributor

Due to Warzone's changes/tests with viaVersion, protocolSupport, 1.17 support, and/or the conversion to a proxy, command blocks have been affected, and no longer seem to function whatsoever.
While the cause of this issue could boil down to something as simple as command blocks being disabled in the server.properties file or as complex as a plugin muddling with how command blocks function, some maps have been affected.

Currently, the maps (I'm aware of) that are affected by this problem are:

  1. Not So Spleef - Due to its functionality requiring snow layers to be removed so the lava can continue flowing down, uninterrupted.
  2. Crossfire - Spawning mechanism and end game function due to their inability to be supported by TGM.

These maps cannot function correctly or at all due to this issue and have limited solutions other than reenabling command blocks. The second-best option is by making broadcasts more versatile by removing their necessity to send a message in chat, and instead only running commands. However, this solution could only fix Not So Spleef as it doesn't require specific conditions to run the commands, while Crossfire requires players to break a block at the edge of the map to end the match.

While I am aware the use of command blocks cannot be a permanent and long-term way to make said maps function, it is the only viable solution at the present moment.

If command blocks, for whatever reason, cannot be re-enabled, the aforementioned broadcast proposal can be found here: WarzoneMC/tgm#791

Owehttamy added a commit to Owehttamy/Maps that referenced this issue Nov 10, 2021
@Owehttamy
Copy link
Contributor Author

Considered fixed once the server reenables command blocks in the server.properties file during a restart.

@Owehttamy
Copy link
Contributor Author

Considered fixed once the server reenables command blocks in the server.properties file during a restart.

Done. Fixed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant