OBD:BINA/OBJC/MELE: Difference between revisions
Jump to navigation
Jump to search
m (technique, 0x40 : what about the value 2?) |
|||
Line 264: | Line 264: | ||
| BGCOLOR="#8C8CCC" | 00 00 00 00 | | BGCOLOR="#8C8CCC" | 00 00 00 00 | ||
| 0 | | 0 | ||
| ALIGN=LEFT | interruptible | | ALIGN=LEFT | 1 = "interruptible" (see below), 2 = ??? | ||
|- | |- | ||
|0x44 | |0x44 | ||
Line 297: | Line 297: | ||
:*the technique's "repeat delay" (probably the one at 0x4C) | :*the technique's "repeat delay" (probably the one at 0x4C) | ||
:*things (flags?) called "Interruptible", "Generous Dir" and "Fearless" | :*things (flags?) called "Interruptible", "Generous Dir" and "Fearless" | ||
;0x40 set to 1 | |||
:interruptible : technique will be stopped when opponent is outside specified range | |||
::;Loser | |||
:A range specified ''where''? Some moves have ranges as parameters, but a technique has a ''set'' of moves. | |||
:Do you mean that one of the ''technique'' parameters (either 0x44 or 0x48) is a range? Please confirm. | |||
::[[User:Geyser|geyser]] 00:00, 20 November 2006 (CET) | |||
:For everybody's convenience, I've grouped the techniques with the 0x40 field set to 1 [[OBD:BINA/OBJC/MELE/Technique0x40#Bit 0x01|HERE]]. | |||
::[[User:Geyser|geyser]] 00:00, 20 November 2006 (CET) | |||
;0x40 set to 2 | |||
:This is true for the following techniques : | |||
:*Furies : | |||
:**Body Surf Front | |||
:**Running Kick | |||
:**Running Punch | |||
:*Ninjas : | |||
:**Lightning Stomp | |||
:*Strikers : | |||
:**Jump Kick | |||
:**Running_Kick | |||
:**Running_Punch | |||
:*Tankers : | |||
:**Circle Left | |||
:**Circle Right | |||
:**Run/Dive-Left | |||
:**Run/Dive-Right | |||
:**Run/Drop Kick | |||
:**Run/Jump Kick | |||
:**Run/Jumpkick Back | |||
:**Run/Jumpkick Left | |||
:**Run/Jumpkick Right | |||
:**Slide | |||
:For an exhaustive listing (complete with actual classes), see [[OBD:BINA/OBJC/MELE/Technique0x40#Bit 0x01|HERE]]. | |||
:That has to be either "Fearless" or "Generous Dir" (whatever that means). | |||
:"Somebody better investigate soon." ^^ | |||
::[[User:Geyser|geyser]] 00:00, 20 November 2006 (CET) | |||
Revision as of 23:00, 19 November 2006
|
- Melee profiles
- They are stored globally, as a collection.
- There are 45 of them.
- Structure
- Melee profile header
- List of techniques (split in 3 groups : attack, evade, maneuver)
- List of moves (grouped in sequences corresponding to techniques)
- Messiness
- The move sequences are not listed in the same order as the techniques
- For a structure that's only 16 bytes in size, the moves have really complicated parsing.
- A lot of EXE hacking is necessary in order to understand and master a move's effect
Profile
Header example
- Size is 0xF0 = 240 bytes. Then there's a list of techniques, and a list of moves.
- Amount of techniques and moves used by the profile are declared.
- Amount of moves used by every technique is declared by the technique.
|
- Techniques
- They are listed right after the profile's header. Their number is specified in the header, and their size is 88 bytes each.
- Moves
- They are listed right after the techniques. Their number is specified in the header, and their size is 16 bytes each.
All profiles
In order of appearance in the collection
|
Sorted by ID
- The IDs start at 0 and increase by 1 for every next profile
- with the exception of the last 3, the IDs of which are 55, 56, 57
- (instead of 42, 43, 44)
|
Technique
- The amount of techniques (attack, evade, maneuver) is declared in the header.
- The list starts directly after the header. Every technique takes up 0x58 = 88 bytes.
- The example below is the first (attack) technique of the NINJA_easy profile
|
- Guesses
- The unknown parameters can be :
- the technique's "weight"
- the technique's "repeat delay" (probably the one at 0x4C)
- things (flags?) called "Interruptible", "Generous Dir" and "Fearless"
- 0x40 set to 1
- interruptible : technique will be stopped when opponent is outside specified range
- Loser
- A range specified where? Some moves have ranges as parameters, but a technique has a set of moves.
- Do you mean that one of the technique parameters (either 0x44 or 0x48) is a range? Please confirm.
- geyser 00:00, 20 November 2006 (CET)
- For everybody's convenience, I've grouped the techniques with the 0x40 field set to 1 HERE.
- geyser 00:00, 20 November 2006 (CET)
- 0x40 set to 2
- This is true for the following techniques :
- Furies :
- Body Surf Front
- Running Kick
- Running Punch
- Ninjas :
- Lightning Stomp
- Strikers :
- Jump Kick
- Running_Kick
- Running_Punch
- Tankers :
- Circle Left
- Circle Right
- Run/Dive-Left
- Run/Dive-Right
- Run/Drop Kick
- Run/Jump Kick
- Run/Jumpkick Back
- Run/Jumpkick Left
- Run/Jumpkick Right
- Slide
- Furies :
- For an exhaustive listing (complete with actual classes), see HERE.
- That has to be either "Fearless" or "Generous Dir" (whatever that means).
- "Somebody better investigate soon." ^^
- geyser 00:00, 20 November 2006 (CET)
Move
- The amount of moves is declared in the header.
- The list starts directly after the list of techniques.
- Every move takes up 0x10 = 16 bytes.
- The example below is the last move of the NINJA_easy profile
- (actually the one and only move of the Pause technique)
|
- Move types
- 0 : Attack, struct array starts at 0x140A88 in the English EXE
- 16 : Position, struct array starts at 0x1435B0 in the English EXE
- 32 : Maneuver, struct array starts at 0x143AB0 in the English EXE
- 48 : Evade, struct array starts at 0x143E30 in the English EXE
- 64 : Throw, struct array starts at 0x144370 in the English EXE
Blue Box Beta WMDD
- PART 1 - PROFILE
- PART 2 - TECHNIQUE
- PART 3 - MOVE
ONI BINARY DATA |
---|
AKVA << Other file types >> CBPI |
BINA : Binary data |
TMBD << Other BINA >> ONIE |
OBJC : Objects |
FURN << Other OBJC >> NEUT |
MELE : Melee profile |
[[OBD:File types/{{{family}}}|{{{family}}} file]] |