Common Issues
This page covers common issues and gives you tips on maintaining stability over CoreArena and other Bukkit plugins in general.
You can see some good tips on using our maps in your dungeons including chest refills and waves of mob fights here: https://github.com/kangarko/CoreArena/issues/507
Yes, there's currently a workaround available, see this: https://github.com/kangarko/CoreArena/issues/401#issuecomment-746900595
1.13+: This feature requires Minecraft 1.13 or greater. WorldGuard: Ensure that block-break flag is true. If you set it to false in the global region, you need to make a custom WorldGuard region around the arena and set it to true there.
If you're having trouble teleporting players to a custom location right after the arena ends, especially if using Multiverse-Core, please use a small plugin made for this by myself. Enter the command to that plugin and test with different delays to see what works. For more information, see this.
Please add the permission corearena.class.KIT_NAME.
If you are using monsters as your next_phase_mode in arenas.yml, please kill all entities or mobs when saving arena snapshots, and if you like, you can use the %corearena_player_current_nearestmob% in a scoreboard to track down mobs inside your arena if you can't find them...
Check console for "[FAWE tick-limiter] Detected and cancelled physics lag source (...)" messages. Try to disable tick-limiter to see if it helps. Make sure you have both latest FastAsyncWorldEdit and CoreArena.
As of 1.16.x and possibly earlier, FAWE does not work with CoreArena, this is not because of CoreArena, but rather the fact that FAWE is very unstable at this point in time. But don't worry, you can simply use the normal WorldEdit plugin and enable Block_Bulk_Restore_Amount in settings.yml to stop lag when loading large arenas!
See this section in your arena.yml file:
-
To use color codes using the & character, put the entire message in quotes (double quotes "" also work). Example:
Random_Message: '&cHello &aworld' -
Use
\nto make a new line. Put the message in quotes. Some systems require different file encodings, see below. -
In localization, you can hide a message by setting it to 'none' or ''.
WordPad or Notepad on Windows is known to cause issues
The plugin saves files like settings.yml or the localization files (messages_X.yml) in UTF-8 format. You need to use this encoding especially if you are using special characters like smileys, symbols and other unicode characters in your files.
On Windows, using Notepad++ for editing your configuration is highly recommended. Most systems accept the UTF-8 (BOM) or UTF-8 encoding (see the green circle at the image for your current encoding). ANSI does not support unicode and may break files.
On Mac, Windows and Linux, we recommend using Atom for altering files. Check the green circle to detect your current encoding, click it to display a menu for changing it.
