CnC_Remastered_Collection VS spring

That's just a clone game though. And the originals were actually made open source with the release of the remaster.

Not most, but quite a few legendary ones were released in a "source available engine, paid maps" kind of way. Check out Id Software's github for a couple versions of DOOM, Quake and Wolfenstein. EA has released Command & Conquer's source code (here).

You could just look through the source code and see if you can spot anything though.

If anyone curious about some historic examples here is the pathfinding code from the C&C/Red Alert games

>The path algorithm works by following a LOS path to the target. If it collides with an impassable spot, it uses an Edge following routine to get around it. The edge follower moves along the edge in a clockwise or counter clockwise fashion until finding the destination spot. The destination is determined by Find_Path. It is the first passable that can be reached (so it will handle the doughnut case, where there is a passable in the center of an unreachable area).

https://github.com/electronicarts/CnC_Remastered_Collection/...

https://github.com/electronicarts/CnC_Remastered_Collection/...

That being said bespoke development being done badly is the source of horror stories. It's like old games C++ being notoriously "horrible garbage hacks" and yet, code like this or this is very well documented and not bad.

What do you more than this? https://github.com/electronicarts/CnC_Remastered_Collection

I merged the upstream branch of the source code into my mod branch, did a new build, moved teh required files into the mod folder and confirmed the mod worked locally.

The source is wrapped up in DLLs so it can run in their frontend, but all of the old game source is there: https://github.com/electronicarts/CnC_Remastered_Collection

As a specific example, the code for the Command & Conquer video games was released by Electronic Arts awhile back. Looking at some of the code for C&C: Red Alert (https://github.com/electronicarts/CnC_Remastered_Collection/tree/master/REDALERT), I was struck by how many comments were included. For example, this is a snippet from one of the source files (HOUSE.CPP):

Recoil (previously called Spring) - https://github.com/beyond-all-reason/spring

If you want to develop the engine https://github.com/beyond-all-reason/spring, checkout GitHub wiki of that repository which contains compile instructions with docker, without and for MSVC setup.

Many current BAR developers are old BA devs. Many old BA players are current BAR players. Then also the engine fork happened (Recoil) (https://github.com/beyond-all-reason/spring) for similar reason as above, and Recoil+BAR currently receive the most active development, with other Spring RTS games like Zero-K also migrating to Recoil.

All is about providing a correct start script for each player: https://github.com/beyond-all-reason/spring/blob/BAR105/doc/StartScriptFormat.txt

Yes, it's using continuously developed fork (https://github.com/beyond-all-reason/spring) of the Spring RTS engine.

Well, my personal preference is for Zero-K/Spring, because I actually like micro :

http://zero-k.info/

But BAR/Spring seems like it would fit you better (it's also the closest of them to TA, which is otherwise a bit old these days) :

https://www.beyondallreason.info/

(BAR used to stand for Balanced Annihilation Reloaded, while Zero-K used to be called Complete Annihilation.)

Still a number of active projects where the game (or variations of it) are being played. Check out Beyond All Reason