Skip to content
This repository has been archived by the owner on Jan 26, 2019. It is now read-only.

Duplicate pixelmon #529

Open
Dpa1991 opened this issue Sep 18, 2016 · 9 comments
Open

Duplicate pixelmon #529

Dpa1991 opened this issue Sep 18, 2016 · 9 comments

Comments

@Dpa1991
Copy link

Dpa1991 commented Sep 18, 2016

You will receive NO SUPPORT if you do not follow the template below. (Vous ne receverez pas aucune aide si vous effacer ce modèle)

Server Log: (Use Pastebin or Github Gist)
N/A
FML Log(s): (Use Pastebin or Github Gist)
N/A
Explanation of issue:
When you put your pixelmon in a PC and type /kill it will duplicate the pixelmon by returning them to your party and leaving them in your PC. This is not a regular dupe as when you send one out - the other one will simply force you to retrieve it instead of sending the second one out. These can still be traded however.
How to recreate this issue:
See above
Modpack Name: (Only if public)
http://www.technicpack.net/modpack/sft-pixelmon.162655
Mods Installed:
http://www.technicpack.net/modpack/sft-pixelmon.162655/mods
Plugins Installed:
Lots, but this isn't the problem. I tested this with kcauldron running the same plugins and the issue did not occur. Switch to Thermos and the problem occurs.
Warmroast Report: (Optional)

Thermos Version:
Build 58
Forge Version:
1558 and 1614

Additional information:
I have tested Build 58,57 and 56 all have the issue.

EDIT
After further testing, this happens after any death. almost every time it will duplicate the pixelmon, but in other cases it will just delete them.

@Dpa1991
Copy link
Author

Dpa1991 commented Oct 3, 2016

Anyone have any ideas?

@Dpa1991
Copy link
Author

Dpa1991 commented Oct 24, 2016

Did some further testing, the problem occurs on build 35. 35 and lower does not have this issue.

@sameer
Copy link
Member

sameer commented Oct 24, 2016

Thank you for noting that -- I am currently in the process of rebuilding Thermos and will see what might've caused that in the commit history.

@Dpa1991
Copy link
Author

Dpa1991 commented Oct 25, 2016

Awesome, glad to hear. If theres anything I can do to help test let me know.

Edit: Forgot to mention, Build 31 works fine. 32,33 and 34 are labeled BROKEN so I didn't test those, but on build 35 this particular issue occurs.

@LemonNick
Copy link

Can you quickly make a fix? I can pay.=)

@lurr
Copy link

lurr commented Dec 5, 2016

@LemonNick this will not speed this up, due to #577 ;(

@Dpa1991
Copy link
Author

Dpa1991 commented Jan 5, 2017

Is it safe to say this is abandoned yet? @robotia

@Eufranio
Copy link

Eufranio commented Jan 5, 2017

Thermos is

@Dpa1991
Copy link
Author

Dpa1991 commented Jan 6, 2017

That's what I meant, Thermos in general -- not this ticket in particular.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants