We did discuss licensing. We ended up choosing a BSD-style license. We're just not certain about practicality right now. We want to make the engine available, but we don't want to make our game content or ideas visible yet. At least not until the game is ready for public viewing. Since we don't have much content yet (and the content we do have isn't in the repo), I could put Cerberus source up for public read access. I think I'll put it on GitHub for easy forking, etc.

Oh, I'll also put a copy on GitHub so people can fork it.

http://github.com/tycho/cerberus

This reminded of one thing... sometimes, fully allowing modifications might spoil the game to some players (like people who use mods on the GTA series to make things easier).

Just a suggestion - maybe something like those games where you must have beaten the game (or in the case of Cerberus, getting to a certain point, OR doing whatever needs doing to unlock modding ) coulda make things more interesting. I'm not sure about it, but I think Fallout 3 uses this system (you must have beaten the game in order for the mods to work)

They chose to use mods, they chose to alter their gameplay experience and if that spoils the game for them, too damn bad. They chose their fate.

What.

The day after I got Fallout 3 PC I started modding it and playing with mods.

-- Griffinhart

so people can fork it.

some things after just compiling and testing cerberus:

1) to actually run cerberus i had to patch it, since it did not find the fonts. see attached patch.

2) is it right that after launching it i see some few lines at the bottom (including fps, version number 0_0_0, etc) and nothing else but a dark background? just to be sure that's how it's supposed to be - or should there be something more?

3) how to close cerberus? i have to kill it by switching to another console and send a sigterm, any other way ingame? some keycombination i did not test? (did not make my way through the code yet to find an answer myself, though)