Update DestroySystem.py #9
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Apparently several players told me that / destroyall returned some duplicate objects, I wrote some lines to prevent this .... I have tested it in version 1.7.5. , But impatio that in 1.7.6 the same thing will happen. Maybe you can check if it's true? ,regards
|
Wuts this? |
|
/destroyall duplicate items, very weird bug i realized today when a player complained me. i never knew this though. : Place a wooden gateway and write /destroyall and break it , you will get 2 wooden gateway in inventory and you can repeat it, again and again, to get an unlimited number of gateways =place and break with /destroyall cmd and then recycle all to get free wood. Please fix. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Apparently several players told me that / destroyall returned some duplicate objects, I wrote some lines to prevent this .... I have tested it in version 1.7.5. , But impatio that in 1.7.6 the same thing will happen. Maybe you can check if it's true? ,regards