Menu
▾
▴
2 Attachments
#511 Ammo Reload Tasks Disappearing
On 0.3.5 I am encountering a strange problem with depleted ammo after a scenario automatically replenishing after a save/reload. See files attached. I create a scenario, then edit the Mechs for damage and depleted ammo in MegaMek (since I use MekHQ for managing my boardgame campaign). The ammo reload and repair tasks show up in the Repair Bay. I do not complete the tasks and instead save. When I reload, all ammo is automatically full on all deployed Mechs (nothing was drawn from the warehouse stock), and the reload tasks have disappeared from the Repair Bay.
Related
This bug was introduced at some point between v 0.3.3 and 0.3.4
Going to stating hunting it down to whatever revision it came from. Probably step 5 revisions at a time or just split em in half until I find it that way. Depends on how many changes were made between 3.3 and 3.4
Ok, whatever caused this bug was made in the MM.jar included in r1674. Beyond that I don't know. Thats the best I can do for now. Don't know if I want to dig through the MM code.
A quick look at the MM svn shows it happened on or before 10001. Probably from 1001 since it had a change from slot to getmount. Will have to build 10000 and 10001 for HQ1674 to see.
Was wrong on the above but I have narrowed it down to between r9916-10001
Working on getting this down further and hope to have something concrete later today/tonight. 85 revisions to check...
Fastest way to find it is to split it in half and test a half. Test 1 revision below the split, if it's present that's your half and split again. So on and so forth. If it isn't, you split the UPPER half and continue.
I did that with HQ. I have already established that at some point HQ stopped writing the missing ammo to the save, just need to find the why of it and if I can fix it. If not, at least you wont have to hunt it down yourself ;)
I cannot dupliicate this in current SVN. If it crops up again in a 0.3.6 version or later please respond here requesting it be reopened.
Nevermind, Jayof9s pointed out I was missing a step in the replication. I've got it now, and I'll fix it soon.
Fixed in [r1854]
Related
Commit: [r1854]