I've searched for raum core there's no trace of it aside from your accounts.raumvogel wrote:QUOTE (raumvogel @ Apr 7 2018, 04:28 PM) If someone can locate Raum core,it is partly developed already.
It automatically builds things in a certain order.
Fog of War?
-
MagisterXF94
- Posts: 1935
- Joined: Fri Aug 23, 2013 9:46 am
- Location: Trieste, Italy
QUOTE ^cashto@Elem (all): yeah, i imagine if you're rusty, you could build op short for no reason, build a naked ref, then go two techpaths even though your mining is by all objective standards $#@!ed[/quote]


This is a good idea.We could have fully maxed pre-built tec and maybe a few empty sectors between them.Sheriff Metz wrote:QUOTE (Sheriff Metz @ Apr 7 2018, 09:21 PM) commanding is far too complex for auto command on conquest mode.
a better focus is working on other game modes that don't require commanders

In my head, a roadmap leading to scenario's/autocommanding would look something like this:
- Configuration rework. Helpful for the next step. Working on it, another good day of work I think
- Make the LAN server easy to use. Because testing everything after this is too frustrating otherwise.
- Delay core loading until a game is launched instead of joining a server, enabling us to switch cores while remaining on the server.
- Spectator mode, for testing purposes.
- Very basic scenario's to quickly test how AI's respond to certain situations.
- Build my own core. A simple core. DumbAsARock core. Enables idiots to make tech choices. This is why "delay core loading" must be done first, otherwise too many players will hate me for this.
- Build the current pigs on the server
- Improve these bots to be capable of executing complex gameplans on their own or together. Good luck.
- Build scenarios where players can fly in scripted events. It should be fun enough to replay a hundred times as that is probably easier than an actual autocommander. This would also be the step allowing for co-op campaigns to be implemented.
- Build an "autocommander" that is not frustrating to the players flying under it. Good luck.
If anyone knows a shortcut, go ahead. But even if I had unlimited time to spend on this, I would still take a very long time before building anything that resembles an autocommander.
raum, I think you misremember what your core was capable of.
- Configuration rework. Helpful for the next step. Working on it, another good day of work I think
- Make the LAN server easy to use. Because testing everything after this is too frustrating otherwise.
- Delay core loading until a game is launched instead of joining a server, enabling us to switch cores while remaining on the server.
- Spectator mode, for testing purposes.
- Very basic scenario's to quickly test how AI's respond to certain situations.
- Build my own core. A simple core. DumbAsARock core. Enables idiots to make tech choices. This is why "delay core loading" must be done first, otherwise too many players will hate me for this.
- Build the current pigs on the server
- Improve these bots to be capable of executing complex gameplans on their own or together. Good luck.
- Build scenarios where players can fly in scripted events. It should be fun enough to replay a hundred times as that is probably easier than an actual autocommander. This would also be the step allowing for co-op campaigns to be implemented.
- Build an "autocommander" that is not frustrating to the players flying under it. Good luck.
If anyone knows a shortcut, go ahead. But even if I had unlimited time to spend on this, I would still take a very long time before building anything that resembles an autocommander.
raum, I think you misremember what your core was capable of.

It would just start buying stuff in the tech tree.I think is was as much of a slight to how bad I am at comm,as it was a serious attempt at an auto command.Rock wrote:QUOTE (Rock @ Apr 8 2018, 12:04 PM) raum, I think you misremember what your core was capable of.
Last edited by raumvogel on Sun Apr 08, 2018 4:34 pm, edited 1 time in total.

