There’s actually some truth to this statement in general. Most games, at least the ones deriving from quake engines that i know of, have an engine(e.g. the exe) and a game (a dll/so) plus assets. When modding SDK-s are released, it’s essentially the source code of the game section that when compiled needs the same engine to run. New games from a studio using the same engine are usually just forks of the previous game code. It’s fair to reason that some code may be shared to get updates on old parts while developing a new game.
“Accidentally” keep happening. How the hell do you compile and push out code for a game you’re not even updating at the time, accidentally?
Because all Valve games are mods all the way down.
When your game is a mod of a mod of a mod, this stuff happens.
I can understand bits and pieces, because that is very true with Valve… But the entire prototype?
I mean it’s just one map with heavily tweaked bot scripting, that is the whole prototype
for a 20 year old game it’s probably only a couple of megabytes
There’s actually some truth to this statement in general. Most games, at least the ones deriving from quake engines that i know of, have an engine(e.g. the exe) and a game (a dll/so) plus assets. When modding SDK-s are released, it’s essentially the source code of the game section that when compiled needs the same engine to run. New games from a studio using the same engine are usually just forks of the previous game code. It’s fair to reason that some code may be shared to get updates on old parts while developing a new game.
So yes, most games are mods of mods.
Because source shares code and assets between projects to cut down on development time