Matthew Evans
- Slayer3201
- slayer3201
- Europe/Stockholm
- Yes
- No
MC-137070
MCD-7097I was testing a build on a training dummy, when all of a sudden I managed to activate my firework rocket artifact without it actually firing. I was able to recreate this bug a couple times, albeit with some hassle as it seems to require frame-perfect input; with activating the artifact and firing off a scatter crossbow at the same exact time. The fireworks do not fire, and do not queue up either, they simply vanish and the activation of the firework is wasted.
I was testing a build on a training dummy, when all of a sudden I managed to activate my firework rocket artifact without it actually firing. I was able to recreate this bug a couple times, albeit with some hassle as it seems to require frame-perfect input; with activating the artifact and firing off a scatter crossbow at the same exact time. The fireworks do not fire, and do not queue up either, they simply vanish and the activation of the firework is wasted.
Something I also noticed is that an arrow is not consumed either. Almost as if the firework is added to your arrows, but lacks the firework effect when it's fired off in this method.
I can confirm the notion that this bug only appears to happen with Food Reserves; unsure about Surprise Gift as I have yet to touch that enchantment myself but on my current build, my armor has tier 3 Food Reserves and I begin getting the bug as soon as I use my potion and the food spawns. I don't even have to pick up any of the food before the bug is there and noticeably inhibiting movement and interactions. Interacting with the food on the ground appears to make the bug even worse. It is not level dependent, this bug seems to happen in any level, even in the Camp. Legitimately all it takes is the use of your potion while Food Reserves is active to proc the bug.
If I had to guess, based off of the inhibited movement and inhibited ability to interact with all objects (including consumables, enemies, and zone changers), the bug seems to mess with the raycast equivalent sent out by the cursor, or at least the interpretation of said raycast equivalent. That is if raycasts are even used for cursor input interpretation. Again, this was if i had to guess.
I noticed a few specifics about this, I too was able to consistently recreate the issue, and I have a few things to add: