There are surely a lot of mistakes at the moment, so let me know if you find any! Level/Geometry
KLONOA DOOR TO PHANTOMILE KEYCHAIN CODE
It will never be complete (at least until it becomes detailed and accurate enough that someone could fully reconstruct something equivalent to the games original source code without having a copy of the game at all), but I'd like for it to be as accurate as possible. The remainder of this readme is an attempt to document as much information about how the game functions as possible, both as it relates to debugging/hacking tools and as it is of general interest. In most cases here, there doesn't seem to be a significant difference. This means that the value is possible to change as much as it wants within the span of a single frame. Freezing memory prevents the value from changing at all, whereas "locking" resets the value once every frame. Note that "locking" values currently works a bit differently than freezing memory the usual way in Bizhawk. This means it's pretty easy to die instantly to a "fall" death when trying to move around in the air. Note: click+drag functionality for moving Klonoa temporarily disables the kill timer for when Klonoa falls out of bounds, but not the kill planes that are deliberately placed around a level. This window is used for changing various aspects of the game state, with the aim of making it easier to explore the game by doing things that are impossible in the original game.
TODO actually document any of these features TODO x position along entire path, not just segment? Control window This is potentially useful for understanding situations in which the game fails to display these values properly in its on-screen HUD. Internal values for lives, health, and dream stones There are additional "special" planes, but they're not documented yet. In addition to displaying raw values, a couple of special/moving "planes" (currently limited to 3-1 gondolas and 5-1 moving platforms) are explicitly labeled as well. See "Level/Geometry" in the general notes below for an explanation of what these values represent. "Plane pointer," "Plane segment," and "X on segment" The value counts up from 0 to 5 if you see the value "5" remaining onscreen during a jump, this means you jumped on the last possible frame. The most noticeable effect is that Klonoa is able to jump during this time despite not touching the ground. Not fully documented/understood.Īfter stepping off a ledge, there is a five-frame window during which Klonoa's physics are different from usual. Unlike the above "status" value, this is a two-byte value stored next to the "ledge physics" value. invincibility frames after taking damage. 0x43434343) seems to rule this out.Ī counter that the game uses for tracking certain temporary effects, e.g.
It made me suspect that the status is actually be a two-byte (half word) value rather than a 4-byte, with the "facing forward" being part of a different variable, but the presence of clearly-intentional values that take up all four bytes (e.g. I have no idea why facing towards the camera has a unique value. Some of the possible states are identified, but there are a lot of other status values that are currently not labeled. This value tracks certain states, such as double jump, flying, etc. Could potentially be modified to create an auto-splitter for LiveSplit, or something.
Updates as soon as Klonoa is able to move when starting a vision. In-game HUDĮnabling the in-game HUD displays various pieces of information. This tool has two main components: a window with options for easily manipulating various aspects of the game state, and an in-game display that displays additional information about the game state.
0 kommentar(er)
