Cricket 24 Blobset Tools

18 to 19gb lol
cb.png
 
Hi everyone, it's Wouldy here. I can't seem to access my Wouldubeinta account on here because the email I used doesn't exist any more and the moderators on here are no help, so I'm using this account.

Here is the new and fast Blobset Tools for all of Bigants games - https://github.com/Wouldubeinta/Blobset-Tools
This is great thank you Wouldy

I'm having an issue with modding scripts in Cricket24 though. Everything works fine in Cricket22 when I extract the scripts, decompile the lua's , make changes, rebuild the m3mp and then modify the blobset with that file. But doing the exact same in C24 I find the game hangs on boot-up after the Cricket24 logo and wont progress into the main menu.

Am I missing something or could this be a blobset rebuild bug do you think?

Cheers, keep up the great work.
 
This is great thank you Wouldy

I'm having an issue with modding scripts in Cricket24 though. Everything works fine in Cricket22 when I extract the scripts, decompile the lua's , make changes, rebuild the m3mp and then modify the blobset with that file. But doing the exact same in C24 I find the game hangs on boot-up after the Cricket24 logo and wont progress into the main menu.

Am I missing something or could this be a blobset rebuild bug do you think?

Cheers, keep up the great work.
Are you sure the lua script you edited doesn't have any error's in it. I known the decompiler doesn't do a complete job in decompiling some scripts. The Best way to test this is to create the m3mp with the original scripts and see if the game loads. If it does, then you know the blobset is getting built properly. There could be another reason they're not working, Bigant could be checking for any changes in the scripts
 
Does anyone know the file name of the stadium chair/seat in the extracted blobset of the stadium texture portion?
 
Are you sure the lua script you edited doesn't have any error's in it. I known the decompiler doesn't do a complete job in decompiling some scripts. The Best way to test this is to create the m3mp with the original scripts and see if the game loads. If it does, then you know the blobset is getting built properly. There could be another reason they're not working, Bigant could be checking for any changes in the scripts
Thanks for the reply Wouldy. Yeah, I'm pretty sure. Was the same values I'd changed and tested in Cricket22 which worked great.

I've just tried another couple of tests. First with a basic texture mod - Cricket24, mods, fields, textures, sponsors, sponsor_field_standard_col.pc.dds - Worked fine, game loaded, could see change in game.

I had been extracting and editing the compressed scripts. So this time had to verify integrity steam files to get the game working again and decided to try the uncompressed just incase this was the factor. So extracted uncompressed 57231 which is location data. Made no changes (not sure you can with those anyway), remade the m3mp with blobset, Tools, m3mp creator. Put this in the Cricket24, mods, m3mp, uncompressed folder. Then modify Blobset with the tools. Game hung/crashed on the Cricket24 logo again.

Seems to just be scripts mods with Cricket24. Wonder if anyone else has had any joy?

Same process for editing the compressed folder (57232) above works ok for Cricket22. Game loads to menu and I can see my changes in that game.

I'm mostly looking to edit those .lua files in the compressed folder 57232.

Hope this helps in narrowing this issue down.

Cheers.
 

Users who are viewing this thread

Top