Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maxing burnout sets me on fire, causes crash with mage robe leggings on. #1681

Open
CJenkins93 opened this issue Apr 21, 2020 · 1 comment
Open

Comments

@CJenkins93
Copy link

-Playing FTB Infinity Evolved Expert

-I made a set of mage robes and put them on, I'm a vampire from witchery but we have another vampire on the server who this doesn't happen to.

-I recently hit level 19 in ars magica 2.

-I started leveling by spamming a self>shield spell a few times. This maxes my burnout which will then sets me on fire for a couple ticks. If I'm wearing mage robe leggings I, and anyone in the same dimension, crash when it tries to stop the fire.

-The crash report mentions blood arsenal but I cannot fathom why from reading it, considering what is happening. This on top of the fact that I haven't gone into blood magic at all. I don't even have an LP network.

-Tried setting myself on fire with flint and steel, no crash. Could spam my spell without being set on fire for a while, but once my burnout fully hit 0 I could cause it again. My arcane affinity is around 47% but checking the affinity stuff it doesn't seem to have anything to do with it.

-None of us can figure out why I get set on fire from maxing burnout for a few seconds. It can happen with any spell, anytime, anywhere, but only to me and no one else has EVER been set on fire from burnout.

-Keep in mind that this never happened for several weeks, but now I get set on fire from burnout with the same spell I always use to level. Very strange.

-If you need the crash report I'll post it but only if you request it. The only issue is me being set on fire so I would like to fix that if possible.

@Flamehearthh
Copy link

I am also experiencing this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants