FAQ & troubleshooting
Resolve missing NPCs, unavailable event commands, reward issues and configuration problems.
The plugin does not enable
Read the first startup error in the console. Citizens is required, and its full distribution must support the server's Minecraft version. A compilation/API artifact is not sufficient. Also check database credentials if you selected MySQL.
Use the Java runtime required by the server. TrickOrTreat's minimum Bukkit API does not mean every old server/plugin combination is supported. Folia is not supported.
A door does not respond
Check that the world is listed in General.enabled_worlds, the door is registered, the resident's position is valid and the event has been started through the setup tools. Verify the participant's trickortreat.player permission.
If General.force_cach_inventory is enabled, participants need to join the event first. A player may also be waiting for the configured repeat-visit cooldown or an unfinished ingredient task. Two simultaneous visitors cannot own the same active door session.
Join and leave do nothing
/tot join and /tot leave use the optional inventory-saving system. Enable General.use_cach_inventorys if you want that workflow. Otherwise use the event as part of your world and open the menu with /tot open.
Warp does not work
Set the event location using the setup tools and start the event. /tot warp requires both a configured location and an active event, as well as the player permission.
Players receive fewer sweets than expected
Check costume matching, GameSettings.rewards.min_amount and max_amount, and whether thieves are enabled. With Costumes.force_change, players must alter at least one costume part between doors.
Reward items thrown by an NPC are visual effects; they cannot be picked up. Check /tot stats for the actual sweet balance. Walking away before a response resolves cancels its pending reward.
I want a relaxed event
Choose Horror.intensity: GENTLE, disable darkness, reduce particle density or disable Horror entirely. Empty-house and thief settings are independent of the encounter system.
Updating an existing event
Back up the plugin folder and database first. Existing configuration files are not overwritten; missing encounter settings use defaults. Costume records are upgraded on save, so restoring an older plugin build also requires restoring the corresponding older database backup.
Find exact controls in configuration and atmospheric encounters.