I think this tool is an excellent tool for making games easily.
However, I have some requests that I have made while using it, so I have summarized them here. (v1.10.5)
- PROJECTILE firing position adjustment function.
When setting up enemies, the muzzle of the graphic and the firing position of the PROJECTILE do not match at all.
Even if you use the FSM function, you can only adjust the height, and you cannot aim up and down, so it is difficult to use.
I would like to add a firing position item to the enemy scale adjustment window so that it can be adjusted even without using FSM.
Similarly, I would like to be able to adjust the firing position of the player's PROJECTILE.
- Add the concept of layers and size to the HUD.
The HUD can only be adjusted in position, and there are not many options for placement. Also, the HUD image displayed in Scripting is displayed in front of the standard HUD.
If you name the image "Foreground0.png", it can be displayed behind the HUD, but this cannot be switched on/off in Scripting.
I think that the HUD needs layer and size items to make these elements coordinated.
・Minimap function expansion.
The minimap only displays the terrain of floor 1, so it is not compatible with three-dimensional maps.
I would like it to be rewritten appropriately according to the player's Z coordinate.
・Minimap permission can be controlled by script.
Currently, the player's permission to jump, crouch, etc. can be controlled by script, but I would like to control permission to use the minimap and flashlight as well.
In the early stages of development, I was thinking of a stage structure where you can progress through complex mazes without getting lost by picking up a map, but this idea was scrapped.
・FSM function expansion.
Enemy behavior is determined by the current States, but the timing of PROJECTILE launch, etc. belong to Actions.
I would like to expand this and increase movement-related Actions such as lateral movement and hopping, and set more complex behavior patterns.
I would also like a dummy States item to allow conditional branching with JUMPIF-related Actions.
- Bug reported.
When an enemy uses a hitscan attack, the player's PROJECTILE will not take damage until the next ATTACK state.
This was addressed by changing the enemy's attacks to invisible and fast PROJECTILEs, making them a pseudo-hitscan.
After a certain point, a bug occurred where the game would crash when a newly created enemy tried to fire a PROJECTILE.
This was resolved by deleting the executable file for test play and regenerating it during test play.