number one pombon fan 
eclairwolf@tech.lgbt
god my brain's been so cooked by Enterprise Software it's been a year already and i'm still like "you know what this Unity game is missing? CQRS and event sourcing and a dependency injection framework"
1
0
1
number one pombon fan
eclairwolf@tech.lgbt
fr though my half-baked "ECS but with Testable Commands" idea has to be at least sort of something
1
0
1
eli (ˈe̝ːli), vampire kitsune
rowan
@eclairwolf i feel like you’d enjoy the AppUI unity package
2
0
2
Show content
@eclairwolf though tbf i have a Lot of feelings about ecs’ current state of querying – especially given its over-reliance on component types and not enough on data or relationships. i wrote my ecs article earlier this year with a pt. 2 planned about how querying in ecs should more closely resemble database queries – probably something like a RDBMS query language at first but hopefully eventually into something like a neo4j cypher-like language which can query based on entity relationships. i would love to be able to, for example, query all enemies in an active battle scene to determine the valid targets of a spell which automatically kills enemies that are under 10% HP
match (:Player)-[:IS_BATTLING]->(enemy:Entity)
where (enemy.current_hp / enemy.max_hp) * 100 < 10
return enemy
Show content
@eclairwolf ecs libraries like FLECS already store their components in graphs that they build/traverse when components are added/removed (these are called archetypes). i feel like it’s a natural next step to be able to query entities and components as a graph.
0
0
2
eli (ˈe̝ːli), vampire kitsune
rowan@eclairwolf frick yeah love observables (also check out r3 if you want a general reactive library for unity)
0
0
0