|
« Reply #49 on: May 29, 2013, 08:11:43 pm »
|
|
I tried the demo.
It told me I got a sword and to press c to use, but I never got it to work. Then I got out of the house and somehow fell down "behind" the house below, I would walk around inside the tiles. I think I jumped over to it or something =/
Then I gave up xD
Its a really buggy demo i was rushing to get a demo out. But in demo 2 all the bugs will be corrected.
and that chest u found was my test chest I used to test the sword but i deleted the contents of the chest so it was just left there.
lol, why did you rush it? Why did you give it out if you knew it was buggy? Why not take your time to make a good first impression!?!
why do you care? why not leave me alone and let me do what i want!?!
Whoa, whoa...whoa. Whoa.
First off, what Zeldafan provided is a demo, which on this website generally means "great WIP". If it's buggy, well, so be it. That's game development; not every iteration before the final product is going to be stable.
Second, that being said, a certain level of stability really should be enforced for releasing demos. If it's unplayable, I would suggest not releasing a demo until said things are ruled out. I think it's okay to have some bugs seeing as these demos usually are just documented works in progress, but I think it's also important to release it in a somewhat playable/stable state.
I would kindly ask both of you to chill out a little bit. Wildex, your questions are great, but have a slight tone of aggression with the use of "!?!". Zeldafan, you have someone who is legitimately trying to help, albeit in a goofy, less docile way. I would suggest you take his suggestion to heart and work at making better demos! Wildex is trying to make YOU look better by giving you helpful tips.
Sorry, I didn't mean to be aggressive, It's just that I'm bewildered by why someone would rush out a demo, knowing it is full of bugs. A demo is a demonstration of the work. The FIRST demo should be the thing you take your time with, polish and clean up to give not only a good first impression, but also allow for feedback. Why should someone take the time to give feedback if the author didn't even take the time to fix the most obvious bugs? Why should we care if the author does not? A demo will have bugs yes, but known bugs should be mentioned by the author if they are hard to fix, fixed if they are easy to fix, and unknown bugs can then be reported to help out the author, thus fulfilling the second point of a demo. I just could not see any reason for why he should need to rush out a demo. Just my 5 cents, will stay silent now.
Logged
|
Working on my Masters Degree in Computer Science. Hey look, Zelda Coop....later. Proud user of C++ for 9 years, and counting!
|