# Maugrim Woods Rework... Rework... Rework (!) **URL:** \ **Category:** Official News\ **Created:** [November 23, 2016, 3:49am UTC](https://community.gemsofwar.com/t/maugrim-woods-rework-rework-rework/15679 "2016-11-23T03:49:49Z")\ **Posts on this page:** 1\ **Showing post:** 34
**Author:** ![Sirrian](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/sirrian/32/35758_2.png) [@Sirrian](https://community.gemsofwar.com/u/Sirrian)\ **Post date:** [November 23, 2016, 10:27am UTC](https://community.gemsofwar.com/t/maugrim-woods-rework-rework-rework/15679/34 "2016-11-23T10:27:49Z")
> [@JapanGamer29](#): > > A dev responded that they couldn’t reproduce it. It was quite baffling. Yep - I remember when we were testing for that one. I didn’t test it myself, but I trust the guy involved to have followed the steps, and believe him when he said he’d tested it many times and not been able to repro it. I think we’ve seen it 2-3 times total in thousands of test games here in the office, and _never_ when we’re looking for it. We’re pretty sure there’s a timing issue involved, when situations like this occur, and have a good idea what’s causing it. For the tech folk out there, there is a poorly implemented state machine in the spell system that relies on timers rather hard-and-fast state changes to advance its state. It went unnoticed in the initial release, but popped up when spell effects became more complex. A fix is tricky, and has a little risk involved that it will cause a worse problem. So, after the fix, we need a LOT of QA on the spell system. If it were a simple fix, we would have done it a while back, but as I mentioned above, we’re going to make a big attempt to address this one for 2.2. Actually - believe it or not - it is very closely related to many of the on-death problems with traits, though some of those _are_ a separate issue. --- _[View the full topic](https://community.gemsofwar.com/t/maugrim-woods-rework-rework-rework/15679)._