-
Notifications
You must be signed in to change notification settings - Fork 1
Errors
This page is a helpful place to come if you are getting an error. All of the default errors that ModuCore will spit out when something is wrong are documented here as well as a few common things that people do wrong.
Table of Contents
broadcast_list_emptydefault_rtp_world_invalidkit_player_command_failedkit_console_command_failedkit_invalid_item
Your broadcast message list is empty but your auto broadcaster is still enabled.
Steps to Resolve: You only need to do one of the following.
- disable
auto_broadcastin themodules.yml - add messages to the
broadcast.messagessetting in theconfig.yml
The default RTP world in your config.yml (randomtp.default_world) is not a valid world. Until this is resolved, the player's world will be used as a fallback.
Steps to Resolve:
- edit your config.yml and change the default world to a valid world name on your server OR
""for no default world.
Sent when a player command for a kit isn't successful. This shouldn't ever happen. If it does, please make a bug report.
Sent when a console command fails for a player. This shouldn't ever happen. If it does, please make a bug report.
Sent when kits are being loaded and one of the items in the list of items is not able to be deserialized correctly.
This is usually because an item was edited manually and was messed up during that process.
The rest of the items will still be available in the kit, so you can see which ones are missing.
Steps to Resolve:
- claim or preview the kit in-game
- see what item is missing from the kit
- this is the item that broke. you can either remove it and add it back, or try and fix it yourself.
Discord Support: discord.jaims.dev