Bug Closed · Resolved

Bug in Crucible condition?

#3936 opened by Unknown 3 years ago

Unknownreported this bug

Summary

?equipslot{slot=HEAD} true if i use this condition in line condition, while i've unequiped the helmet, it runs regardless.

Steps to reproduce

For example:

  • mechanic1{...} @self ?equipslot{slot=HEAD} true
  • delay 60
  • mechanic2{...} @self ?equipslot{slot=HEAD} true

If in these 3 seconds i've unequiped the helmet, the mechanic2 runs even if i unequiped the helmet.

Current behavior

Describe what happens currently, while the bug is affecting your server.

Intended correct behavior

Is there a method to avoid this? Or is it a bug? Can you put a condition that avoid this problem? Or fix (eventually) this bug? So if is it possible to make the condition updated in real time. So in in mechanic1 i have the item on HEAD, it runs, but if in the next 3 seconds i haven't the item on HEAD, it doesn't run.

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.

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.

Proposed fixes

If it's not a bug, so my suggestion is to make a new parameter in the condition: {slot=HEAD;realtime=true/false} for example realtime parameter that controls if the helmet is still equiped or not

Unknowncommented

This isn't really a bug since the equipSlot condition simply checks where an item skill originated from, if you use delays and need to ensure the item is still equipped you can use the wearing condition.

I'll add the suggestion to my list but it might be a while

Sign in to join the discussion.