Producer Letter #18 Version 1.2.0 and Future Improvement Plans
[p]Producer Letter #18[/p][p]Version 1.2.0 and Future Improvement Plans[/p][p]Hello everyone, producer Morino again here.[/p][p]In this 18th Producer Letter, I’d like to talk about Version 1.2.0, which is finally released, as well as our plans for future improvements.[/p][p][/p][h2]Version 1.2.0 Update Details[/h2][p]![]()
[/p][h3] Bullet Hell System and Area2DGameObject[/h3][p]The contents are the same as what was explained in Producer Letter #17, so please refer to that letter for detailed information.[/p][p]The bullet hell system is a bit tricky to use, but it allows you to fire a large number of bullets. So it’s possible to create some really interesting behaviors.
We’ve also created a new sample project for this system, so please look for in the Sample Project list.[/p][p]We don’t consider the bullet hell system complete as yet, as we plan to continue updating and expanding its settings over time.
There are still many things we want to add, such as stopping bullet generation, more allowing direction control when firing, setting targets for shotgun shots, rotating the origin positions for all-direction attacks, and more. These will be added gradually in future updates.[/p][p]Area2DGameObject is compatible with existing GameObjects, so by simply switching the root node for GameObjects that don’t require collision (such as UI), you can expect a reasonable amount of performance improvement.
That said, we don’t consider this sufficient optimization on its own, and we’ll explain further improvements later.[/p][p][/p][h3]Display Direction (DisplayDirection) System Improvements[/h3][p]We didn’t mention this in the previous letter because we weren’t sure it would make it into Version 1.2.0 in time, but we’re happy to say it was successfully implemented![/p][p]Previously, display direction was always forced to be the same as the direction of movement, which significantly limited our scripting system’s flexibility. This has now been improved so objects can face various directions regardless of movement.[/p][p]You can now select an Object’s display direction type from the following options:[/p]
But we’d like to share our plans beyond that immediate future as well.[/p][p][/p][h3]Addressing Performance Issues When Creating Objects[/h3][p]We’ve continued optimizing and updating the engine to address performance issues, but it’s still not in a perfect state.[/p][p]In particular, we believe that the heaviness when creating objects cannot be fully resolved through optimization of the current structures alone.[/p][p]To address this, we’re considering implementing a system commonly known as an object pool.
This involves generating objects in advance when a scene is loaded, keeping them invisible and disabled, and then activating them only when needed.[/p][p]This is a common approach for solving performance issues during object creation, and we expect it to be quite effective.[/p][p][/p][h3]Updating to Godot 4.6[/h3][p]The current version of ACTION GAME MAKER is based on Godot 4.4, but Godot itself was recently updated to 4.6.[/p][p]We skipped the 4.5 update because it mainly focused on 3D features, but Godot 4.6 includes several useful additions for us, such as new default themes and unique node ID functionality.[/p][p]Because of this, we targeting an update ACTION GAME MAKER to Godot 4.6.[/p][p][/p][h3]Other Development Items[/h3][p]Since we still have some large-scale development work ahead, please bear with us a bit longer regarding the Linux and Mac versions.[/p][p]At the same time, we will continue working in parallel on fixing reported bugs and updating other features.[/p][p][/p][h2]Closing[/h2][p]That’s all for this Producer Letter.
I’ll talk to you all again soon, and thank you for your continued support of ACTION GAME MAKER![/p]
We’ve also created a new sample project for this system, so please look for in the Sample Project list.[/p][p]We don’t consider the bullet hell system complete as yet, as we plan to continue updating and expanding its settings over time.
There are still many things we want to add, such as stopping bullet generation, more allowing direction control when firing, setting targets for shotgun shots, rotating the origin positions for all-direction attacks, and more. These will be added gradually in future updates.[/p][p]Area2DGameObject is compatible with existing GameObjects, so by simply switching the root node for GameObjects that don’t require collision (such as UI), you can expect a reasonable amount of performance improvement.
That said, we don’t consider this sufficient optimization on its own, and we’ll explain further improvements later.[/p][p][/p][h3]Display Direction (DisplayDirection) System Improvements[/h3][p]We didn’t mention this in the previous letter because we weren’t sure it would make it into Version 1.2.0 in time, but we’re happy to say it was successfully implemented![/p][p]Previously, display direction was always forced to be the same as the direction of movement, which significantly limited our scripting system’s flexibility. This has now been improved so objects can face various directions regardless of movement.[/p][p]You can now select an Object’s display direction type from the following options:[/p]
- [p]Does not change automatically[/p]
- [p]Movement direction (pre-v1.2.0 function)[/p]
- [p]Movement key direction (Pixel Game Maker MV’s system)[/p]
- [p]Follow an Object[/p]
- [p]Follow a Group[/p]
- [p]Drift-like movement[/p]
- [p]Facing a mouse cursor[/p]
- [p]Temporarily facing a specific direction during event scenes[/p]
But we’d like to share our plans beyond that immediate future as well.[/p][p][/p][h3]Addressing Performance Issues When Creating Objects[/h3][p]We’ve continued optimizing and updating the engine to address performance issues, but it’s still not in a perfect state.[/p][p]In particular, we believe that the heaviness when creating objects cannot be fully resolved through optimization of the current structures alone.[/p][p]To address this, we’re considering implementing a system commonly known as an object pool.
This involves generating objects in advance when a scene is loaded, keeping them invisible and disabled, and then activating them only when needed.[/p][p]This is a common approach for solving performance issues during object creation, and we expect it to be quite effective.[/p][p][/p][h3]Updating to Godot 4.6[/h3][p]The current version of ACTION GAME MAKER is based on Godot 4.4, but Godot itself was recently updated to 4.6.[/p][p]We skipped the 4.5 update because it mainly focused on 3D features, but Godot 4.6 includes several useful additions for us, such as new default themes and unique node ID functionality.[/p][p]Because of this, we targeting an update ACTION GAME MAKER to Godot 4.6.[/p][p][/p][h3]Other Development Items[/h3][p]Since we still have some large-scale development work ahead, please bear with us a bit longer regarding the Linux and Mac versions.[/p][p]At the same time, we will continue working in parallel on fixing reported bugs and updating other features.[/p][p][/p][h2]Closing[/h2][p]That’s all for this Producer Letter.
I’ll talk to you all again soon, and thank you for your continued support of ACTION GAME MAKER![/p]