ok, i'm going to way in here. I think that letting people view open sorce code is great. I never would say this, but now that I started the process of coding, I can see how this bennifits us. but, bgt is esentually just a scripting language. not a programming language. all you are doing with bgt is using a c style language, that has been put in to script form, in order to write scrips, wich eventually can evolve in to a game if it is done write. we have very few games in the ag community as it is. bgt is not a programming language. don't get this confused. it is true, that more games should come out in other languages, but bgt is a good way to start and get an audiogame out there, even if it is just a scripting language. the hole thing about using code, if it is open sorced, this means the person could make some moddifications to it. true. but, if your going to release a game, and call it your own, I think you should make some slight changes that are noticible to the player, thus, making it a little easier on you as a dev to not be called a code thief or what ever. zombie arena was an open sorced project. I have looked at the code myself, but I am not, however, using the same exact code to create a game of my own. I am writing out he code to see if I can implement it properly, then creating my own code derived off of the code that I am looking at. I feel that his is a better approach, considering you are having to learn how to write code, and also have a study guide to look at so to speak. this game is good for someone who is starting out, however, I think the person should really invest there time in figuring out how to write there own code, instead of just changing afew values, and then releasing it as there own game. this just shows that the person is to lazy to figure out how to recode something of there own. this is the exact reason why I haven't released my own game yet. I know iam ranting here, but I think a lot of people can agree with me on this point. programming a good quality game takes a lot of time and work. anyways, to conclude this long monnalog, just work on the coding process for now, instead of letting people shoot you down. as Einstein said, 1000 failures just means you haven't found the 1 thing that works, or something like that. the point here is, don't let the nay sayers get you down. there just words. take the game down, recode it, revamp it, then put it back up. I think you would have a lot more success that way, and reduce the flames on your game that way.