Day 6.
At some moment I understood I want complex dialogs, but it's difficult to maintain quest branches looking into script code. So, I've created converter of visual graphs into script dialog. Graph is created in online diagram drawing tool (draw.io).
But it generates only skeleton of script. Then I will write readable descriptions and if needed modify any branch. Now need to think how better generate dialog with text or resource_ids.
Day 7
Congrats with a new year!
Part#1. Dialogs convertor
Today I've completed diagram-to-dialog convertor. And I have to say that it could be more difficult than I expected. Example of how simple dialog (2 entry points, 3 endings, 1 possibility to accept quest) could look like (big zoom just for total overview):
Groovy code generated from this diagram is completed on 95%. Then I add some custom conditions in several places and dialog is ready (in 2 variants for main planet and common planet of Lumen race). Here player could accept 1st quest for Lumen race.
Part#2 Basic AI & World simulations
I setup each planet to produce 1 ship each 5 seconds.
Then add basic AI component to each ship. In general each AI ship each second will raycast in looking direction to check on obstacles. If there are no obstacles - then move ~50 px / second. To avoid obstacles rotate on ~20 degrees.
Source code of AI processing here in gist
System has very general name, but it will be used like Patrol system soon. I'm going to add more AI behaviours and system for targeting enemy objects.
Now galaxy looks alive and crazy even with such simple AI.
ECS magic step-by-step or "how to learn your animals move in world":
1. Rename ShipAiManager to AiPatrolManager
2. Create AiPatrolComponent for your animal entity (in my case it is on scene loader stage)
3. Profit! Space-Creatures moves by own business in space...
4. PS: do not forget to review usage of AiPatrolSystem when add attack action into patrol action :) or animals will attack player
Day 8.
Completed basic ships AI (red ship is under AI control):
It's a simple system with step every 0.3 seconds which could call other subsystems by situation:
And example of what subsystem could do in 0.3 second step: AiAttackSystem
Day 9. Stationary turrets
Yes... this is turret set on planet:
It has the simplest AI ever:
Where AiStaticAttackHelper tries to target enemy.
And at the same time StationaryGunSystem controls rotation of gun.
Day 12
I've made some fixes fo AI and added heat damage when entity is too close to the sun.
For this I added triggers into Box2dSensorComponent:
And then in startSensorDetectsBody method which is called from 'Box2World > ContactListener > beginContact':
The same way for endTrigger in another method.
And user implementation of any trigger (in this case for sun damage):
Any entity gets damage each 0.5 seconds in area of sun body sensor.
Text-Quest state machine detects quest-options, closures or strings for text area, example in-game:
