Right, so you don't want actions as such, but the addresses of actions, to see which are valid?
How are you going to read sprite behaviors? (Not actions, the stuff with speeds, jump heights and such) They have action addresses in them that are never wrong and you can then just get further addresses from the next action address.
Keen 4-6 Action Format
Yeah, maybe, but to be honest I'm basing all the action read stuff on the action.doc.
I'm not sure how keen actions change in the other episodes, but having the base address, I think it's enough to get the sprites moved.
About the other values like jump height, speeds and such I was planning to hardcode them as in Keen 1-3, but if you have a better method to read them I'm open to a better idea...
I'm not sure how keen actions change in the other episodes, but having the base address, I think it's enough to get the sprites moved.
About the other values like jump height, speeds and such I was planning to hardcode them as in Keen 1-3, but if you have a better method to read them I'm open to a better idea...
Whelp, Keen actions are pretty much the same beetween all episodes, with a few small alterations such as Keen mooning or the neat Keen-on-platforms pose. They're even in the same order. (1st action: Keen standing still, 2nd is Keen looking up when bored...) So hard-coding may help you there.
A lot of sprite properties are set on spawn or in behavior, and it's actually quite possible to scan code for the variables, if you know where a sprite's stuff is located. For example, in Keen 5, $C7 $07 appears before a sprite's type (See $1061E which sets the platform's type as 6, or 'can be stood on') I have a list for Keen 4-6 for the various tell-tale code bits for things like 'forground beh' 'change h-velocity' and 'change direction' I don't know if it'd be easier than hard-coding though.
A lot of sprite properties are set on spawn or in behavior, and it's actually quite possible to scan code for the variables, if you know where a sprite's stuff is located. For example, in Keen 5, $C7 $07 appears before a sprite's type (See $1061E which sets the platform's type as 6, or 'can be stood on') I have a list for Keen 4-6 for the various tell-tale code bits for things like 'forground beh' 'change h-velocity' and 'change direction' I don't know if it'd be easier than hard-coding though.
Remember that some directions are random. (Quite a few actually, I have a list.)
I'm not quite sure what you mean by 'table' but I have a list of the locations of the sprite actions for Keen 4-6, and also the Patch Index has an 'action list' which gives the AZ value of every default action and what that action is for.
I'm not quite sure what you mean by 'table' but I have a list of the locations of the sprite actions for Keen 4-6, and also the Patch Index has an 'action list' which gives the AZ value of every default action and what that action is for.