Everytime I try to edit or mod B30 I always get this message
01.04.18 15:06:51 EAX: 0x00000000
01.04.18 15:06:51 EBX: 0x00000001
01.04.18 15:06:51 ECX: 0x00000000
01.04.18 15:06:51 EDX: 0x00000000
01.04.18 15:06:51 EDI: 0x0019F0E0
01.04.18 15:06:51 ESI: 0x00000000
01.04.18 15:06:51 EBP: 0x0019EFB8
01.04.18 15:06:51 ESP: 0x0019EFAC
01.04.18 15:06:51 EIP: 0x775EF60C, C2 08 00 90 ?????
01.04.18 15:06:51 EXCEPTION halt in \halopc\haloce\source\tag_files\tag_groups.c,#3157: #16 is not a valid scenario_vehicle_palette_block index in [#0,#16)

I can't go into the map file and delete whatever it is crashing the system so I deleted all vehicles and painfully renamed and added vehicles for a hour. After save the same problem exist. I'm not sure if it has something to do with opensauce but as of now I'm saying away from this scenario.

I believe I know your problem. The scenario keeps vehicles in two sections.

The first is the Vehicles table, which contains references to the actual vehicle tags.

The second section contains the instances of each vehicle placed in the map. It contains the coordinates of the vehicle and which number the vehicle is in the table mentioned above.

So in the second vehicle section, your 17th (0 based index) vehicle doesn't have a proper vehicle assigned from the table. Open the tag in guerilla, find the second vehicle section, find number 16 in the dropdown and assign a vehicle to the blank dropdown.


If the above isn't the case, you may have edited your scenario with the OpenSauce HEK. OpenSauce makes permanent changes to the tagfile when it opens certain tags that have upgrades in HEK, including the scenario. If the number of possible vehicle instances has been increased, from say 16 to 32, you may have too many vehicles for the stock tagset to modify. Which is why index number 17 (0 based index) is the issue, the first 16 are valid but stock Halo doesn't expect more than that.


It's one of those two probably. Or not.

Well another problem trying to find vehicle 16 in guerilla also crashes it.

Use OS_Guerilla, or Moses' Guerilla and try then. I believe it's the second option, where OS_sapien added additional vehicle instances.

Even if somebody else had ever opened it once in OS_Guerilla, it'll permanently break the tag for use in stock editing tools.

I was using open sauce nothing else I could do

Are you using stock vehicle tags?

I believe the CMT TSC:E tag release packages contain a fixed "b30_falling_box" vehicle, or something along those lines, which was a vehicle that previously broke on extract and never worked properly with HEK+ extraction.

TSC:E tag release also has several other "fixed" versions of campaign assets, like the female pilot from a10, which previously crashed the game or would otherwise cause exceptions in the editing tools.

I think I remember putting that patch in there before but I'll try again once I can modified DLL that upgrades the cache from 576 to 800 or 900