| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
#3
|
| |
|
|
| |
It is no longer split into horizontal and vertical results. Also, the collision detection routine now does the work of calculating an adjusted position, instead of the caller (CharacterSystem) having to do it. This will be useful for #3.
|
| |
|
|
|
|
| |
Also made sprite hitboxes bigger.
#15
|
| |
|
|
|
|
| |
The whole function should probably be refactored at some point, possibly like therapy5's but that may be too complicated.
#14
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
TODO:
* all the animations are weird. we will need to have an adjustable framerate bc the climbing animation does not look right at the current rate. (also remove the manual animation stuff ig)
* does the medium stuff seem good and right? i am kinda not satisfied with it.
* running onto a ladder causes the characters to bunch up bc the movement speed is slowed down but the trails are not doubled
* no ladder running sound
* shadows should vanish while on a ladder
* uhh if you end a cutscene while on a ladder it resets the animation to "still" which is wrong. will this ever happen? idk
* adding a sprite to your party while you are on a ladder??
|
| |
|
|
|
|
|
|
| |
Because of an issue with how collision checking with sprites worked, it was possible that you could collide with a boundary twice (once when moving up to it, and once when moving from it to past it, instead of just one or the other) when moving up or left as long as the colliding sprite had the ID zero. This was causing a fun issue where the map change script from hallucination_interior to hallucination_cliff was getting triggered twice, but only every other time.
Because we're using integers and not real numbers, we can make the boundary exclusive by adding one. The issue was also technically possible in the down and right directions, but only if the sprite ID was INT_MAX, which is unlikely to occur.
It was decided that the former collision is the real one (if you start away from the boundary and then move into it).
|
| |
|
|
| |
A sprite with an enclosure zone will collide with it if it attempts to leave the area defined by the zone. This is used to make sure that wandering sprites don't end up in weird places.
|
| | |
|
| |
|
|
|
|
| |
The player party characters are now initialised at the start of the game and are no longer re-created after every map change. The script system takes care of moving the player into the correct position on the new map.
Deleted sprite IDs are now reused the next time a sprite is created, instead of throwing out everything between maps.
|
| |
|
|
|
|
|
|
| |
Sprites can be destroyed now, which really just means that their index is removed from the list of active sprites. The actual memory is not freed until all sprites are deleted on map change.
Sprite layers are introduced. All sprites by default are on layer 0 (Normal) which renders them in between the lower and upper map layers. There is also a layer 1 (Above) that renders above the upper map layer, and the sprite for the lightning strike uses this layer in order to not be hidden by the trees.
Fixed a bug where waiting for the end of a non-looping animation would trip the flag immediately upon the final frame activating, instead of waiting the length of the last frame.
|
| |
|
|
| |
This allows running off screen for a map transition to happen without bumping into something that isn't there.
|
| | |
|
| |
|
|
| |
Also removed some dependencies on the Renderer. More changes need to be made. Fading to black before the change would be good. And making sure the characters are facing the right direction. Maybe that code shouldn't live in Game, either. Later we also want to combine the tilesets for these two maps (and any others that are on Tanetane).
|
| |
|
|
| |
Walking into a trigger zone runs a script.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
