Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
MythicMobs MythicMobs
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 140
    • Issues 140
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • MythicCraft
  • MythicMobsMythicMobs
  • Issues
  • #1687

Closed
Open
Created Aug 07, 2024 by Theeef@Wyzards

holding condition validates AIR as specific mmoitem after restart

Summary

Describe the bug encountered in detail.

Steps to reproduce

Provide a full set of steps used to reproduce the bug, including links to SEPARATE Pastebin pastes for each relevant configuration file.

Not sure which are relevant. This could be a config issue, so I've included all I thought could be helpful. Apologies if this is a configuration issue.

  • Mob File: https://pastebin.com/znRKqfxs
  • Skills file: https://pastebin.com/zkAR4bYa
  • General Mythic config: https://pastebin.com/BZ1ZJhZX
  • Mythic Mobs config: https://pastebin.com/cXF8dm60
  • Mythic Items config: https://pastebin.com/zKdGSmW2
  • Mythic Skills config: https://pastebin.com/e7bGvEc7

Current behavior

I have a skill with a TriggerCondition of the player holding a specific MMOItem. This works fine, but when I restart the server it validates AIR as the specific MMOItem. This is fixed after running /mm reload, where the condition then works as intended.

Intended correct behavior

The TriggerCondition should function correctly after server restart without requiring a plugin reload.

Server log file

Provide a link to a Pastebin paste with a copy of your server's latest.log file from startup to "Done!" AND includes a player connecting. https://pastebin.com/r5dqd8Um

Debug log snippet

Provide a link to a Pastebin paste with an excerpt of your latest.log file that includes debug output where you trigger the bugged behavior. /mm debug mode true repeatedly said "Debug Level must be an integer (1-5)" despite me trying /debug level 5. SOL :p

Proposed fixes No idea

Edited Aug 07, 2024 by Theeef
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking