[Not a bug]Item Duplication

Question

[Not a bug]Item Duplication

Interestking opened this issue 4 years ago · 9 comments

Interestking commented 4 years ago

Common sense Info

I play...
- With a large modpack
- Only with CQR and it's dependencies
The issue occurs in...
- Singleplayer
- Multiplayer
I have searched for this or a similar issue before reporting and it was either (1) not previously reported, or (2) previously fixed and I'm having the same problem.
I am using the latest version of the mod (all versions can be found on github under releases)
I read through the FAQ and i could not find something helpful (FAQ)
I reproduced the bug without any other mod's except forge, cqr and it's dependencies
The game crashes because of this bug

Versions
Chocolate Quest Repoured: 1.20.1A
Forge: 14.23.5.2847
Minecraft: 1.12.2

Describe the bug
A clear and concise description of what the bug is.
When using a block on a table in a dungeon, the blocks in your hand are cloned and put in your off-hand. Efectively doubling them. However, this won't work if you use something other than blocks, have only one if your hand, or if you're in creative mode.
To Reproduce
Steps to reproduce the behavior:

Go to a dungeon (or spawn one in) then hold any number (above one) of any block in your hand
Use blocks on a table

.
.
.
4. See error

Expected behavior
A clear and concise description of what you expected to happen.
What I expected to happen was for a block to be displayed, and then retrieved by right clicking it again.
Screenshots
If applicable, add screenshots to help explain your problem.
https://user-images.githubusercontent.com/67964034/97100047-fef66280-1665-11eb-874f-f6c257cb19dc.png
https://user-images.githubusercontent.com/67964034/97100054-1b929a80-1666-11eb-9335-cdad5ac78668.png
https://user-images.githubusercontent.com/67964034/97100067-35cc7880-1666-11eb-945e-1d00c4533663.png
https://user-images.githubusercontent.com/67964034/97100071-40870d80-1666-11eb-9183-47098e51e393.png
https://user-images.githubusercontent.com/67964034/97100078-4b41a280-1666-11eb-9986-af33c2767551.png https://user-images.githubusercontent.com/67964034/97100087-5694ce00-1666-11eb-864a-4b7e0b885967.png
https://user-images.githubusercontent.com/67964034/97100094-67454400-1666-11eb-9d54-7d78b1b32e8b.png

Other
Please note: log files and crash reports should be uploaded as a FILE and not as a copy paste of the text of it here. Upload the file to a site like pastebin or similar and link it here!!

Link to Crash report file:
Link to Log file:
Other mods (that are necessary to produce the bug):
Other mods (that are also installed):
CQR config folder (link, only if you changed the configs):
Other mod's configs (link):

LordEpos · Answer 1 · 2020-10-25T06:13:49.000Z

Thanks for bringing this to our attention

DerToaster98 · Answer 2 · 2020-10-25T08:11:57.000Z

Please verify that this is also present in the latest version. The one you are using is outdated.

DerToaster98 · Answer 3 · 2020-10-25T08:16:54.000Z

Current version is 1.21.9, this will only be investigated if the bug is present in the latest (1.21.9) version.

DerToaster98 · Answer 4 · 2020-10-25T08:59:12.000Z

Tried reproducing it in the master branch, the issue is not present there, issue will be closed.

Meldexun · Answer 5 · 2020-10-25T11:19:47.000Z

On the screenshots I can see other modded items. So at least the screenshots were not made with only CQR. Also I just installed forge 2847 and cqr 1.20.1 and I couldn't reproduce it.

DerToaster98 · Answer 6 · 2020-10-25T11:36:54.000Z

Closing issue now, this won't be investigated.

Not reproduceable in latest version
Not reproduceable in given version (1.20.1)
Not reproduceable in workspace

Interestking · Answer 7 · 2020-10-27T13:42:15.000Z

I've heard (and just checked to make sure) that in the newer versions of the mod, there is no barrier stopping you from breaking blocks, and I think that the barrier is the cause of the problem. I just tried it in the newest version, and it didn't work. About the "extra mods", in my screenshots, I only had cqr, llibrary, and soulbound armoury (which was said to be an optional dependency), anyways, I just tried it without soulbound armoury, in (1.20.1A) and the bug still happened. Also, did you try it in survival mode inside of a dungeon? If you're in creative mode, you are allowed to break blocks, so the bug won't happen.

…

On Sun, 25 Oct 2020 at 07:37, DerToaster98 ***@***.***> wrote: Closed #229 <#229>. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#229 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQGQZAWB4SPXPFSNRQTQZVDSMQEWHANCNFSM4S6DKBJA> .

DerToaster98 · Answer 8 · 2020-10-27T15:25:20.000Z

So apparently you think you know more about testing, coding, etc then the devs or what? Of course we tried it in survival and INSIDE A DUNGEON. Also the protection zone IS in the newer version but disabled by default. It was tested with and without the protection zone and it doesn't matter, this "bug" has nothing to do with the protection zone. It probably is a mistake present in that version. The next time you report something: Verify it is present in the newest version and don't set yourself on a position higher than the devs like you do in your most recent post on this ticket. Also "dependency" means requireddependencies, the ones it needs to actually run, not some optional stuff Am 27.10.2020 um 14:42 schrieb Interestking:

…

I've heard (and just checked to make sure) that in the newer versions of the mod, there is no barrier stopping you from breaking blocks, and I think that the barrier is the cause of the problem. I just tried it in the newest version, and it didn't work. About the "extra mods", in my screenshots, I only had cqr, llibrary, and soulbound armoury (which was said to be an optional dependency), anyways, I just tried it without soulbound armoury, in (1.20.1A) and the bug still happened. Also, did you try it in survival mode inside of a dungeon? If you're in creative mode, you are allowed to break blocks, so the bug won't happen. On Sun, 25 Oct 2020 at 07:37, DerToaster98 ***@***.***> wrote: > Closed #229 > <#229>. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#229 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AQGQZAWB4SPXPFSNRQTQZVDSMQEWHANCNFSM4S6DKBJA> > . > — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#229 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJH4N72HEAJ5HLO6RQVZZ63SM3E4VANCNFSM4S6DKBJA>.

-- Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft. https://www.avast.com/antivirus

Meldexun · Answer 9 · 2020-10-27T17:48:46.000Z

To clear this up this issue is present in CQR v1.20.1 but in newer CQR versions the issue isn't present because of the changes that were made to the protection system.
(It actually is a problem with the cqr table block but one probably needs another mod to reproduce this issue in the newest version of CQR and because of that there won't be a bugfix build)

(Also the protection system is still there and still active by default in the newest version of cqr.)

Share to