I've been so busy with work that I've had to put the CGE game project Templequest on hold for a while. I wanted to restart it now, so after two months or so, I check this site and webboard again and see that nothing has changed: people still crying out for that much needed update or at least some up-to-date update progress log from beenox. So to continue the project would be stupid indeed, and unfair to teammembers who invest their precious time contributing to a game which just might never get of the ground. I am not reassured at all by what I read here, including responses to people's requests for some information about this update to CGE, that the work done on Templequest until now has not been a complete waste of time.
So Templequest is still on hold.
Beenox is loosing customer enthusiasm for this software. I need some sign to keep my hope alive issues are dealt with and a working version of our game can eventually be produced with CGE.

------------------
"Get back to work, you slacker!" - Duke Nukem
(url="http://"http://home.wanadoo.nl/wim48/templequest.htm")Templequest(/url) (url="http://"http://home.wanadoo.nl/wim48/coldstone.htm")homemade tiles(/url) (url="http://"http://home.wanadoo.nl/wim48/pog/pogscreenshots.html")Funny POG screenshots(/url)

How is it that your game is stalled? You have not run into any bugs yet (as far as I can tell by your post), yet you have given up because the 'voice' of the community agrees that CGE sucks? What about the two or three games, the latest being Kit's ABC adventure, that are completed? I see this as reassurance that a game can, indeed be completed using CGE. Besides, how many of these games did you expect to see completed anyway? I've visited your site (and others game sites), admired what you (and other game developers) have done so far, but have not gotten overly excited about it. Why? Because there is a tremendous amount of work involved in the creation of a game, whether using the existing graphics, or making new one's from scratch, and i do not expect an awful lot of people to see it through to the end. No, i'm not passing the blame from CGE to the community, you or anyone else, I'm just saying that if you're gonna stop, have a reason.

------------------
Just pimpin' my (url="http://"http://homepage.mac.com/dampeoples/iblog/dampeoples")blog(/url),(url="http://"http://homepage.mac.com/dampeoples/damcam.html")voyeur cam(/url), and (url="http://"http://homepage.mac.com/dampeoples/Sterling/Menu19.html")stuff(/url)

1: gamedevving is a very tiresome and involving process.
2: people dislike tiresome and involving processes.

My game is on hold as well, but it has little to do with coldstone - I'm too lazy and spend too much time on other projects to finish it.
I could blame it on CGE, but that would be rather unfair. Its still a great prog, and although it's not as versatile as we'd want, you can make a game with it.

(one of the projects i do spend time on is (url="http://"http://users.skynet.be/fa250604/sites/crap/")CRAP(/url) .)

I agree with both dampeoples and Drunk Ninja. Although I have never put my game on hold for vvery long I still understand that it requires great patience to create a game. Many people don't have enough patience to complete a game. And thus knowone has anyone else to do but complain about bug because they have not the time or patience to complete a game.

------------------
Thanks,
GrahamVH
graham@vhpublications.com
Coldstone Developer

I'm not saying people are taking the 'Coldstone bug' cop out, I'm just saying hang in there, work until you get a bug, and when you do, don't be afraid to ask about it, you may think it's a bug, when in reality it could be a totally different problem, one that's more easily called a bug than researched and have it turn out to be a naming problem, etc, etc.

------------------
Just pimpin' my (url="http://"http://homepage.mac.com/dampeoples/iblog/dampeoples")blog(/url),(url="http://"http://homepage.mac.com/dampeoples/damcam.html")voyeur cam(/url), and (url="http://"http://homepage.mac.com/dampeoples/Sterling/Menu19.html")stuff(/url)