Hi guys. I’ve been a little absent lately. Free time isn’t something I can really enjoy myself in terms of brawl hacking these days.
Also, I’ve been working on stage fixing and even stage making for the recent ProjectM demo. One of the stages I’ve made to be used in that demo is my own version of the Metal Mario stage in SSB64.
Yeah, this stage was already in the vault… at least 3 times. But I’ve always wanted to make my own one, and I felt this was the moment, specially due to the ability to give the stage a real metal effect. It comes in 2 versions, the standard one, and a smaller one, fitting the size that had one of the old versions in the vault, used in ProjectM prior to the demo.
I’ve also included the ProjectM version in a separate folder, which is smaller than the standard one, and bigger than the small one. Get the one you want, unless you don’t want it, or you already use it in said demo.
Now, the other item in the title. I’ve made a new tool called GCT Analyzer. You may have used ChiboSempai’s GCTEdit, which opens txt and gct files, and allows to edit them and stuff. This GCT Analyzer is similar, only that doesn’t open txt files, but only gct’s.
The tool looks the entire file, identifies some of the codes (not all of them, the database has to keep growing), and lists them. If some code isn’t identified, it’s put together as an ‘unknown code’. You can select the codes in the list and preview them in txt format.
Why could be this tool interesting? You may have not compiled the gct you’re using. It may have some codes you don’t want to use, but it is harder to find all the codes and compile them yourself. The tool allows you to remove codes from your gct. It also allows you to include new codes (from other gct files) and export your codes as individual gct files. Those individual gct files can be stored, and fused afterwards, with GCT Analyzer or even GCT Fusionizer.
Basically, it’s meant to help you to customize your codes. You can’t edit them in the program, that’s the bad thing. But once splitted, you can use tools like GCTEdit to edit them quickly.
Anyway, people aren’t usually editing codes, but using them. And editable codes like the ASL or the custom SSS are already covered by other tools.
So this is it. Keep always a copy of your gct before using the tool (it isn’t perfect and may fail). Also, some codes may not be found. If you know of a code that should be listed, and isn’t, just report me the issue via private message and I’ll add it to the internal database.
As a final note, I’ve done some stage skins for the ProjectM demo. These are 2 of them:
For those willing to make ProjectM demo skins for stages, in order to avoid problems, please be sure they’re not desynching on wifi and replays. Some stages in the ProjectM pack may look like the original Brawl ones, but they have some edits that make them different. So be sure you’re editing a stage in the pack, not an original Brawl one, not only for not desynching, but for keeping the same visual experience.
That’s all. Next time, Temple of Time, or Fire Temple, or whatever, who knows xD
EDIT: I’ve updated the tool, now the changes in the codes (text format) can be put back into the gct file. This allows you to add codes that you have in text format only too.