Unregistered
|
Members · 164 posts · joined 26-November 07
It's sprite data time!
This has 188 entries, and starts even and ends odd. This is WIP, so I don't know everything yet. But I know the most important factors to it.
The other thing is that depending on whether it's an item, an enemy or a projectile, some numbers may be used for DIFFERENT THINGS (ex. what I call a timer for one enemy, might control the angle of the spinning on something like the holy book). So you basically have to study the enemy that you want to change a little. But some basic things like action, speed, dmg, frame and frametimer, etc. are always used the same way.
Anyways, on with the show!!
SHORT hmovement- for some things (like skeletons) this affects how fast they move left and right... for
others it does nothing. This is the BEST way to increase Alucard or Richters speed.
SHORT hpos- the horizontal pos on screen... for enemies this is relative to the player
SHORT vmovement- same as hmovement, but for the vertical aspect.
SHORT vpos- vertical pos on screen. For enemies relative to player
LONG hspeed- your horizontal movement speed (- = left, + = right)
LONG vspeed - vertical movement speed (- = up, + = down)
SHORT hoffset- where the center of your sprite is horizontally;
SHORT voffset- where the center of your sprite is vertically;
SHORT dirfacing- direction facing; 1=left, 0 = right.
SHORT color = the colorpal used;
SHORT transp; enables transp (different #'s = different transparency amounts... try 40, 10 & 100), enables hwidth & vwidth below (values 256 & 512... 768 = both), & rotation BELOW (1024). These values CAN be combined to enable them all at once. Keep in mind, in the case of hwidth & vwidth below... 256 is normal... if at 0 the sprite WILL be invisible!
SHORT hwidth; horizontal size of sprite (graphically, 256 = normal)
SHORT vwidth; vertical size of sprite (graphically, 256 = normal)
SHORT anglesmall; angle of rotating items
SHORT UNKNOWN
SHORT UNKNOWN
SHORT Imagepriority; (notice how somethings graphically overlap others... this determines that. Higher number= more priority over other images. So an image with 120 here will graphically overlap an image with 100 here if they occupy the same space)
SHORT sprite1; //what is created, enemy, item, weapon, etc.
LONG sprite2; //what is created, enemy, item, weapon, etc.
SHORT action1- what action is being taken by the item/enemy (atk, spawn, die, etc.)
SHORT action2- some actions have 2 parts to the (ex. start to attack, attack, recover from attack)
BYTE itemnum1- what items spawns, what color you blink or the ring is etc.
BYTE itemnum2- usually = 128 or 0... for items 256-258, this would be 129 or 1.
SHORT UNKNOWN.
SHORT SPECIAL- same as stopwatch effect/axe bounces off for the MONSTER struct above
//NOTE: these next TWO entries have multiple uses such as does enemy move when map is up, will it UNSPAWN if you go far enough away from it, etc. I will notate this stuff later.
BYTE SHOWSDMG- when orb is present an enemy is damaged... does it show how much?
BYTE. SHOWSNAME- when faerie scroll is present... does enemies name show up
SHORT UNKNOWN.
SHORT canbehit1; // mostly used for players sub weapon attacks... notice how if you throw 2 boomerangs with richter, even if both overlap the enemy only one hits.... that's because the # here is the same for both of them. Buit if the numbers are different, then they would BOTH hit. Get it?)
UPDATE!FOR ENEMIES THIS IS THE # OF THE ENTRY IN THE LONG LIST OF ENEMIES ABOVE WHERE IT'S EXP AND STRONGTO/WEAKJ TO ETC. DATA IS GOTTEN FROM. AXE KNIGHT IS #6, AXE KNIGHT AXE IS 7 AND SO ON.
SHORT canbehit2; //same as canblock entry for MONSTER struct above. for player weapons 32 means hit enemy but not candles, 4=blocks projectiles, 2 = dmg enemies & candles
SHORT hp- ummmm. doy. lol
SHORT dmg- dmg amount if any
SHORT dmgtype; //type of element dmg attack does
SHORT UNKNOWN
BYTE hrange; //range that touching sprite does damage to you or enemy, increase goes further LEFT
BYTE vrange; //vertical range of sprite
SHORT pain; changes when enemy goes into pain animation. Can be frozen with code so that enemy NO LONGER goes into pain animation.
SHORT UNKNOWN
SHORT actiondata; //determines image set used for current actions
SHORT UNKNOWN
SHORT frame- the current frame the sprite is in
SHORT frametimer- how long till it changes to the next frame (counts down)
SHORT frameset- what set framepics are pulled from
SHORT framepic- current pic being used (if you want to change this, find the number in memory in the
700000+ range and do it there. It's very effecient.)
SHORT hitstun- how much stun the moves does
SHORT frameset2- has to do with centering the framepics used
SHORT UNKNOWN
SHORT UNKNOWN
SHORT UNKNOWN
SHORT UNKNOWN
SHORT UNKNOWN
SHORT UNKNOWN
SHORT UNKNOWN
SHORT hitscandles; //1=yes, 0 = no (for player things only)
SHORT transp2; //amount of transparency for some things, like richters dust
SHORT UNKNOWN
SHORT UNKNOWN
SHORT UNKNOWN
SHORT UNKNOWN
SHORT UNKNOWN
SHORT UNKNOWN
SHORT UNKNOWN
*NOTE: for the next few things below, use changes based on WHAT kind of sprite your messing with.
SHORT fadetimer; //used BY daggers to fade out {N/A on player sprite)
SHORT widthtimer; //used by holy book to control how far spinning extends out
SHORT timer2; //used by prism beam ITSELF to determine when beam fires
SHORT spinangle; //used BY holy book, determines what angle it spins at
SHORT timer3; //used by prism beam to determine how long till book opens up
SHORT UNKNOWN
SHORT UNKNOWN
SHORT UNKNOWN
SHORT UNKNOWN
SHORT UNKNOWN
SHORT blinkintensity; //used when richter is blinking to indicate how MUCH to show blinking
SHORT UNKNOWN
*NOTE: for these so called USERTAGS, I use these mostly as spaces for values I use to indicate certain
occurences on a sprite. Most of the time they are just zeros, but some things use some of them. Again
you will have to play around a little like I do.
SHORT usertag18;
SHORT usertag17;
SHORT usertag16;
SHORT usertag15;
SHORT usertag14;
SHORT usertag13;
SHORT usertag12;
SHORT usertag11;
SHORT usertag10;
SHORT usertag9;
SHORT usertag8;
SHORT usertag7;
SHORT usertag6;
SHORT usertag5;
SHORT usertag4;
SHORT usertag3;
SHORT usertag2;
SHORT usertag1;
SHORT ITEMDATA: in each area there is a certain value here for the set of items that include, hearts life max ups, etc.... and another value for the equipment set.
SHORT UNKNOWN
WHEW! That was a long one.. okay.... next I'm gonna find some of the memory ranges used by monsters for you guys:
But first:
Players range (richter OR alucard): 62a217- 62a2d2
Monster ranges- these don't respawn when killed, and there are a total of 96. The best way to find the enemy you are looking for is look up it's maxhp, search for it.... hit it, search for values decreased by whatever amount you hit for. Once you have the hp, just look below or subtract 3F(hex) to get the start of it's data.
HP found at = address range
Here are a few for you:
62dd16= 62dcd7-62dd92
62ddd2= 62dd93 - 62de4e
62de8e= 62de4f-62df0a
62df4a= 62df0b-62dfc6
62e006= 62dfc7-62e082
62e0c2= 62e083-62e13e
62e17e= 62e13f-62e1fa
62e23a= 62e1fb-62e2b6
62e2f6= 62e2b7-62e372
62e3b2= 62e373-62e42e
62e46e= 62e42f-62e4ea
62e52a= 62e4eb-62e5a6
62e5e6= 62e5a7-62e662
62e6a2= 62e663-62e71e
62e75e= 62e71f- 62e7da
62e81a= 62e7db- 62e896
62e8d6= 62e897- 62e952
62e992= 62e953- 62ea0e
62ea4e= 62ea0f- 62eaca
62eb0a= 62eacb- 62eb86
62ebc6= 62eb87- 62ec42
62ec82= 62ec43- 62ecfe
62ed3e= 62ecff- 62edba
62edfa= 62edbb- 62ee76
62eeb6= 62ee77- 62ef32
For enemies that RESPAWN (ex. stone rose, zombies) and projectiles, they start at 631798. Their seem to be about 64 of them but most are used for projectiles. And in rooms where you have spawning enemies, they seem to use only SOME of those addresses, and always the same ones. But again they are all in order.
This post has been edited by Esco: 19 January 2010 - 12:01 AM
|