

๐ฎ [Viridi Vix]
so AGK is an ECS engine right... but i can't call the S part "system" because there's alreaddy java.lang.System and i think it would get too confusing. what should i call them,. the things that do things instead of the things that just are things (data-style)


๐ฎ [Viridi Vix]
maybe one of these?


๐ฎ [Viridi Vix]
it is decided so: the Systems in my ECS shall be named "". I am confident that the JVM will be absolutely fine with this name and will not cause any issues 


๐ฎ [Viridi Vix]
@rowan disregarding kotlin entirely, I'm subscribing to a three-stage System ECS pragma, that is, that each System has a before() -> Boolean, onEach(Entity) -> Unit, after() -> Unit stage flow (Unit is essentially void in Kotlin), where before returning false will suppress the other two stages (so e.g. if there is a check to see if the game is paused, that system can short and cancel itself out before it does Things). So beyond the "do A Thing to each entity" of the onEach stage, Systems can also run a global process in their before and after stage as well
In a more broad overview sense, each System will just Do A Thing to each entity; queried component data in, modified component data out, on each Entity passed to onEach.
@vivi a ok that makes sense! thank you for explaining
so the three-stage System is responsible for
i think i like โBehaviorโ or โRunnerโ for that, but i also know Nothing 


๐ฎ [Viridi Vix]
@rowan i actually did choose Behavior for the name in the meantime anyways



๐ฎ [Viridi Vix]
@rowan also yes those are the very yes correct stage descriptions i should have said 