I'm sure you could do that, however I think there is an edit button for your original post. Just try using that and add stuff from there. I think it would probably be better to use an external blog though

I think that that was meant for people that have a project that no one cares about enough to comment on (although IMHO, it does not mean no one cares about it, but cannot elaborate on it). The reason you would have it up on WIP is for people to give suggestions for features, aesthetic, ect. So yes, I think it could be a dev blog.

I'm sure you could do that, however I think there is an edit button for your original post. Just try using that and add stuff from there. I think it would probably be better to use an external blog though

True, but the problem with using the same post to cascade all of the updates together is you get one really big unpartitioned tldr.

Anyway, once you've done five posts, an edit is considered a 6th post (which means you can't edit the posts either) for some reason.

The rule was put in to prevent people having chains of 10+ posts without responses (cough cough gouessej cough)It encourages you to make fewer posts about bigger updates rather than a lot of posts about tiny updates.

The rule was put in to prevent people having chains of 10+ posts without responses (cough cough goussej cough)It encourages you to make fewer posts about bigger updates rather than a lot of posts about tiny updates.

Hmm, well I don't think the number of response is a good gauge for the frequency/size of updates. While it makes sense, IMO the model is a bit broken.

Would it be possible to measure the time between posts instead?

Anyway, the least you could do is allow for someone to edit their final post once they've reached that limit because my thread is virtually in a dead-lock right now :S

If no one is reading your thread, why should we let you update it? Sounds harsh, I know, but if no one is taking an interest afte you've posted 6 times there, then I think you should realize that adding in new updates won't do anything to gain you popularity. Make your updates far less frequent, and bigger so they're more exciting.

If no one is reading your thread, why should we let you update it? Sounds harsh, I know, but if no one is taking an interest afte you've posted 6 times there, then I think you should realize that adding in new updates won't do anything to gain you popularity. Make your updates far less frequent, and bigger so they're more exciting.

Your argument makes no sense.

The number of responses isn't at all directly proportional to the number of readers. A responder must be a reader, but a reader usually isn't (and statistically isn't) usually a responder. Additionally, news posts don't always warrant a response.

Finally, that isn't the main motivation of a development blog (discussion)

My thread has been read ~600 times, and has been responded to 0 times. The services are delegated across various web-platforms as well. Hence, attempting to relate replies to reads doesn't make much sense at all.

My blog posts on game jolt usually have an average of 16 reads per blog entry, and no response. Noting the only way to discover one-another is by finding one and reading the others. Just because a user does not engage in a conversation with you doesn't mean they aren't interested in what you've posted. This model is well adopted in virtually every website that posts news\updates\etc...

This thread has 80 views, and 6 responding posts. Will those viewers likely return regardless to their participation in the discussion? Likely.

Sorry, thats not what I meant at all. Besides, my point still stands because if your game is cool, people will comment. If you've updated your thread that much and people still aren't responding, you obviously need to shake it up. Sorry, but most people arent going to care about a game unless your game is awesome. If people aren't responding, its probably because they just dont care enough to respond. Its just the truth.

Sorry, thats not what I meant at all. Besides, my point still stands because if your game is cool, people will comment. If you've updated your thread that much and people still aren't responding, you obviously need to shake it up. Sorry, but most people arent going to care about a game unless your game is awesome. If people aren't responding, its probably because they just dont care enough to respond. Its just the truth.

True, but still, the point of a development blog isn't to make it cool so people respond (most things early in development aren't cool, especially an engine in development.) It may also appeal to others without provoking a response. I've had several members from GameJolt contact me about JevaEngine (seen on this forum) and they have not responded to the respective thread.

With a development blog, you can provide a link to individuals which documents all the work you've done on the engine and helps potential team members guage progress and determine how mature the project is. It gives a detailed description of the thought-process into the project. That is the real purpose behind a development blog. It is not a typical news article for potential users.

The rule was put in to prevent people having chains of 10+ posts without responses (cough cough goussej cough)It encourages you to make fewer posts about bigger updates rather than a lot of posts about tiny updates.

Please can you avoid misspelling my pseudonym? You have forgotten one 'e', it's "gouessej", not "goussej". If you spell it correctly, my bots will detect your posts about me which is better for me, you probably know why... I'm more satisfied by Riven's answer which is crystal clear.

java-gaming.org is not responsible for the content posted by its members, including references to external websites,
and other references that may or may not have a relation with our primarily
gaming and game production oriented community.
inquiries and complaints can be sent via email to the info‑account of the
company managing the website of java‑gaming.org