Talk:Bug Reports

Archives:

• Archive 1 -pinkgothic 12:40, 20 Dec 2005 (GMT)
• Archive 2 -pinkgothic 16:41, 7 Feb 2006 (GMT)

---

Zombie Gun Use

Discusssion regarding the Zombie_shot_me_with_a_gun bug / exploit.

Clean-Up

I think I should do a clean up sometime soon, when I have time. That won't be until in a few weeks, though, so if anyone else wants a go at beautifying the page a bit, please, give it a try :) -pinkgothic 14:10, 27 Jan 2006 (GMT)

Man, I'm really itching to change this thing. One more exam, today, and I'm going to template individual Bug Reports, summarise the Misunderstandings into a more readable form, give search tips, and the whole lot. And suggest a new way of handling aaaage old bug reports. This page is too long. Anyway, give me another six hours or so and spring cleaning will commence.

Until then, in the off-chance anyone has any input to dump on me, this is the place to do it. ^_^

BAGH BARGAHZ BAHAHAHAHAHA.

Oops, out of character. -pinkgothic 10:00, 7 Feb 2006 (GMT)

Okay, details written up now. Note that just because it says 'for immediate implementation and use', it does not mean it's not open to debate and criticism. On the contrary. Please tell me what you think. -pinkgothic 16:45, 7 Feb 2006 (GMT)

For Immediate Implementation And Use

I'm going to be gone for a few hours. When I return, I hope to template-ify all bugs on the actual page reported so far. If anyone wants to beat me to it, go right ahead, but please read the status and severity flag details below, thanks! Well, unless you disagree with them, of course, in which case, please state your reasons so what I've cooked up until now can be improved. -pinkgothic 16:58, 7 Feb 2006 (GMT)

Templated the page. I've also taken out the Misunderstandings and Features and the Browser Issues sections, and stuck them here, and added the section Bugs currently being reviewed in Known Bugs, for references on bugs being discussed in Known Bugs that have yet to be fixed, and the section Bugs on which further information is requested to categorise bugs which have comments attached to them, but where the comments don't yet contribute to a change in the bug's status.

Also, check the new note on the top of the page, the rewritten New Bugs (previously 'Bugs reported once') introduction. All in all, a couple of details have been changed, but in large parts, it is still the same old Bug Reports page.

Notably, I have also moved a couple of reports devoid of a timestamp to another page. That's it for today. -pinkgothic 17:11, 9 Feb 2006 (GMT)

Template

All right, folks, we have us a template. I'll be damned if I get the defaults to work one day, but for now, it has none, just a bunch of parameters that should never be amiss. This is the syntax:

===A header name which best describes the bug in under ten words===
{{bug|
bug_time=~~~~~|
bug_author=~~~|
bug_status=new|
bug_severity=unassigned|
bug_desc=Your detailed description of the bug you encountered.
Remember to include as much information as could be possible, including
your character name (and profile) and screenshots if you have any.|
bug_talk=
<!-- PLACE YOUR COMMENTS **BELOW** THIS LINE - DO NOT DELETE THIS LINE -->
Comments here
<!-- PLACE YOUR COMMENTS **ABOVE** THIS LINE - DO NOT DELETE THIS LINE -->
}}
----

Note the blatant rip-off of the Suggestions page's template. And syntax description, in fact.

The Status Flag -- Possible status flags:

• new

This should always be in place if there have been no comments yet.

• unreproducable (since ~~~~~)

If people have tried to reproduce this bug and failed, and not one other user has, until that time, been able to reproduce it, this is what should be put into the status flag. Note the timestamp.

• reproducable

If people have tried to reproduce this bug and managed on occasion, the bug is marked reproducable. Previously "unreproducable" bugs pass as this, or bugs with less than two confirmations which would otherwise be considered "confirmed" (see below).

• confirmed

If people have, in retracing the steps of a bug, been unable to avoid a bug, or a pattern of it's occurance has been found, a bug can be marked confirmed.

• non-bug

Not really a flag, but listing for completions sake. If something is found to be a non-bug, the bug should be removed and the author of the bug should be informed of the removal. It should also be noted on the talk page for consideration into the guide about 'frequently misunderstood features/browser quirks' - which is going to appear in one of the next Clean-Up steps.

The Severity Flag -- Possible severity flags:

• unassigned

Newly submitted bug, will be reviewed. Note that not all submitted bugs have to start out this way - the author of the original report has the full right to point out what he expects the severity to be.

• aesthetics

Typos and page colour or page formatting errors.

• low

Something that should not happen does, but it does not actually enable anyone to do anything out of the ordinary... it might just allow a skip of a page, or a dropdown list is populated wrongly - essentially, something that cannot be abused, but causes server strain or user irritation ;)

• medium

Anything that does not fall into the other categories.

• critical

Exploitation of this bug is easy when known - or, worse yet, it can be easily stumble upon - and skews gameplay.

Frequently Misunderstood Features/Browser Quirks

The entire Misunderstandings and Features and Browser Issues sections will be removed, and instead replaced with pointers helping people to spot a bug from a feature/quirk themselves. I'll be writing that guide either later today, or tomorrow, or sometime other that can be classed as "sooner rather than later".

If anyone wants to beat me to it, go right ahead. ^_~

Not For Immediate Use

Rule Suggestions: Discussion And Voting

• Status: new, Severity: any, Timestamp: Older than 1 month

Removal without notice.

• Status: unreproducable, Severity: all non-critical, Status Timestamp: Older than 1 month

Removal without notice, optionally with notice of the original author for resubmission.

• Status: unreproducable, Severity: critical, Status Timestamp: Older than 1 week

Bump to the top, refresh timestamp, place 'RERUN:' infront of the bug name. If the bug is already labelled that way, removal without notice, optionally with notice of the original author for resubmission.

• Status: reproducable, Severity: aesthetics

Keep in a designated "Semi-Neccessary Face-Lifting" ;) section on Bug Reports. Stuff like this is not so much a bug as something Kevan can do in his free time, so it has no use on the Known Bugs page bar for clutter.

• Status: reproducable, Severity: low

Move to Known Bugs after 5+ confirmations weighing 50%+ are in.

• Status: reproducable, Severity: medium

Move to Known Bugs after 3+ confirmations weighing 50%+ are in.

• Status: reproducable, Severity: critical

Move to Known Bugs after 1 confirmation is in.

• Status: confirmed, Severity: aesthetics

Move to Known Bugs after 5 confirmations are in, mark as low priority there.

• Status: confirmed, Severity: low or medium

Move to Known Bugs after 3 confirmations are in.

• Status: confirmed, Severity: critical

Move to Known Bugs immediately.

Any other quirks, such as bugs being ancient but confirmed/reproducable/etc should be decided on a case-by-case basis.

Notably, I won't instate those rules just yet, this is a rough draft. If no one tells me otherwise within two months, I will start working by this, though.

Archive

I have moved most of the "new" bugs from before May to Bug Reports/Archive. Feel free to clean it up if you want to. --V2Blast ^P! 13:00, 9 June 2006 (BST)

• I'm going to archive everything that hasn't been commented on since last year. I'm also going to move stuff to Fixed Bugs as appropriate. --V2Blast ^{T•P!•C•SR} 23:22, 26 April 2007 (BST)

Blah. *gives up on page* --V2Blast ^{T•P!•C•SR} 05:24, 31 December 2007 (UTC)

I'll take it over then... maybe later today --~~~~ [talk] 13:49, 31 December 2007 (UTC)

Mmmkay, i finally got to do something about it. it's much shorter now, but still has 60+ reports. most depressive is that at least half of them might never go anywhere. --~~~~ [talk] 20:27, 19 January 2008 (UTC)

Logged in..Character STILL exhausted of APs

Greetings Newbie here to the posting at WIKI~~

Please excuse and kindly direct me of where to go if I'm posting this in the wrong area. I'm not used to how this is setup and how posting goes and everything. I have been reading to try and understand it, but have failed to progress beyond stumbling Newbie so far, *put dunce cap on head*, if you must.

-p

To my problem-bug-quirk-whatever,

I have 3 different characters I play with for variation and different game play experience. My problem is with one of my characters: Ann ill ate

I had last logged in with my 3 characters some time yesterday and when I logged in earlier today (1:53pm MY time) to play. One of my characters was fully charged and another was mostly charged with AP. However when I went to log into 'Ann ill ate' my character was totally depleted of AP. What's up? I always clear out cookies and my browser regularly, particularly before I log off my PC.

I currently finally gained some APs but I have no idea what happened to all the APs I should have accrued, like I did on my other characters, from a complete nights rest and most of the morning through to noon of today. Hmmm...

Thank you for your time, attention, and forebearance of this here Newbie,

--EveryWitchWayURun 04:26, 24 June 2006 (BST)

When I've tried posting this to the Bug Reports page, it just keeps putting it here. I obviously have no clue as to what I'm doing. I apologize for any inconvenience. I wanted to only post the problem I experienced above in case it was or became a bug problem that might bother other players. I will try to keep reading and understand the format here and post when I hopefully might know a bit more. Thanks to any who've tried enlightening me. :-)

Confused newbie...--EveryWitchWayURun 22:22, 28 June 2006 (BST)

• Perhaps you should click on the "article" button before trying to post... anyway, I did it for you. --V2Blast ^{T•P!•C•SR} 16:12, 10 August 2006 (BST)

Losing 2 ap everytime i move once.

I keep losing 2 ap everytime i move to one space, because of this i died. I'm not at all happy and it is still doing it when i am a zombie as well. No i am not clicking the mouse twice just i single click. Sometimes i would end up with a -1 ap. Could someone have it looked into my username is sciice. —The preceding unsigned comment was added by Sciice (talk • contribs) .

Can you provide a link to your profile? Cyberbob  Talk  08:02, 31 August 2006 (BST)

Action bug

when loged on as vahalian i loged in as dead and pressed stand up when i pressed it i automaticly logged off i loged on again and tryed stand up again and once again it logged me off again i pressed back a couple times and it didn't show me logging on again but it did show me standing up then i pressed enter church then I logged off again is this a bug or just my computer

--Vahalian 02:38, 3 September 2006 (BST)

Reduced Hit Percentage

When I logged in today all my characters hit percentages have been cut down. I read about the same problem occuring with Zombie Characters but my character isn`t a Zombie. How can I fix this?--Dr Ug 13:01, 4 October 2008 (BST)

Visually, as in the drop-down menus all have reduced percentages? You might be in the dark; step outside and see if they get better. If you get the same percentage listed on the drop-down menu and are not hitting anyone, maybe you've tripped up a zerg flag somewhere? Pakopako 03:13, 16 December 2008 (UTC)