shapez.io VS CnC_Remastered_Collection

You can pay for FOSS software. I do it to support FOSS developers and maintainers.

software example: Krita https://store.steampowered.com/app/280680/Krita/ source code https://invent.kde.org/graphics/krita

game example: Shapez https://store.steampowered.com/app/1318690/shapez/ https://github.com/tobspr-games/shapez.io

Shapez.io is sold Steam but the source code and build instructions are on github: https://github.com/tobspr-games/shapez.io

It's been free on github the whole time 😝

It's free on github too :P

apparently the instructions from github are outdated or something

I have experience in releasing an Capture Note made with Electron and there are some annoying processes, but it is possible without as much difficulty as I thought. From what I know, there are also games that have been released. Try looking for "Danger Crew" or Shapez. Shapez is open source, so it may be more helpful.

It's possible that this is a bug in how I've built the local version, or that the local version is only a demo. So I have filed https://github.com/tobspr-games/shapez.io/issues/1500 to see if that's the case.

Pretty sure shapez.io is an Electron app, and that's on Steam.

Hmm, like Thrive and Shapez.io?

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):