{"author_name":"Covenant","cat":"LD #20 - It's Dangerous to go Alone! Take This!","comments":[{"author_name":"nilstastic","time":"May 3, 2011 2:50 am","epoch":1304409000,"text":"My personal opinion is that no buxfixes should be allowed no matter how serious they are. My entry has issues with the game playing on 600fps on som some machines as well as a number of other “minor” problems (getting stuck in walls, background shownig through the parallax etc) but it would be unfair if i could fix them after the deadline since i decided that i should spend the last hours of the compo on making the game fun instead of bugtesting. =)","spam":"N"},{"author_name":"nilstastic","time":"May 3, 2011 2:52 am","epoch":1304409120,"text":"Also, this should be a sticky since the status on this seems a bit unclear. I work with 0 and 1, I need rules! =)","spam":"N"},{"author_name":"","time":"May 3, 2011 2:59 am","epoch":1304409540,"text":"Yeah same…
\n Thing is that LD is not a programming competition, so fixing “major” bugs should be allowed. Things that qualify as major bugs:
\n – Application not running on some platform because of compatibility issues
\n – Graphic\/audio glitches caused by compatibility issues
\n – Logic bugs that not affect gameplay mechanics (flow related things, like main menu to load game to game to game over, etc)","spam":"N"},{"author_name":"nilstastic","time":"May 3, 2011 3:40 am","epoch":1304412000,"text":"I would like it if only compability issues were allowed. Regarding menu\/logical\/gameover bugs, i think that they would have to stay in the competition entry since for me (and a lot of other people) a well put together menu can be a lot of fun to use. It would also make the difference between allowed\/not allowed fixes to be more distinct (compability = hardware). =)","spam":"N"},{"author_name":"","time":"May 3, 2011 4:23 am","epoch":1304414580,"text":"Well, “a well put together menu can be a lot of fun to use” would be a mechanic change, if you change the menu… If you change it so that the game doesn’t crash when you over a particular zone of the screen while functionally leaving the menu just the same as it was is a bugfix…","spam":"N"},{"author_name":"nilstastic","time":"May 3, 2011 5:16 am","epoch":1304417760,"text":"Agreed that we need a yes\/no answer (with a good motivation).","spam":"N"}],"epoch":1304407140,"likes":1,"metadata":{"p_key":"65767","p_author":"Covenant","p_authorkey":"326","p_urlkey":"101563","p_title":"Bug fixes (repost)","p_cat":"LD #20 - It's Dangerous to go Alone! Take This!","p_event":"LD20","p_time":"1304407140","p_likes":"1","p_comments":"6","p_status":"UPD5","us_key":"326","us_name":"Covenant","us_username":"covenant","event_start":"1304035200","event_key":"6","event_name":"LD20"},"text":"
\n

Sorry about posting this again, but it probably got lost in the traffic and I didn’t get any answers…<\/p>\n

What\u2019s the current policy on bug fixes?<\/p>\n

People have found a couple of bugs on my entry so far (one pertaining ambient light levels, the other the behavior of the ESC key)\u2026 I\u2019m I allowed to correct these bugs (since the first one kind of ruins the second level, and the other is just silly)?<\/p>\n

I also have another bug concerning full screen (if the resolution is not that of the desktop, it just shows a black screen), would like to fix that so that people don\u2019t have to edit a text file\u2026<\/p>\n

I remember we had some compos that allowed for bug fixes after the end, but I\u2019m not sure what\u2019s the current status\u2026<\/p>\n <\/div>","time":"May 3rd, 2011 2:19 am","title":"Bug fixes (repost)"}