Page 1 of 7

Beta bug reporting

PostPosted: 27 Jul 2016 20:58
by MrMasochism
Hey Guys,

Thanks for all the error reporting that's going on. We'll be getting more builds out constantly till we're over the bugs but while this is happening I thought I'd just share some bug reporting guidelines so that we can get this done a lot more quickly and efficiently.

1- Check what we've already fixed.
We are continually fixing bugs that have been reported to us. While we are in this beta phase, we will be maintaining a wiki page listing the bug fixes that are ready for the next beta release. If a bug you have encountered is already in that list, you don't need to report it as we have already fixed it for the upcoming Pixelmon version.

2- Check previous reports.
I know it can be difficult to go over previous reports and it feels like it's taking lots of time for you but realise that for us wading through a heap of duplicate reports is a difficult task and one that gets very confusing. Please check previous reports and if what you came to report has already been reported then don't make a new report. If it has been reported and you have more information to provide us with then add it to the existing report.

3 - Give us all the important details.
Plenty of the current reports don't even say which of the 2 betas the error has occurred on. Please provide us with the Minecraft version, beta version, Forge version and the full crash logs if they are available.

4 - Be patient.
Fixing bugs takes lots of time. I spent at least 4 hours yesterday (not including time others also spent on the same problem) trying to work out why the Pokémon were freezing in mid-air. Pixelmon is an enormous mod with a ridiculous amount of content which means that we can't see the possible permutations of all our code changes. Some bugs we fix will introduce others but that of course is the point of a beta. You are helping us get this right!

5 - One bug per report.
Part of keeping things organised and being able to track what we've fixed is the ability to have each bug in it's each topic, this lets us tick things off and get proper feedback on each issue individually. Please don't open tickets and put a big list of things wrong in them!

We are already making good progress, a battle pausing bug fix will be released soon!
MrM

Beta bug reporting

PostPosted: 27 Jul 2016 21:31
by MrMasochism
Just added point 4

Beta bug reporting

PostPosted: 27 Jul 2016 21:59
by Some Body
We've added a page that lists fixes that are ready for the next release. The newspost has been updated accordingly.

Re: Beta bug reporting

PostPosted: 28 Jul 2016 07:57
by FrostEffects
Some Body wrote:We've added a page that lists fixes that are ready for the next release. The newspost has been updated accordingly.

-Inserts link to said pages here- ...?

Beta bug reporting

PostPosted: 28 Jul 2016 08:01
by bvanseghi

Beta bug reporting

PostPosted: 28 Jul 2016 08:05
by FrostEffects
hotlinks aren't showing in the launcher. My Bad.

Beta bug reporting

PostPosted: 28 Jul 2016 08:08
by bvanseghi
Don't sweat it.

Re: Beta bug reporting

PostPosted: 28 Jul 2016 08:16
by Triineax
Hey! Everytime when i battle a pokemon and try to send out another pokemon, my game says: Loading...
And it keeps doing that! It would be great if you could fix that bug, THANKS.
My IGN is: OmgItzAFlyingPig ,
BTW.




Peace,

Re: Beta bug reporting

PostPosted: 28 Jul 2016 08:34
by bvanseghi
Triineax wrote:Hey! Everytime when i battle a pokemon and try to send out another pokemon, my game says: Loading...
And it keeps doing that! It would be great if you could fix that bug, THANKS.
My IGN is: OmgItzAFlyingPig ,
BTW.




Peace,


Bugs should be reported to the bug tracker found here: http://www.pixelmonmod.com/tracker.php?p=2
Remember to double check and make sure that bug was not already listed in the tickets.

Beta bug reporting

PostPosted: 29 Jul 2016 11:46
by uuno23
was trying to run pixelmon 5.0.0-Beta3