I moved my old Robinhood quest into 403 from 2.11b16 and can't seem to get bombs no matter what I do.
In cheat> Link data it says I have bombs, start with 4 can carry 4, but they don't show in the active subscreen even though the passive sub counter says I have 4, and I bought some too which still didn't change anything.
This may have something to do with how b16 corrupted the subscreen when it was moved up there from b12c BUT I exported this subscreen and put it in the SwanSong Genesis quest in 403 that was brought up from 10b and bombs work fine in it.
Freedom, you may have missed this thread because it's now on the second page in Beta Discussion. This might fix most of your item issues.
http://www.armageddongames.net/forums//thread/97552/
Both of these quests were prior to 277 which means it will be a computability issue with older quests, so it will need to be ironed out.
Thanks for the heads up though. 😉
It's a compatibility issue only if a quest was saved in a 2.5 build. It has no effect on quests built in 2.10 or earlier.
The thread you pointed out doesn't seem to be talking about this situation though.
The Robinhood quest was last saved in b16 and then moved to 403 and played
The subscreen was exported from it when it was still in the b16 folder yesterday and imported into the Swansong quest that was brought up from b10b and worked on and saved in 403.
the bombs work in swansong and not in Robinhood, using the same subscreen in both.
so.... it seems that any quest from b16 may be effected if someone tries to play it only, the thread you pointed me to says this corruption happened in the 277, so this might be the same problem, although according DarkDragon's post it isn't, it still will need to be looked at, otherwise earlier quests might be effected.
I don't know... but I figure better safe than sorry.
I'd hate to see a stable version released and then start getting reports of bombs not showing up for people.
b16 was the exact build where the entire item system was gutted to allow for an item editor, so it is likely that the problems you are having have been fixed and do not occur for compatible (2.10 and earlier) quests.
If you post your quest (original b16 version), I'll be happy to double-check.