Skip to content

GitLab

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

Closed
Open
Created Oct 26, 2023 by Andrea Di Giovanni@Cendi

Another Bug on Not capsed ID Enchantments

If i do /me enchant BURNING 1 and then /me enchant BURNING 2 it works, the precedent same enchant it's replaced by the new one. This when i have the Enchantment ID in CAPS.

When i have Burning as Enchantment ID it will not replaced...

EDIT: I've tested better and it seems just a graphic bug, fortunately the enchantments works (but obviosly, the bug persists)

In this screen i've used BURNING (CAPSED Enchantment ID) 2023-10-26_16.23.22

In this screen i've used Burning (not CAPSED Enchantment ID) and the result is the sovrapposition bug 2023-10-26_16.22.32

Edited Oct 26, 2023 by Andrea Di Giovanni
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking