[hypercube33]

Weird. I find the balance for player vs AI to be actually pretty horrible. AI can outrange artillery sight so you have no choice but to push forward always or micro manage units. I have a fork of OpenRA on my GitHub where I try to address this, along with pathfinding bugs, enabling Tiberian Sun and fixing bugs with that. I also updated it to cross platform .NET 10 and bumped the performance up about 6-10x fixing minor bugs. Debating if I'll roll any of the code over as pulls to the main project ever after I tried to fix a random bug before and they were not welcoming to me but that was like a decade ago.

[mitthrowaway2]

Link to your GitHub? I'd love to play the version with your improvements!

[liendolucas]

The comparison was against the original game. I haven't played on the computer since ages, but that was my impression the times I played it. I'm not deep into all the nuances of the game just that it was considerably better that the 1995 release.

[benoau]

1995 was the original "Command and Conquer" not "Red Alert". In the original C&C the computer wouldn't attack sandbox walls which was basically godmode since you could just fence them off heh.

[b112]

The load/save is what kills me. It's a great project, but having to wait 2 hours for a game to load, fans blaring on my laptop, makes it less playable.

For context, I love huge, massive maps with loads of players. OpenRA replays the entire game to restore, it doesn't have a save-current-state routine.

So 20 hours of massive map + 8 players means 2 hours of pegged CPU to reload the save.

Heartbreaking.

[lenkite]

Now, that is what I call taking the "Command Design Pattern" to heart!

[apitman]

> So 20 hours of massive map + 8 players means 2 hours of pegged CPU to reload the save.

It's super impressive this works at all.