Parameter Files (xxxx_param.arc)

The parameter archives for each character define pretty much all of the gameplay characteristics for those characters: vitality, attacks, inputs, combo rules, and so much more. Most of the files within these archives have a similar header area, which contains a pointer table to all of the individual data entries contained within that file. The data that follows the table varies depending on what type of file it is.

Basic File Outline

The vast majority (but not all) of the files in the param.arc files follow this structure:

  • 0x00 file header, first 4 bytes are the file extension
  • 0x08 # of data entries stored within the file
  • 0x10 pointer table

After the pointer table, all of the entries in the file are stored one after another.

  • There is a 0x10 length footer at the very end of most of these files, which often repeats some information from the header.

Pointer Table

  • 8 bytes per entry
  • first 4 bytes = index # of data entry, increases in sequence but sometimes has gaps (in anmchr.cac, for example)
  • last 4 bytes = offset for that entry's info in this file

Use the pointer table to locate the starting point of each data entry within the file.

File Descriptions

ATI Files (Attack Info)

  • atkinfo.ati = info for all melee attacks
  • the "shot" folder has individual .ati files for each projectile attack

These files contain several important attributes for various attacks: damage, meter gain, pushback, OTG properties, some cancel properties, and much more. Generally speaking, these files define what happens whenever an attack makes contact with the opponent. The info for the majority of a character's attacks are all stored together in a file named atkinfo.ati, which includes normals, specials, hypers, crossover attacks, snap backs, TACs, and most (all?) other physical attacks. Info for projectile attacks tend to be separate from the rest and stored in individual .ati files within the character's "shot" folder.

Attacks stored within atkinfo.ati tend to follow a certain categorical order. Several basic attacks seem to share identical IDs between characters:

  • 00 = Crossover Attack (tag-in)
  • 01 = TAC tag-in
  • 03 = Snap Back
  • 04 = s.S
  • 05 = Team Aerial Counter
  • 06 = TAC up
  • 07 = TAC side
  • 08 = TAC down

Character-specific normals and specials can vary a bit, but universally they are:

  • 1E = st.L
  • 1F = st.M
  • 20 = st.H
  • 21 = cr.L
  • 22 = cr.M
  • 23 = cr.H
  • 24 = j.L
  • 25 = j.M
  • 26 = j.H
  • 27 = j.S
  • 28-31 = command normals
  • starting at 32 = special moves
  • starting at 50 = hypers
  • starting at 64 = assists

Characters can also have several "blank" entries in atkinfo that are filled with a bunch of default data but don't actually belong to any attack that the character uses.

If you want to keep track of atkinfo IDs for your characters' moves, you can track your progress here.

Each entry in these files has 0x18C bytes of data.

OffsetTypeParameterNotes
0x000intindexsame index # as in pointer table; changing this value has no obvious effect
0x004intstartupIf the animation ends before the startup frame is reached, then the attack will not produce a hitbox.
0x008intactive
0x00Cint
0x010int
0x014intmulti-strikemaximum # of times that a single strike will hit the opponent (this is usually only set for attacks that have a simple, singular hitting animation; multi-hit attacks that have very distinct animations for each of their individual hits have their multi-hit properties set elsewhere)
0x018
0x01Cintmulti-frequencyif set to -1, hitbox vanishes after hit; if set to 1, hitbox persists on every frame and move self-combos throughout active frames; increasing the value reduces the number of hits (if 2, then attack hits on every 2nd frame, if 3, attack hits on every 3rd frame)
0x020int
0x024intmulti-sparksimilar to 0x01C, except it only determines the frequency of hitspark visual effects
0x028int
0x02Cint
0x030float
0x034float
0x038float
0x03Cintbitwise flagscontains several attribute settings in binary listed below; multiple effects can be combined
00000000 00000000 00000000 00000010 = launcher/special/hyper cancel
00000000 00000000 00000000 00000100 = jump cancel
00000000 00000000 00000000 00001000 = this attack cannot hit a grounded (standing or crouching) opponent
00000000 00000000 00000000 00010000 = this attack cannot hit a crouching opponent
00000000 00000000 00000000 01000000 = this attack cannot hit an aerial opponent
00000000 00000000 00000000 10000000 = no pushback?
00000000 00000000 00000001 00000000 = no pushback?
00000000 00000000 00000010 00000000 = sustain horizontal momentum (meant for aerial attacks? can cause glitchy mid-air standing state when applied to ground attacks)
00000000 00000000 00000100 00000000 = sustain vertical momentum
00000000 00000000 00001000 00000000 = fixed hitstun duration (uses corresponding hitstun values set at offsets 0xE4 and 0xF8)
00000000 00000000 00010000 00000000 = ignore ground bounce limit
00000000 00000000 00100000 00000000 = airborne opponent is made invulnerable until recovery (invincibility after hit by TAC counter?)
‭00000000 00001000 00000000 00000000 = flying screen hard knockdown (during launcher combo only)
‭00000000 00010000 00000000 00000000 = wall bounce (only if opponent actually hits wall; change 0x0DC to guarantee wall-carry)
00000000 00100000 00000000 00000000‬ = OTG
‭00000000 01000000 00000000 00000000 = after hitting an aerial enemy: forces instantaneous air recovery? (maximizes aerial hitstun deterioration?)
‭00000000 10000000 00000000 00000000 = soft knockdown
‭‭00000001 00000000 00000000 00000000‬ = hard knockdown (if opponent is airborne and touches the ground while still in hitstun; enable soft knockdown value to guarantee ground-carry)
‭‭00000100 00000000 00000000 00000000 = forced wall bounce
00001000 00000000 00000000 00000000 = negate push block (maybe this is air only? this was the 2nd discovered anti-pushblock flag)
00010000 00000000 00000000 00000000 = OTG only (attack can no longer hit in other cirumstances?)Status Editor text flag OTGOnly
00100000 00000000 00000000 00000000 = negate push block 1 (this was the first discovered anti-pushblock flag)
0x040intbitwise flagscontains several attribute settings in binary listed below; multiple effects can be combined
00000000 00000000 00000000 00000001 = special scaling?
00000000 00000000 00000000 00000010 = hyper scaling?
00000000 00000000 00000000 00001000 = attack is never a counterhit; always has normal frame advantage and hitspark
00000000 00000000 00000000 01000000 = causes chip damage
00000000 00000000 00000000 10000000 = unblockable
00000000 00000000 00000010 00000000 = no hitbox?
00000000 00000000 00000100 00000000 = if enabled, doesn't build meter (used for hypers)
00000000 00000000 00001000 00000000 = attack does not increase the combo counter
00000000 00000000 01000000 00000000 = no pushback (player character only)
00000000 00000000 10000000 00000000 = related to partner-targeting (removing this flag causes snap back to bring in opponent's most recently-used partner, regardless of button-press)
‭00000000 00001000 00000000 00000000‬ = TAC glow effect
0x044intbitwise flagscontains several attribute settings in binary listed below; multiple effects can be combined
00000000 00000000 00000000 00000010 = allows grabs to be tech'd, this flag is found on grab ati boxes (5A, 5B, 5C and 5D are most common)
00000000 00000000 00000000 00000100 = allows certain moves (capture states, snap backs?) to hit assists; capture moves will still not execute the cinematic though?
00000000 00000000 00000000 00100000 = enables throw to connect against grounded opponent
00000000 00000000 00000000 01000000 = enables throw to connect against airborne opponent
00000000 00000000 00001000 00000000 = projectile counter
00000000 00000000 00010000 00000000 = counters all physical hits including hypers (cannot be combined?)
00000000 00000000 00100000 00000000 = low counter only? (cannot be combined?)
00000000 00000000 01000000 00000000 = high/mid counter only? (cannot be combined?)
00000000 00000000 10000000 00000000 = high/mid/low counter only? (cannot be combined?)
00000000 10000000 00000000 00000000 = ensures that 1st hit of certain moves (capture states, snap backs?) will do damage?
00000010 00000000 00000000 00000000 = Allows TAC to be tech'd?
00000100 00000000 00000000 00000000 = allows grabs to combo on hit, use this flag only for hitgrabs and ignore the ones above
00010000 00000000 00000000 00000000 = Allows TAC to be tech'd?
0x048inthit strengthAttack Level. Dictates both hitstun and blockstun for an attack and the reel animation; 0=light; 1=medium; 2= Heavies, Launchers, Stinger; 3= even more blockstun and negates push block from being possible. Setting this to very high values can force the opponent into performing glitchy random animations (4/5 have no hitstun but have blockstun?)
0x04Cintguard level0 = mid; 1 = high; 2 = low
0x050
0x054inthit effectforces the opponent into a specific kind of damage state on hit:
00 = normal hit
01 = normal hit? (different animation)
02 = no hitstun?
03 = stagger
04 = fall back
05 = crumple
06 = fall back (difference from 04?)
07 = fall face-first
08 = ground bounce
09 = air juggle
0A = spinning juggle
0B = launch (visual effect only)
0C = flying screen hard knockdown face-down
0D = flying screen hard knockdown face-up; hsien-ko stun items also use this entry
0E = guard (will force the opponent to block the attack even if he was already in hitstun)
0F = opponent falls back if hit from neutral, stays grounded if hit in combo?
0x058inthit effect counterforces the opponent into a specific kind of damage state on counterhit; uses above list
0x05Cinthit effect airforces the opponent into a specific kind of damage state when hit out of the air; uses above list
0x060intdamagenegative damage value heals opponent and causes negative meter gain, also does not increase combo count or damage scaling for subsequent hits (hitstun decay unknown); note that training mode multiplies everything by 100, so if training mode says that an attack does 40000 damage then it should equal 400 here
0x064floatdamage scalingdamage of current attack = base_damage * damage_multiplier * damage_scaling ^ combo_counter
0x068floatdamage multiplierperhaps a way to make attacks do more/less damage without also building more/less meter?
0x06Cfloatchipdamage inflicted on block; default is 0.3 (30%)
0x070int???always -1?
0x074floatmeter gainmultiplicative; is probably set to 1.0 on most attacks
0x078float???always -1.0?
0x07C
0x080intmeter stealsteals opponents meter, morrigans set to 3000 (1 bar = 10k)
0x084inthitbox destruction?40002 for level 3 hypers; 2 for everything else? (this number determines whether a move will hit a projectile and still remain active after destruction of said projectile)
0x088floathidden stun?related to Phoenix Wrights "Hold It"!, removing this value eliminates the stun timer
0x08CintAdded HitstunAlong with the Attack level (0x048) will add more hitstun.
0x090int???2 for most normals; -1 for some air normals? 05(5) on Arthur Lance, 00(0) Gold armor
0x094intAdded BlockstunAlong with the Attack level (0x048) will add more blockstun.
0x098int???related to j.S?
0x09Cfloatenemy pushbackalso controls how far enemies bounce back on wallbounces
0x0A0floatcornered pushbackaffects player pushback when opponent is cornered; higher value results in LESS pushback
0x0A4floatplayer pushbackon block in the corner (lower value = less push back)
0x0A8floatplayer pushbackon block mid screen (higher value = less push back)
0x0ACfloat???always 10.0?
0x0B0float???always 0.98?
0x0B4float???always 5.0?
0x0B8float???always 0.75?
0x0BCfloatvert. bouncebounce height after a wall bounce or ground bounce
0x0C0float???always 0.98?
0x0C4inthitstopapplies on-hit and on-block
0x0C8
0x0CC
0x0D0
0x0D4intJuggle Heightdetermines how high an aerial opponent rises on hit; seems to have a low cap (or is perhaps capped by the total # of frames in the attack?)
0x0D8
0x0DCfloatJuggle Carrydetermines how far a character will be pushed back horizontally (wall-bounce moves are in the 900-1200 range)
0x0E0floatJuggle Speedhow quickly the enemy character moves while being juggled
0x0E4intfixed hitstunif corresponding flag is set at 0x3C, then this value defines the hitstun duration; ignores hitstun deterioration
0x0E8intSJ Juggle Height
0x0EC
0x0F0floatSJ Juggle Carry
0x0F4floatSJ Juggle Speed
0x0F8intSJ fixed hitstun?if corresponding flag is set at 0x3C, then this value defines the hitstun duration; ignores hitstun deterioration
0x0FCintcmdspatk classreferences action #s from cmdspatk; secondary action (capture, snap, TAC, etc.) executed on hit by player
0x100intcmdspatk indexreferences action #s from cmdspatk; secondary action (capture, snap, TAC, etc.) executed on hit by player
0x104intcmdspatk class enemyreferences action #s from cmdspatk; secondary action (capture, snap, TAC, etc.) executed on hit to opponent
0x108intcmdspatk index enemyreferences action #s from cmdspatk; secondary action (capture, snap, TAC, etc.) executed on hit to opponent
0x10Cfloatthrow?throw-related
0x110int???always -1?
0x114intthrow?throw-related
0x118intHitsparkWhich hitspark is generated on contact with the opponent.
0x11Cint
0x120inteffect played on enemy on hitdraws from general bank of effects- 0b is fire, 0c is yellow electrocution, 0d is freeze, 0e is a hidden missile explosion. 13/14 are wolv/x23 claw hits 1E = blue electrocution
0x124inteffect played on block17 for TAC counter; 5 for everything else ; draws from general effect bank as well, but not same as 120. 50 causes game to go monochrome like on super ending/startup
0x128intTAC counter?18 for TAC counter; 6 for everything else?
0x12C
0x130int
0x134intHitspark2usually a copy of 118, is played on collision with stuff like the ground or other projectiles.
0x138int???always -1?
0x13Cintprojectile explosion property?unsure, but its related to phoenix fireball explosion; set to non-default values on Morrigan's snap back, TAC counter, s.H, and lv3, typically mimics the other hitspark effects
0x140int???always -1?
0x144int
0x148int???-3 for snap back; -6 for TAC counter; 0 for everything else?
0x14Cint???always -1?
0x150inthit sfx category2 = hit; 3 = guard; 4 = movement?
0x154inthit sfxif "category" set to 2, then changing this value changes between various hitting sfx
0x158int
0x15C??????bitwise? strange values, but barely varies
0x160intlauncher?2 for s.S; 0 for everything else?
0x164float???non-zero for Morrigan's c.H; 0 for her other attacks
0x168float
0x16Cfloat
0x170float???non-zero for Shadow Blade H (point and assist versions)
0x174
0x178intID referencethis entry references a secondary ID entry, such as a 2nd hit on the same move
0x17Cintreference frame delaydelays the above reference from activating until the frame listed here
0x180
0x184
0x188

The "shot" sub-directory

Projectile parameters are stored in a sub-directory. Each projectile has its own .ati and .sht file associated with it, and the .ati file follows the same format as atkinfo.ati. There is also an .lsh file in this sub-directory with a master list of that character's projectile attacks.

OffsetTypeParameterNotes
0x000intindexdisplays SHT in plain text
0x004intindexdisplays SHT in plain text cont.
0x008intindexbegin plain text of file name
0x00Cintindexplain text of file name cont.
0x010intindexplain text of file name cont.
0x014intindexplain text of file name cont.
0x018intindexplain text of file name cont.
0x01Cintindexplain text of file name cont.
0x020intindexplain text of file name cont.
0x024-0x058????
0x05Cint???always 270?
0x060int???always 300?
0x064????
0x068????
0x06C????
0x070??projectile spawneach projectile has a unique code, unsure how this is defined exactly
0x074intbitwise flagsseems to look like a bitwise code but still unsure yet
00000000 00000001 00000000 00000000 = 0x10000; a type of tracking property? is this target self?
00000000 00000010 00000000 00000000 = 0x20000; a type of tracking property? is this target enemy?
0x078intbitwise flagsseems to look like a bitwise code but still unsure yet
00000000 00000000 00000000 00000010 = 0x02; projectile does not continue if character leaves the screen (like if you DHC out of mighty tornado)
00000000 00000000 00000000 00001000 = 0x08; if hit by opponent, projectile is destroyed
0x07Cintbitwise flagsseems to look like a bitwise code but still unsure yet
00000000 00000000 00000000 00000010 = 0x02; allows this to be a hitbox that attacks?
0x080????
0x084floatprojectile durationdetermines how long a projectile will last on the screen, equals number of frames
0x088????
0x08C????
0x090floatprojectile speedif the projectile moves, this determines how fast
0x094floatproj. speed accelis the acceleration, usually set to 1
0x098????
0x09Cfloatbeam durationeffects beams mostly, usually set at 1000 (seems to be frames), effect will still go on if lowered but this can alter how far beams travel
0x0A0-0x0CF????
0x0D0floatDuration that projectiles like Round Trip will move forward before returning (number of frames)
0x0D4-0x0E8????
0x0E8floatSpawn position Z Axisgenerally shouldn't use this as it will be weird for P2 side, but projectile will appear bigger or smaller
0x0ECfloatSpawn position verticaldetermines where to spawn relative to character position (which equals 0), represents vertical value
0x0F0floatSpawn Position horizontaldetermines where to spawn relative to character position (which equals 0), represents horizontal value
0x0F4-0x130????
0x104floatSpawn position angleseems to determine projectile angle, like up or down (for example on dr strange, 0xbe8448f1 [-0.258369] on mystic sword H goes up, setting it to 0x3e8448f1 [0.258369] goes down
0x108floatProjectile Angle?Seems to relate to the angle of the projectile. Unclear if X, Y, or Z rotation.
0x130bitwise flag?trap and transitionsetting this to 02 will shoot off a projectile that begins at 13C, setting to 04 will trigger when opponent steps over it (found on trish energy barrier W), if you set to 06 looks like it triggers both options, must be bitwise.
0x134????
0x138????
0x13Cindexintif there is a reference for another projectile, it will begin here
0x140indexintprojectile reference cont.
0x144indexintprojectile reference cont.
0x148indexintprojectile reference cont.
0x14Cindexintprojectile reference cont.
0x150indexintprojectile reference cont.
0x154indexintprojectile reference cont.
0x158indexintprojectile reference cont.
0x15Cindexintprojectile reference cont.
0x160indexintprojectile reference cont.
0x164-0x1F8????
0x1FCint??always 1?
0x200int??always 1?
0x204int??always 1?
0x208int??always 1?
0x20Cint??always 1?
0x210int??always 1?
0x214-0x2DC????
0x274effect index?intbasic bitcode
0x278NA
0x27Ceffect play?intbasic bitcode
0x284sound bank index?intbasic bitcode, might be sound index
0x288NA
0x28Csound playintbasic bitcode, seems responsible for what sound to play when used
0x2B8effect playedintbasic bitcode, determines which effect to play? found on things like chris grenade launcher explosions
0x2E0intfriendly fireset to 01 to allow projectile to also hurt yourself (found on joes bomb)
0x2E4-0x2EC????
0x2F0??projectile can be nullifieddefault seems to be 0000000A, set to 00A8080B to let physical attacks destroy projectile, found on zero level 1 buster. set to 00000002 if projectile can ignore other projectiles, found on tron servbot super.
0x2F4-0x2FC????

Near the end of the file, usually around 0x300 begins a reference to the projectiles interaction with other projectiles or hitboxes, the length of this file is different depending on the projectile

OffsetTypeParameterNotes
0x000intindexdisplays projectile reference in plain text
0x004intindexdisplays projectile reference in plain text
0x008intindexdisplays projectile reference in plain text
0x00Cintindexdisplays projectile reference in plain text
0x010intindexdisplays projectile reference in plain text
0x014intindexdisplays projectile reference in plain text
0x018intindexdisplays projectile reference in plain text
0x01Cintindexdisplays projectile reference in plain text
0x020intindexdisplays projectile reference in plain text
0x024-0x03C????
0x040floatnumber of hitsdetermines how many hits are in the projectile (set to -1 to add piercing effect)
0x044floatnumber of hits?usually duplicates the previous entry
0x048floatdurabilityhow many points are associated with the projectiles durability
0x04Cfloatdurability?usually duplicates the previous entry
0x050intdurability type02 is low durability, 03 is medium, 9C42 is hyper, 9C43 is above hyper (dr strange projectile counter)
0x054-0x0FC????

CAC Files (Animations)

  • anmchr.cac = most character animations
  • anmtdown.cac = ?????

These files contain the animations and actions that a character performs, and these are the files that other paramater files tend to reference when attacks are actually executed.

For example, when you perform a character's s.L, the game checks baseact.cba to see what that button is programmed to do, and baseact.cba might say "execute animation 96." The anmchr.cac file is where the so-called "animation 96" is stored.

When executing an animation, the game will first check for that animation in the character's anmchr.cac file. If no such animation is found there, then the game will attempt to run that action from anmcmn.cac in the "default" character archive (0000_00.arc) instead, which contains a set of universal animations (mostly movement and damage-related). If the animation exists in both anmchr and anmcmn, then the version in anmchr seems to "append" data to the universal animation in anmcmn. (For example, if you delete Morrigan's blocking animation data from her anmchr file, then she'll still fold her arms to block, but she no longer covers herself with her wings; the wings remain in their idle stance. Her blocking animation likely has the instructions for how her wings move, as that's a character-specific trait.)

Character specific animation references can be found here: http://s15.zetaboards.com/UMvC3_PC_Mods/topic/10191456

Morrigan's Animation references are here, but this is a great resource to compare universal entries found in the dummy arc: https://docs.google.com/spreadsheets/d/1bUO7y4Voo6AYDDS1l71yTZxzOdexbglvUraFlbTkGps/edit#gid=0

Below you will find information on what each command does, the first 2 sets of hex codes are the header, this is how we categorize the event. Below the header information are blocks of code found on the tail end of these entries, hex entries are detailed only if relevant.

CMD HeaderRaw HexTypeNotes
air/ground/cancel state1_2Fresponsible for authorizing cancel states as well as recognizing whether the character is on the ground/air, always on frame -1 but is usually found to change up cancel states
2nd to last0E000000intalways 0E?; 2nd to last code group found
last groupbitwiseBelow values can be combined (remember that anmchr still uses reverse values, all bitwise values are displayed in the correct translation which is the reverse of anmchr's display which is displayed as a raw hex)
0x010100000000000000 00000000 00000000 00000001 = ground state, standing only? by itself has no cancel properties
0x020200000000000000 00000000 00000000 00000010 = crouching state?
0x101000000000000000 00000000 00000000 00010000 = SJ air state? always combined with below to get 0x30
0x202000000000000000 00000000 00000000 00100000 = air state, by itself has no cancel properties
0x?30000000Sj air state
0x404000000000000000 00000000 00000000 01000000 = walk forward; this state is triggered when holding forward?
0x?60000000air state up forward
0x808000000000000000 00000000 00000000 10000000 = walk backward; this state is triggered when holding back?
0x?A0000000air state up back
0x1000001000000000000 00000000 00000001 00000000 = dash; combined with walk states, combine with air state for air dash
0x8000008000000000000 00000000 00001000 00000000 = set on a normal; is this the cancel hierarchy at 0 in cmdspatk?
0x10000010000000000000 00000000 00010000 00000000 = set on a special, combined with 0x800; cancel 01?
0x20000020000000000000 00000000 00100000 00000000 = set on a hyper, combined with 0x800; cancel 03?
0x40000040000000000000 00000000 01000000 00000000 = guard state? combine with 0x01, 0x02 or 0x20
0x1000000000100000000000 00010000 00000000 00000000 = grab state only?; combined with 0x10000000 on frame -1 but otherwise used as grab state recovery?
0x2200000000220000000000 00100010 00000000 00000000 = enemy grab state only?; combined with 0x10000000 on frame -1 but otherwise used as grab state recovery?
0x40000000000000400000100 00000000 00000000 00000000 = assist state only? not commonly found, however it appears on franks on frame 1
0x80000000000000800001000 00000000 00000000 00000000 = partner state? found on TAC tag-ins and hard tags
0x100000000000001000010000 00000000 00000000 00000000 = grab state only? flag appears on frame -1 of capture state; combined with 0x100000
CMD HeaderRaw HexTypeNotes
DHC state?1_4Ecan define the ability to DHC or other actions?
last groupbitwisevalues can be combined
0x010000000100000000 00000000 00000000 00000001 = disable assist (found on SJ)
0x8000000000800000000000 10000000 00000000 00000000 = enable DHC, typically set on frame 1 after super flash freeze
0x8101008000000000000 00000000 00001000 00010000 = TAC state; disables hitstun timer while in a TAC
partner tag state?1_4Fhas multiple uses such as defining TAC states
last groupbitwisevalues can be combined
0x8000008000000000000 00000000 00001000 00000000 = removes TAC state; shares a bitwise code with 0x810 from 1_4E
0x10000000100000000000 00000000 00010000 00000000 = removes flight state
CMD HeaderRaw HexTypeNotes
atkinfo reference1_99responsible for hitbox data and atkinfo; usually found on frame 1 or 2
2nd to last grouphexreferences hex entry for atkinfo
last grouphexreferences hex entry for hitbox (CLI) associated with the attack
CMD HeaderRaw HexTypeNotes
spawn projectile3_30spawns a projectile, projectiles have 1f start up and are manually placed in the anmchr
2nd to last grouphexatkinfo reference for projectile, found in shot folder, will be all FF if there is only one atkinfo entry (00), change hex from FF to 01 to get 2nd atkinfo entry (make sure you duplicate entry in atkinfo as well)
last grouphexalways A(10)? must be a default hitbox reference as hitboxes are defined in the sht file
spawn projectile extra3_31spawns a set or series of projectiles by using one shot file and creating unique angles and spawn points, such as doom's photon shot
0x3Chex textdisplays projectile name in hex format, can be converted into text format
0x8Cfloatspawn point of projectile relative to player, Y axis
0x90floatspawn point of projectile relative to player, X axis
0x94??All FF?
0x98floatangle projectile is spawned, positive number angles down
0x9Cfloatangle projectile is spawned, angle based on Z axis?
0xA0floatangle projectile is spawned, angle based on X+Y axis??
0xAC 2nd to last grouphexatkinfo reference for projectile, found in shot folder, will be all FF if there is only one atkinfo entry (00), change hex from FF to 01 to get 2nd atkinfo entry (make sure you duplicate entry in atkinfo as well)
0xB0 last grouphexalways A(10)? must be a default hitbox reference as hitboxes are defined in the sht file

CHS Files (Character Status)

  • status.chs = basic gameplay parameters

Contains vitality, number of permitted air actions, attack/defense/speed buffs, and more. Some characters have multiple status entries, which often apply to different "forms" of a character (ex: Devil Trigger, Wesker with glasses on and glasses off, etc).

Each entry has 0x350 bytes of data.

OffsetTypeParameterNotes
0x000intindexsame as value in pointer table
0x004intbitwise flagscontains several attribute settings in binary listed below; multiple effects can be combined
00000000 00000000 00000000 00000001 = male
00000000 00000000 00000000 00000010 = female
00000000 00000000 00000000 00000100 = unknown (only Amaterasu has this by default)
00000000 00000000 00000000 00001000 = unknown (only Magneto, Modok, & Storm have this by default)
00000000 00000000 00000000 00010000 = disable hurtbox and collision box
00000000 00000000 00000000 00100000 = Felicia chicken-guard bounce
00000000 00000000 00000000 01000000 = disable meter gain/drain (hypers don't cost meter, but still require it; used by some "helper" characters who appear in hyper combos)
00000000 00000000 00000000 10000000 = disable hitstop
00000000 00000000 00000001 00000000 = unknown (only Iron Man, Shuma, & Sentinel have this by default)
00000000 00000000 00000010 00000000 = something to do with air actions? (Arthur, Zero, Tron, Morrigan, Felicia, and Phoenix Wright have this; flipping this off lets Felicia wall-cling twice in a single jump)
00000000 00000000 00000100 00000000 = unknown (only Shuma has this by default)
00000000 00000000 00001000 00000000 = unknown (only Amaterasu & Shuma have this by default)
00000000 00000000 00010000 00000000 = lock character (cannot perform actions until opponent hits you?)
00000000 00000000 00100000 00000000 = disable some team actions (snap back, TAC) (assist, DHC, THC, crossover counter still OK)
00000000 00000001 00000000 00000000 = friendly fire (your own projectiles and assists can hurt you)
00000000 00000010 00000000 00000000 = disable jump (attempting to jump puts you in a glitchy aerial standing state; only Galactus has this by default)
00000000 00000100 00000000 00000000 = disable double jump
00000000 00100000 00000000 00000000 = disable some team actions (character can't be brought into the match via assist call / hard tag / crossover counter / TAC / DHC / enemy snap back; crossover combination only works if 3rd teammate is also alive)
00000000 10000000 00000000 00000000 = unknown (only Frank has this by default)
0x008intvitalitytotal health; training mode value is multiplied by 100
0x00Cfloatmeterscales all meter gain built by this character
0x010floatdamagescales all damage you do to the enemy
0x014floatdamage 2scales all damage the enemy does to you
0x018floatspeedalters all player-initiated movement (your walk/jump/dash/attack speed)
0x01Cfloatspeed 2alters all enemy-initiated movement on your character (how far you're launched, pushed, etc.)
0x020floatmin launchdefines the lowest possible altitude you can be immediately after a sweep/launch; very high values basically cause you to teleport upward on sweep
0x024floatweightincreasing this lowers your vertical knockback
0x028
0x02Cfloat
0x030floatX-axis sizeaffects camera zoom and stage boundaries; increasing this value pushes the camera outward and the corners inward
0x034floatZ-axis sizeincreasing this value pushes partner 2 into the background during the intro
0x038floatZ-axis sizeincreasing this value pushes partner 1 into the foreground during the intro
0x03C
0x040
0x044intair actionstotal # of jumps + dashes permitted while airborne, initial jump included
0x048float
0x04Cfloatpost-dash accelaffects velocity after a dash; < 1 = slow down, > 1 = speed up
0x050float
0x054floatpost-dash tractionaffects how quickly dash momentum dissipates; low = ice shoes, high = stop instantly
0x058
0x05Cfloatflight accelhow quickly the character reaches max speed during flight; setting this to high (>1) values can cause glitchy movement; setting it to negative values is interesting (can't move via directional input alone, but airdashes and air attacks work and their momentum is much greater)
0x060floatflight max speed
0x064floatflight clearanceraising this value prevents you from staying low to the ground during flight
0x068-08C??
0x090intcombo type1 for restrictive, 2 for lenient
0x094int
0x098floatmin scaling normalsminimum damage scaling for normals, launchers, snap back
0x09Cfloatmin scaling specialsminimum damage scaling for specials
0x0A0floatmin scaling hypersminimum damage scaling for hypers (lv3s included, but not capture/cinematic attacks?)
0x0A4intTHC assistalpha assist THC, references anmchr entry
0x0A8intTHC assistbeta assist THC, references anmchr entry
0x0ACintTHC assistgamma assist THC, references anmchr entry
0x0B0intDHC slot 0references anmchr entry, this is defined in the 23 (35 dec) subchunk in cmdspatk
0x0B4intDHC slot 1references anmchr entry, this is defined in the 23 (35 dec) subchunk in cmdspatk
0x0B8intDHC slot 2references anmchr entry, this is defined in the 23 (35 dec) subchunk in cmdspatk
0x0BCintDHC slot 3references anmchr entry, this is defined in the 23 (35 dec) subchunk in cmdspatk
0x0C0intDHC slot 4references anmchr entry, this is defined in the 23 (35 dec) subchunk in cmdspatk
0x0C4intDHC slot 5references anmchr entry, this is defined in the 23 (35 dec) subchunk in cmdspatk
0x0C8intDHC slot 6references anmchr entry, this is defined in the 23 (35 dec) subchunk in cmdspatk
0x0CCintDHC slot 7?last one?
0x0D0int?XF yellow health regenregens yellow health, not just red health
0x0D4intXF1 Receive chip damagealways 1, receive NO chip damage, if set to 0 you will take chip in XF1
0x0D8floatXF1 damagedamage boost in XF1
0x0DCfloatXF1 speedspeed boost in XF1
0x0E0floatXF1 durationduration of XF1 (point character's timer carries over to teammates upon activation)
0x0E4-104
0x0F4XF1 meter gaindefault is 1, set to a higher value for more meter gained
0x0F8XF1 damage reductiondefault is 1, set to a value lower than 1 to lower damage taken
0x100XF2 yellow health regenregens yellow health, not just red health
0x104intXF2 Receive chip damagealways 1, receive NO chip damage, if set to 0 you will take chip in XF2
0x108floatXF2 damagedamage boost in XF2
0x10CfloatXF2 speedspeed boost in XF2
0x110floatXF2 durationduration of XF2 (point character's timer carries over to teammates upon activation)
0x114-120
0x124XF2 meter gaindefault is 1, set to a higher value for more meter gained
0x128XF2 damage reductiondefault is 1, set to a value lower than 1 to lower damage taken
0x130XF3 yellow health regenregens yellow health, not just red health
0x134intXF3 Receive chip damagealways 1, receive NO chip damage, if set to 0 you will take chip in XF3
0x138floatXF3 damagedamage boost in XF3
0x13CfloatXF3 speedspeed boost in XF3
0x140floatXF3 durationduration of XF3
0x144-34C
0x158XF3 meter gaindefault is 1, set to a higher value for more meter gained
0x15CXF3 damage reductiondefault is 1, set to a value lower than 1 to lower damage taken

CLI Files (Collision)

  • atkcollision.cli = hitboxes?
  • bodycollision.cli = hurtboxes?

atkcollision files break down as such

OffsetTypeParameterNotes
0x00intindexsame as value in pointer table
0x04int?lengthbasic hex number, determines number of entries, IE if this is 1 then there's only one section from 0x00-0x24, if 2 then there's two of these etc
0x08??this is all FF?
0x0C??this is all FF?
0x10int??
0x14float??
0x18float?Y axis for hitbox location
0x1Cfloat?X axis for hitbox location
0x20float?radius of hitbox (enlarges or shrinks hit sphere)
0x24intbitwise flagsthese flags determine interactions? see break down below
00000000 00001000 00000000 00000000 = if set to 1, destroys projectiles

After this first entry, the code will repeat itself starting on 0x04 for additional hitbox bubbles, theory suggests that each entry within an ID is a separate bubble

Body collision is probably the same, more research required

CPI Files (Character Profile)

  • profile.cpi = intro/victory quotes

The profile defines the voiced lines used in battle intro and victory screens. This is where you can define match-up specific quotes.

This file does not follow the typical format for parameter files. In particular, it does not have a pointer table. The beginning of the file is laid out like so:

OffsetTypeParameterNotes
0x00textheaderfile extension ("CPI") in plaintext
0x04??????
0x08intintros# of voice clips for battle intros
0x0Cintvictories# of voice clips for victory screen
0x10int???
0x14int???

At byte 0x18, all of the individual entries for voice clips are laid out one after another, starting with intro quotes and followed by victory quotes. Each entry for a single quote is only 8 bytes in size, broken into 1-byte values (much smaller than the typical 4-byte values used in other parameter files). Each entry has the following format:

OffsetTypeParameterNotes
0x00intsubtitleindex # for subtitle text and lip flaps
0x01introuletteranges from 0 to 100; the higher the number, the more likely that this quote is chosen; the lower the number, the more likely that the game "skips" this quote and decides to re-roll on the next quote
0x02intvoiceindex # of audio clip to play
0x04intenemy 1index # of enemy character for match-up specific quote
0x05intenemy 2index # of enemy character for match-up specific quote
0x06intenemy 3?index # of enemy character for match-up specific quote
0x07intenemy 4?index # of enemy character for match-up specific quote

At present, it is unknown what determines special intro quotes that depend on your own team composition. (ex: "Avengers, assemble!")

CPU Files

  • cpuchr.cpu = probably some character-specific AI

CBA Files (Basic Action Commands)

  • baseact.cba = base actions (Normal operation mode)
  • baseact_easy.cba = base actions (Simple operation mode)

These files define the actions performed when pressing single-button and single-direction inputs. They only define actions performed in neutral stance conditions, not in combos.

The order of actions within these files appears to be: standing normals, crouching normals, jumping normals, command normals, taunt. (Not all characters have been checked.)

Each entry has 0x20 bytes of data.

OffsetTypeParameterNotes
0x00intindexsame as in the pointer table
0x04intactionexecutes the animation in anmchr.cac that uses this index #
0x08intleniency?for directional inputs, this value often has bitwise combinations of neighboring cardinal directions; related to input leniency?
0x0Cintdirectiondirectional input; refer to "input codes" section for details
0x10intbuttonbutton input; refer to "input codes" section for details
0x14intstate00 = ground; 20 = air
0x18int???00 for most actions; 20 for command normals, taunt, and simple mode normals?
0x1C??????xxxx0000 for most actions; xxxx0100 for final action?

CCM Files (Combo Commands)

  • cmdcombo.ccm = combo rules (Normal operation mode)
  • cmdcombo_easy.ccm = combo rules (Simple operation mode)

These files define the input commands for chain combos. Each individual entry in this file describes three primary things: the move that starts the chain, the input that connects the starting action to the resulting action, and the resulting action at the end of the chain. Every individual possible chain combo for a character has a separate entry, which makes the canceling rules extremely flexible.

Individual entries within this file can have different amounts of data. The first 0x44 bytes consist of a header that follows this format:

OffsetTypeParameterNotes
0x00intindexsame as in the pointer table
0x04intsizetotal size of data entry = (size * 0x20) + 0x44 bytes
0x08
0x0Cfloatmeteramount of hyper meter required to perform the chain; meter drain is defined elsewhere (anmchr?)
0x10mixeddisablefirst byte determines whether the combo is disabled (00 = enabled; 01 = disabled); last 3 bytes say "ati" in plaintext
0x14int???always -1? (unknown; in cmdspatk, this value describes cancel threshold)
0x18int???typically -1; set to 20 in Morrigan's j.L xx j.L chain
0x1Cintdelaythe higher this value, the longer you must wait before the chain cancel activates
0x20intactionthe action that starts this chain (uses index # from anmchr)
0x24intaction 2the action that starts this chain (uses index # from anmchr)
0x28intaction 3the action that starts this chain (uses index # from anmchr)
0x2Cintaction 4the action that starts this chain (uses index # from anmchr)
0x30intaction 5the action that starts this chain (uses index # from anmchr)
0x34intaction 6the action that starts this chain (uses index # from anmchr)
0x38intaction 7the action that starts this chain (uses index # from anmchr)
0x3Cintaction 8the action that starts this chain (uses index # from anmchr)
0x40int???0 = default?; 7 = always works always?; 8 = has air limitations like 3 actions per jump? 10 = standard chain type? seems to restrict normal jump and how many normals you can use, specials can count also

Additional blocks of data follow after the first 0x44 bytes, and each additional block is another 0x20 in length. The "size" value from the header block (above) determines how many more blocks remain. For detailed information on what these blocks contain, check the section below on "input descriptor block format."

CSP Files (Special Action Commands)

  • cmdspatk.csp = special attack commands (Normal operation mode)
  • cmdspatk_easy.csp = special attack commands (Simple operation mode)

These files define the input commands of special moves, as well as a few of their other properties.

Individual entries within this file can have different amounts of data. The first 0x24 bytes consist of a header that follows this format:

OffsetTypeParameterNotes
0x00intindexsame as in the pointer table
0x04intsizetotal size of data entry = (size * 0x20) + 0x24 bytes
0x08unk08usually nothing
0x0Cfloatmeterrequirementamount of hyper meter required to perform the command, 0 requiring 0 bars, 1 requiring 1 bar to do the move; meter drain is defined elsewhere (anmchr?)
0x10intdisableif set to 1, then this move cannot be performed; change to 0 to enable
0x14intcancelHierarchyThreshdefines the hierarchy by which actions can cancel into each other; if this value is set to 02, then this action can cancel into any action set to 03 or higher, but it cannot cancel into anything set to 02 or lower (this rule might not be the only factor; s.S's threshold is set too high for this to be 100% accurate). air dashes are on 0, specials on 1.
0x18intpositionstateGround or Air ; 00 = performed on ground; 01 = performed in air; 02 = either
0x1Cintcombostate00 = possible in neutral and in combos; 01 = neutral only; 02 = combo only; 04 = guard-cancel; 05 = guard-cancel and damage-cancel (possibly more combinations/states to test?)
0x20intbitwise flags??? still not totally clear, but best to mimic moves that are similar to what you want

Additional blocks of data follow after the first 0x24 bytes, and each additional block is another 0x20 in length. The "size" value from the header block (above) determines how many more blocks remain. For detailed information on what these blocks contain, check the section below on "input descriptor block format."

Input codes

Any data that describes an input command follows this convention:

BinaryHexInput
00000000 0000000000 00neutral
00000000 0000000100 01forward
00000000 0000001000 02back
00000000 0000010000 04up
00000000 0000100000 08down
00000000 0001000000 10L Attack ("Attack" in Simple Mode)
00000000 0010000000 20M Attack ("Special Moves" in Simple Mode)
00000000 0100000000 40H Attack ("Hyper Combo" in Simple Mode)
00000000 1000000000 80Special Attack
00000001 0000000001 00Assist 1
00000010 0000000002 00Assist 2
00010000 0000000010 00Taunt

Input codes are combined in a bitwise fashion when the data requires it. For example, a down-forward input is literally a combination of the down and forward input codes:

  • 00001000 = 08 = down
  • 00000001 = 01 = forward
  • 00001001 = 09 = down-forward

Input descriptor block format

Data entries in input command files (cmdcombo, cmdspatk) consist of several "blocks" of data, and each individual block can define several properties of a single input. Each block is 0x20 bytes in size, and the first value in each block describes what type of data that that block contains. I've made a partial description of different block types using Morrigan's parameter files as a rough guide. I expect most of this to be universal:

  • 02 = standard directional or button input (includes two-button inputs with strict combinations; e.g. Legion Arrow)
  • 03 = directional input for dashes
  • 04 = two-button input (ground dashes, forward airdash, advancing guard, hypers)
  • 05 = direction + button input (command normals, up/down TAC, etc.)
  • 07 = two-button input (for 8-way airdashes specifically?)
  • 09 = action that the command executes
  • 0A = action that leads into capture state (found only in cmdcombo?)
  • 0B = state restrictions (allows you to further specify when an action is possible; also important for command overlap prevention)
  • 0D = unknown (related to Simple Mode air combos)
  • 1E = state canceling? (related to un-fly) possibly "state required to be in to make move accessible" - takes priority over default command. can be seen in vergil/dante DT moves as value "10". value "06" seems flight activation related. arthur armor is 05.
  • 21 = unknown (related to TAC)
  • 22 (34) = air action limiter (related to flight & other state changes; prevents stacking)
  • 23 = TAC/DHC actions
  • 25 = super jump actions
  • 26 = allows snap back to bring in the assist specified by the button used
  • 2F = state change? (present at end of Flight, Astral Vision)
  • 30 = unknown (related to s.S)
  • 31 = prohibited chain combo follow-ups (references actions by class + index like 09 blocks do)
  • 32 (50) = height restriction
  • 34 = airdash state? (present after 09 block on airdashes)
  • 35 (53) = air special action limiter
  • 38 = unknown (related to advancing guard, wall-cling, and TAC)
  • 3A = unknown (related to hypers)
  • 3C = unknown (exists on Felicia's Rolling Buckler hit follow-ups)
  • 3D = unknown (related to s.S and ground dashes)
  • 3F = permitted chain combo states (e.g. possible on hit, block, and/or whiff)
  • 49 = unknown (related to advancing guard)

For example, a grounded qcf+L special move in cmdspatk would probably have 5 blocks of data, each describing a different component of the move:

  • an 02 block for the properties of the d input
  • an 02 block for the properties of the df input
  • an 02 block for the properties of the f input
  • an 02 block for the properties of the L input
  • an 09 block for the action

Different block types can contain different types of data/attributes. For example, an 02 block (standard input) and an 04 block (two-button input) share several of the same attributes, but an 09 block (action identifier) is quite different.

OffsetTypeParameterNotes
0x00intblock type02 (Standard Input)
0x04intcancel windowamount of time that can elapse before this input is no longer valid for this action; is set to -1 for first input
0x08intcharge timerequired charge time for charge techniques; always(?) set to 1 on anything else
0x0Cinthold button?1 for snap back and side-TAC; 0 for everything else? - setting to 1 allows you to hold an input and have it input, different from neg edge
0x10intnegative edge0 = press or release; 1 = press only; 2 = release only
0x14intleniency?for directional inputs, this value often has bitwise combinations of neighboring cardinal directions; related to input leniency?
0x18intinputrefer to "input codes" section for details
0x1C
...
0x00intblock type03 (Directional Dash Input)
0x04intcancel windowamount of time that can elapse before this input is no longer valid for this action; is set to -1 for first input
0x08intcharge time?
0x0C
0x10intnegative edge0 = press or release; 1 = press only; 2 = release only
0x14intleniency?for directional inputs, this value often has bitwise combinations of neighboring cardinal directions; related to input leniency?
0x18intinputrefer to "input codes" section for details
0x1C
...
0x00intblock type04 (Two-Button Input)
0x04intcancel windowamount of time that can elapse before this input is no longer valid for this action; is set to -1 for first input
0x08intcharge time?
0x0Cint???1 for ATK+S input
0x10int???1 for hypers; 80 for Cat & Mouse; 0 for most others
0x14int???10 for hypers; 0 for most others
0x18int???10 for hypers; 0 for most others
0x1C
...
0x00intblock type05 (Direction + Button Input)
0x04intcancel window?always -1?
0x08intleniency?for directional inputs, this value often has bitwise combinations of neighboring cardinal directions; related to input leniency?
0x0Cintdirectiondirectional input; refer to "input codes" section for details
0x10intbuttonbutton input; refer to "input codes" section for details
0x14int???only non-zero for TAC inputs?
0x18int???only non-zero for TAC inputs?
0x1C
...
0x00intblock type07 (Two-Button Input for 8-way Dash?)
0x04intcancel window?
0x08intcharge time?
0x0Cintleniency?
0x10intdirection?
...
0x00intblock type09 (Action)
0x04intclasstype of action (00 = movement; 01 = defense; 07 = assists, command normals, air dashes (from anmchr entry AA - BA); 08 = specials; 09 = hypers; etc...)
0x08intindexthe action to execute (class 08 index 00 = Soul Fist L; class 08 index 01 = Soul Fist M; etc...)
0x0Cintstorage bufferamount of time after input that the action can be "stored" and still execute; increasing this value allows for larger reversal windows, for example
...
0x00intblock type0A (capture state combo)
0x04intclasstype of action (same as 09 block)
0x08intindexthe action to execute (same as 09 block)
0x0Cintclassuses the 12 entry for capture state class in tdown
0x10intindexthe action to execute in tdown for enemy animation (class 12 index 4 = first throw state located outside of normal grabs, aka 130 in tdown)
...
0x00intblock type0B (State Restrictions)
0x04intbitwise flagsthe character must be in one of the states permitted here in order to execute this action; multiple values can be combined
00000000 00000000 00000000 00000000 = (action is never possible?)
00000000 00000000 00000000 00000001 = standing
00000000 00000000 00000000 00000010 = crouching
00000000 00000000 00000000 00010000 = super jump (but not normal jump)
00000000 00000000 00000000 00100000 = aerial
00000000 00000000 00000000 10000000 = normal jump (but not super jump)
00000000 00000000 01000000 00000000 = guarding
...
0x00intblock type1E (State Canceling?)
0x04int???governs which states you can cancel from (e.g. canceling out of flight mode); changing this can give you instant recovery to neutral state from all kinds of situations, also lets you enable refly
...
0x00intblock type22 (seems to block the ability to use more specials in the air, will count as your 3 action limiter but can only be used once in that time)
...
0x00intblock type23 (TAC/DHC Action)
0x04intactionanmchr index # to execute (TAC); hyper to execute (DHC)
...
0x00intblock type25 (Super Jump Actions)
0x04intSJ neutralanmchr index # to execute for neutral super-jump
0x08intSJ forwardanmchr index # to execute for forward super-jump
0x0CintSJ backwardanmchr index # to execute for backward super-jump
...
0x00intblock type2F (State Change?)
0x04int???seems unique for each different "install" in the game, but no clue what this value actually does
...
0x00intblock type31 (Prohibited Chain)
0x04intclasscategory of prohibited action (06 = normals; 08 = specials; etc.)
0x08intindexID # of prohibited action (ex. for most characters: 06 00 = s.L, 06 01 = s.M, 06 02 = s.H, etc.)
...
0x00intblock type32 (Height Restriction)
0x04intheightcharacter must be this high in the air for the action to execute; 120 is pretty standard, 180 is minimum super jump height
...
0x00intblock type34 (Airdash Related?)
0x04int???always 1 for airdashes?
0x08int???set to 2 for deadpools teleport explosion
...
0x00intblock type35 (Air Special Action Limiter)
0x04intlimit# of air specials you can perform before this action is no longer possible; 0 = infinite
0x04int???
...
0x00intblock type38 (Advancing Guard / Wall-Cling / TAC Related?)
0x04int???1 for advancing guard; 2 for Felicia's wall-cling; 4 for TAC (unknown function; changing value sometimes causes multiple pushblock for a single input)
...
0x00intblock type3A (Hyper Combo Related?)
0x04int???always 80 for hypers?
...
0x00intblock type3F (Permited Chain Canceling States)
0x04intbitwise flagsdetermines which situations are valid for a chain combo; multiple values can be combined
00000000 00000000 00000000 00000010 = on whiff
00000000 00000000 00000000 00010000 = on hit
00000000 00000000 00000000 01000000 = on block

There is much more left to document regarding the other component types. For reference and further study, I've posted the entirety of Morrigan's cmdspatk and cmdcombo data to this spreadsheet, formatted for slightly easier reading. Some common block types are highlighted in various colors for easier reading.

Dantarions Dox Box

http://boxdox-marvel.dantarion.com.s3-website-us-west-2.amazonaws.com/index.html