| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
| |
Since it's always the same ones anyway, might as well set defaults and allow them to be overridden.
|
| |
|
|
| |
This may happen due to lag or due to debugging with lldb. What happens is that 60 times a second, the engine will check whether the direction toward the current endpoint is equal to the direction in the pathfinding instruction, and if it isn't (because the sprite has gone past the endpoint) then it sets the sprite's position to the endpoint instantly so that the pathfinding can continue.
|
| |
|
|
| |
It's because the game's coordinate system has Y increasing downward, whereas the coordinate system used by the trig functions has Y increasing upward.
|
| |
|
|
|
|
| |
Looking pretty good so far.
TODO: direction facing functions have inverted Y coordinate. confusion expression doesn't exist yet. rest of scene.
|
| | |
|
| |
|
|
| |
The filenames for these are fairly regular, and we're gonna want to abstract it away further later on anyway.
|
| | |
|
| | |
|
| |
|
|
| |
(except when the debug console is open)
|
| | |
|
| |
|
|
| |
This allows common functions to be stored in not per-map script files. Which is useful for code that we're going to want in a lot of places -- i.e. how every underwater map is going to have a copy of the same exit area function.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Also spruced up the event that takes you there. Also fixed an issue where transplantParty wouldn't take the medium of the new position into consideration. Also added a constructor to the lua version of vec2i.
|
| | |
|
| | |
|
| |
|
|
| |
In the renderer, it's important to set the render target properly before any copying or drawing operations, especially if it's after a call to renderMessageLine, since that changes the render target.
|
| |
|
|
| |
Map scripts also now actually run in their own lua thread.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Lucas's climbing animation now accurately uses 60fps and looks correct finally!
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
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??
|
| |
|
|
| |
This allows walking through solid objects. It can be enabled and disabled using StartClipping() and StopClipping() in the debug console. It should not be used in any actual scripts.
|
| |
|
|
|
|
| |
Map layers can have a flag on them that specifies that they should be rendered as part of the upper set (rendered above the normal sprite layer but below the above sprite layer).
Also added map connections between hallucination_interior and hallucination_cliff. And named the layers in the map files bc why not.
|
| |
|
|
|
|
|
|
| |
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).
|
| |
|
|
|
|
| |
The hallucination cliff area and the hot spring map have also been dumped now, but they have not been tested and likely need work because they use a third layer, which is not yet supported. However these all share a tileset now, yay! I added collision and run sounds back to the tiles and hopefully it matches up with what it was before. Also the maps have nicer names now.
i.e. big change with no noticeable effects
|
| | |
|
| |
|
|
| |
And they're all on their own threads again. This is mostly so debug commands can be run during execution of other scripts. But it can also be useful for map init scripts (if we want a script to run whenever a map is loaded, even though map loading is usually done by a script).
|
| |
|
|
| |
Also it turns out you totally don't need the runner thread.
|
| | |
|
| |
|
|
|
|
|
|
| |
Open it by pressing backtick, close it by hitting escape. Pressing backtick does not open it in release builds.
Current shortcomings: opening it for the first time also types a backtick for some reason, but not on subsequent times. Also, it doesn't create a coroutine, so any script function that yields is going to fail.
This also added a "is gameplay paused" flag to Game, which will be useful for adding a pause menu.
|
| |
|
|
|
|
| |
All sprites are now paused when a cutscene starts and unpaused when it ends. Pausing means that the CharacterSystem and BehaviourSystem will not process them in their tick. This allows specific sprites to be unpaused during cutscenes if movement is needed.
The player character is halted and made non-controllable by the script when the cutscene starts and made controllable again when it ends. It is important to remember that if interacting with a sprite that might be moving, you have to manually call Halt() on them in their script to make them stop moving.
|
| |
|
|
| |
Ionia now moves at half Lucas's speed, which I think is good for NPCs.
|
| |
|
|
| |
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.
|
| | |
|
| |
|
|
| |
i.e. Map prototypes and triggers will not be instantiated upon loading the map if there is a persistent sprite with the same name. This is important because the Claus that joins your party is originally a map prototype.
|
| | |
|
| |
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
