Messages

Wario use two different bonesets for his costumes: One for normal Wario, and another one for WarioWare Wario. Using a mod with the wrong boneset on a wrong skin, say, for example a mod based off of normal Wario being used over WarioWare Wario, will freeze the game. Try changing which skin your mod(s) are replacing!

This is awesome Sammi! I wish I could help, however I don't have a PC that I can work with, so I'm unable to help.
Keep up the good work though :D

Just a small hint: Use multiple GFG1 files and compare them. Look at the different stages where this file is used, and observe how the enemy CPUs work here. It can help giving you an idea of how the file is structured/ what values do what, instead of only doing trial-and-error testing.

Oh, I feel this is necessary to mention:

Collision objects in COLL files in stages and SSE stages have a flag value that are only used in some SSE stages. It is probably related to some of the files in BLOCs. Also, some collision planes use "Crash1" as a material, which I believe can be related to damaging collisions or something. (Using that material in versus brawl stages, however, usually crashes the game.)

Just something to be aware of if you're gonna research files related to collisions :)

You probably know this, but ADPM parameters are very similar to STPM parameters. (Normal Brawl stages use STPM for pause-camera and shadow direction among other things.)

Subbed to thread. I worked on SSE files a long time ago, and had some data on the different types. Sadly, I think most of it is gone, due to my PC breaking some time ago.
I posted some information in the SSE collab thread, if you want to add it to the OP.

Nice. I worked on this a long time ago, until my laptop stopped working, and I lost all my work.
Still, I do have a link to a folder containing all the exported ADSJ files:
http://www.mediafire.com/download/6fn7uudfvubdteo/jump_(ADSJ).zip

These stages don't contain ADSJ files, due to being only one-room stages or coded differently:
Midair stadium (3 stages, but still doesn't use ADSJ)
The Ruined Hall
The Glacial Peak
Battleship Halberd Bridge

ADSJ files connects the different parts of stages. It uses offsets to refer to the stage-ID, and I believe the flags are for which entrance / outrance are used (perhaps Bone-IDs?)

---

EDIT: I also have the format for BGMG files, which controls which song is played in which stage (room) in SSE:
http://www.mediafire.com/view/jhelruref80vne9/BGMG_simple.txt

Feel free to ask more questions if you need anymore help :)

Learning to make your own custom XML isn't exactly easy. You need to learn the structure of a xml file, and what you can and can't do to make it work in-game.

For instance, the xml file needs to start with game ID / region so Riivolution recognizes the right xml with the game. Next, you have an "options" section, where you can make options for whatever you want, like for example different sets of stages. You can create multiple choices within the options, and each choice needs a "patch id", so Riivolution knows where in the xml it should look for commands.
After the options section, you have the patch section, where you have all the commands that tell Riivolution which files you want to replace, with your own ones.

I can give you an example of a xml that I used to use (take note this is a PAL xml):

http://www.mediafire.com/view/s0cf51ldyyiajd7/Brawl_Hack_Sets.xml

Sorry but you are not allowed to view spoiler contents.

I don't know how to add multiple pages to a xml, though :\

The CLR0 bug is just that and the Mask color being on the far right (unless it's intended to be that way.
I also found a small GUI bug in SHP0:

Sorry but you are not allowed to view spoiler contents.

The framecount doesn't display correctly when there're 5 digits.

Lastly, I'm having some strange Collision viewer issues.

Sorry but you are not allowed to view spoiler contents.

Oh, and just noting the model viewer issue also happens with the collision viewer too.

Small thing: When right clicking a Section in a module, it says "Open in Memory viewer". Right beside that, it has the shortcut Ctrl+O, but that doesn't work since BB already uses Ctrl+O for opening files.

Also, when trying to view a Camera entry in SCN0, I get a JIT exception:

Sorry but you are not allowed to view spoiler contents.

Only the header data will show up.

EDIT: I found a small GUI bug in CLR0:

Sorry but you are not allowed to view spoiler contents.

EDIT2: I'm having refreshing issues when entering model viewer and exiting:

Sorry but you are not allowed to view spoiler contents.

Minimizing the window and opening it again helps, but sometimes BB just crashes on me when exiting model viewer. Anyone else experiencing this?

Just a quick request, can you change the names of certain values in STPM files to this?:

Value28 - PauseCamZoomIn
Value29 - PauseCamZoomDefault
Value30 - PauseCamZoomOut
Value31 - PauseCamRotY-
Value32 - PauseCamRotY+
Value33 - PauseCamRotX-
Value34 - PauseCamRotX+

The values defines the limit of how much you can zoom out the pausecamera, how much you can rotate it etc.
Example: If I were to set the PauseCamRotY+ to 90, I would be able to see straight down at the stage from above when pausing the game.

PauseCamZoomDefault is the zoom value you get when switching between focusing on characters on the pausescreen, and you switch to not focusing on any character.

Wait, it's his b-day again?! Time sure passes fast!
Happy birthday BJ =]

It's about time we could edit the interpolation anyway :srs:
I'm somewhat surprised you guys have coped without editing the tangent slopes.

That's actually one of the main reasons why I never became an animator. I couldn't change the "smoothness" of turning points (keyframes), so I never really got satisfied with even the simplest stage animations.

A shader can have up to 16 stages. A stage holds color interpolation information to blend colors together from various sources (with the previous stage's output color, usually). You can add a stage to a shader by right clicking it -> Add Stage.

The shader only combines/blends colors together, it doesn't do anything else.
Everything else is handled by the material.

Color and Alpha are always used by the shader. The display of alpha and opacity is determined by the material, not the shader, by using Alpha Testing or Blending, respectively.

Lighting can be enabled through the LightChannels in the material. You can enable Color and Alpha lighting there. If you disable Color for LightChannel1, the material will appear to glow since it won't be shadowed.

Here's some more specs that I never finished:
http://forums.kc-mm.com/index.php?topic=39649.msg801237#msg801237

Makes me wonder why Shaders aren't directly a part of Materials.