Iterated entries messes up the internal array list
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ares |
Fix Released
|
Medium
|
AlexB |
Bug Description
So I noticed that sometimes when I pick up an explosion/
Today I decided to dump out the internal arrays to check it out and I was surprised when I seen that TWLT100 was at the end of the list (like if it was read somewhere from the ini) and ELECTRO played because the crate is hardcoded to play the first animation on the array.
I replaced the 0 with a + to have TWLT iterated and then ELECTRO disappeared. I checked an older version and it was right. Then I noticed that at the end of my Animations list, one animation, which I placed there for AttachEffects testing was an iterated one (to not even mess up the array list), I commented it out and my array was fine.
Mod INIs are attached. Debug.logs will soon be as well.
Changed in ares: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in ares: | |
assignee: | nobody → AlexB (alexander-b) |
milestone: | none → 0.d |
status: | Confirmed → Fix Committed |
Changed in ares: | |
status: | Fix Committed → Fix Released |
235455 has TSTIMPCT2 commented out,
233113 has +=TWLT100
and 224224 has the original setting.