Hey guys, so lately I have been working on my project "DeathStop" and I have been posting a lot on it, and I feel like I am spaming the fourm but I really just want to show you guys the development of my game because it's actually a really cool project. Now I feel that no one is really interested on clicking the DeathStop link when they have already seen it like 5 hrs ago. For this I am really sorry and I will work on posting a lot less about the game. Other than that hope you guys have good day
-Noah
-------------------------------EDIT---------------------------------------------------------------------------------
I think I'm gonna take some time off DeathStop and learn how to use Blender. Does anyone have any good tut links that might start me out?
Last edited by n04h on Wed Feb 16, 2011 7:34 am, edited 1 time in total.
Now I feel that no one is really interested on clicking the DeathStop link when they have already seen it like 5 hrs ago.
I think we all know you're excited about your game, and you should be, you've worked quite a lot on it. But as you know, it get's kind of annoying. Well, it's not actually that annoying, just mildly repetitive.
Its not bothering, but as you pretty much mentioned in the OP, it does seem to get a lot less pressing to check it out when you saw it just a few hours ago and the only new thing is a couple more images added.
What you could do is adopt a version number system. It doesn't have to be industry-standard or anything like that. Just as long as you understand it. For example, just a single page with some design would likely be around v0.0.1.x. The first number after the "v" is the "major release". That shouldn't hit 1 until the game is completely done and released. Then it wouldn't hit 2 until a major revision of the game, changing nearly everything. For example, WoW only changes major version numbers after the release of a full expansion pack. The second number is a "minor update". These still typically mean a very large update. Again using WoW as an example, a minor version update is typically a free game update that includes a laundry list of 30 - 40 small-ish but very player-relevant updates to the game: new dungeons, new items, new spells, etc. The next number over is typically called the "build number". These are usually smaller changes that are working towards a full minor update. These are not often publicized in games such as WoW, except as a quick bug patch to fix a problem the game has been experiencing. The update list will typically only have an handful of updates or less. The last number is typically called the "revision number", and simply keeps track of the compiles of the source code. For a single developer working alone, you could choose to up this number while actively coding and checking your page over and over. These numbers are usually of absolutely no significance to end-users. Most of these never end up in the hands of players, so they almost seem to change at random.
Version numbering could be useful for several reasons. It will, of course, do its primary purpose of keeping your codebase cleaner and helping you know which files are for which build. As you start keeping backups of your site it will become crucial, else you end up with a mess of mis-matched files and many errors. The second reason would be that you could decide to post updates to your game on the forums on every minor update or so, or for specifically important build releases.
Jackolantern wrote:Its not bothering, but as you pretty much mentioned in the OP, it does seem to get a lot less pressing to check it out when you saw it just a few hours ago and the only new thing is a couple more images added.
What you could do is adopt a version number system. It doesn't have to be industry-standard or anything like that. Just as long as you understand it. For example, just a single page with some design would likely be around v0.0.1.x. The first number after the "v" is the "major release". That shouldn't hit 1 until the game is completely done and released. Then it wouldn't hit 2 until a major revision of the game, changing nearly everything. For example, WoW only changes major version numbers after the release of a full expansion pack. The second number is a "minor update". These still typically mean a very large update. Again using WoW as an example, a minor version update is typically a free game update that includes a laundry list of 30 - 40 small-ish but very player-relevant updates to the game: new dungeons, new items, new spells, etc. The next number over is typically called the "build number". These are usually smaller changes that are working towards a full minor update. These are not often publicized in games such as WoW, except as a quick bug patch to fix a problem the game has been experiencing. The update list will typically only have an handful of updates or less. The last number is typically called the "revision number", and simply keeps track of the compiles of the source code. For a single developer working alone, you could choose to up this number while actively coding and checking your page over and over. These numbers are usually of absolutely no significance to end-users. Most of these never end up in the hands of players, so they almost seem to change at random.
Version numbering could be useful for several reasons. It will, of course, do its primary purpose of keeping your codebase cleaner and helping you know which files are for which build. As you start keeping backups of your site it will become crucial, else you end up with a mess of mis-matched files and many errors. The second reason would be that you could decide to post updates to your game on the forums on every minor update or so, or for specifically important build releases.
This I did not know, and will write it down with useful information!
well then you won't mind when I miss some posts hehe I can barely keep up these days
I have been dropping in now and then and checking on your game. As far as I am concerned as long as you are updating your game topic and not posting from one end of the boards to the other like mad then all is good. It is your topic. You just have to be careful as to not "cry wolf" as you posted.
Yeah, like Halls said, it is definitely not spamming to keep posting updates in your project thread. It is more an issue of trying to maximize the number of people who come in and test it
