Should I Release the T.W.T.P.B. Source Code

I'm thinking of releasing the source code for my pc shoot em up game - T.W.T.P.B. under some kind of "free for personal and educational use". Do you think that that would be a good idea?

There will be some restrictions, since I don't want all of the code out there (copy protection, highscore stuff etc) but the bulk part of the actual game code would be released.

I've been asked some questions about game programming in general and about T.W.T.P.B. in particular, so maybe this could be a good contribution to aspiring game programmers.

Would a source release do any good? I actually think so, since the game is small enough for an "inexperienced" game programmer to dive into and possibly understand. Also we could do a forum section where I could answer questions and comments...

Anyway, what do you think? Should I release the source?

users avatar

Expect some support requests...

I think it would be a good idea if you are prepared to support it to certain extent.

This is sort of similar to what id Software has done with the Quake codebases, and personally I've certainly benefited from that.

/johno
"you can't stop the change"

users avatar

I personally lack the time

I personally lack the time to dive into the code now, but I think it's a great idea. I'm not very good at c++ gui programming yet, so it'd probably come in handy in the future, like in summer or so.

______________________________________________
"The time you enjoy wasting isn't wasted time"

users avatar

I'm thinking of doing some

I'm thinking of doing some kind of video tutorial explaning the basics of the source, and would of course welcome any questions and discussions.

As I see it it could be a staringpoint of some kind of active "Game Development" section here at SoP and beeing a resource for the numerous game development schools out there.

users avatar

Of course you should

Just leave the components you want to protect out of the source code you release and make sure it builds without them. Make it a separate code project so people that want to play around with it can edit, recompile and run it easily. If possible, make the license as non-restrictive as possible.. you never know what kind of awesome stuff people might do based off of your source code.

I can easily see peoples creativity getting a boost by something like this, personally I have enough to do with my own code these days..

users avatar

Sounds great

Then I wouldn't have to bother you with questions like how did you structure this or that in your game? Smiling

users avatar