Quoted from timlah79:Hey guys. For the time being, please don't PM me about making updates or porting existing customizations to 1.01. While it's awesome that I can now access 1.01's sound files (all thanks to PBrowser's amazing latest app update), I am not allowed to share firmware files as per its developer. If I do, my PB license will be revoked. I need to be respectful of his requirements.
The other blocker is that upon investigation today into 1.01, the sound script locations have been completely jumbled vs. 1.00. This means that everything I bookmarked in 1.00 and prior is now irrelevant/unusable to accurately pinpoint any given sound script. Until I can figure out how to realign such changes, I won't be able to do anything. Bookmarking 3800+ locations alone and figuring out script changes from 0.96+ to 1.00 each time was months of work prior and a prerequisite for me to implement sounds in the first place.
If you are PB savvy with adapting .dat changes from firmware version to version (with JP or any Spike 2 code releases in general): Please PM me. I could use any help I can get.
In summary, my hands are tied in more ways than one. At this time, I cannot promise any updates nor share even my current code version with you. Really sorry to be the bearer of bad news instead of good. I haven't given up. I'm still looking into all of this and figuring out how to do things the right way while following the new sharing rules. Thanks for your understanding and patience.
Tim - the way I understand it is that you can share the macro with folks which essentially will provide the updates to the code that way. So I believe you can eventually share it if you want. Just an FYI.
I can’t comment on file locations but from experience on JP, stern mixes up the file locations when they update which is so annoying when trying to adapt custom code to the new version!