Can you provide some more details on what you mean by spawn AI in Construction Script?
Spawning Actors directly in the construction script would result in massive duplication of the generated Actors as the construction script gets re-run a lot of times unless we did a substantial amount of work to associate the spawned actors back to their parent … kind of like what ChildActorComponent does. And before you ask why we don’t just make Spawn Actor do the ChildActorComponent thing automatically, it isn’t really all that possible (and certainly isn’t good API design) to make SpawnActor behave differently in construction script vs. event graph.
ChildActorComponent is absolutely the right way to do this and we do plan on making it parameterizable both for which class and likely the same expose on spawn parameters will also be available. Unfortunately, there are some other things that are currently taking priority (cyclic dependencies in blueprints is probably the most directly involved) so I can’t give you a timeline, but it is something we plan on doing.