Matthew Lyons
- Speak2erase
- speak2erase
- Europe/Stockholm
- Yes
- No
W
Hen throwing a loyalty trident while still raising the trident, it deletes.When throwing a loyalty trident while still raising the trident, it deletes, or appears to, until relog. Not to sure why.
NOTE THIS IS ON A SERVER
The bug
When throwing a trident while still raising the trident, it deletes, or appears to, until relog. This happens both on a server and on a single player world. This is only client side, as in the player data files the trident is still there. Loyalty has no effect.
Sometimes this crashes the server or game. Not to sure if this is just me...
Trident disappearswhen throwing it while still raising itTrident disappears from inventory while throwing it when the cool down is not full
The bug
When throwing a trident while still raising the trident, it deletes, or appears to, until relog. This happens both on a server and on a single player world. This is only client side, as in the player data files the trident is still there. Loyalty has no effect.
Sometimes this crashes the server or game. Not to sure if this is just me...
The bug
When throwing a trident while still raising the trident, it deletes, or appears to, until relog. This happens both on a server and on a single player world. This is only client side, as in the player data files the trident is still there. Loyalty has no effect.
Sometimes this crashes the server or game. Not to sure if this is just me...
I am editing this to keep it at the top...
The bug
When throwing a trident while still raising the trident, it deletes, or appears to, until relog. This happens both on a server and on a single player world. This is only client side, as in the player data files the trident is still there. Loyalty has no effect.
Sometimes this crashes the server or game. Not to sure if this is just me...
I am editing this to keep it at the top...
The bug
When throwing a trident while still raising the trident, it deletes, or appears to, until relog. This happens both on a server and on a single player world. This is only client side, as in the player data files the trident is still there. Loyalty has no effect.
Sometimes this crashes the server or game. Not to sure if this is just me... When I get my recording software running I will dd footage of this bug in action.
The bug
When throwing a trident while still raising the trident, it deletes, or appears to, until relog. This happens both on a server and on a single player world. This is only client side, as in the player data files the trident is still there. Loyalty has no effect.
Sometimes this crashes the server or game. Not to sure if this is just me... When I get my recording software running I will add footage of this bug in action.
Are you on a server?
Gravel falling on torch crashes localhost server.
There is a new repeater inconsistency that just popped up in 1.16. I tested every single version from 1.11.2 to 1.15.2, and they all exhibit this behaviour:
There is a signal strength of 1 going to a Redstone dust that climbs up onto 2 different blocks. Prior to 1.16, that repeater would not get powered. Now, in 1.16,the repeater is powered. My guess is that this has something to do with the recent Redstone dot change.Affects 1.16+.
There is a new repeater inconsistency that just popped up in 1.16. I tested every single version from 1.11.2 to 1.15.2, and they all exhibit this behaviour:
There is a signal strength of 1 going to a Redstone dust that climbs up onto 2 different blocks. Prior to 1.16, that repeater would not get powered. Now, in 1.16,
the repeater is powered. My guess is that this has something to do with the recent Redstone dot change.
Affects 1.16+.
There is a new repeater inconsistency that just popped up in 1.16. I tested every single version from 1.11.2 to 1.15.2, and they all exhibit this behaviour:
There is a signal strength of 1 going to a Redstone dust that climbs up onto 2 different blocks. Prior to 1.16, that repeater would not get powered. Now, in 1.16,
the repeater is powered. My guess is that this has something to do with the recent Redstone dot change.
Affects 1.16+.
Yes, this is a "repost." S
Ome mod took down my other bug report because I had shaders in them. THIS IS RUNNING ON A VANILLA CLIENT AND SERVER.There is a new repeater inconsistency that just popped up in 1.16. I tested every single version from 1.11.2 to 1.15.2, and they all exhibit this behaviour:
There is a signal strength of 1 going to a Redstone dust that climbs up onto 2 different blocks. Prior to 1.16, that repeater would not get powered. Now, in 1.16,
the repeater is powered. My guess is that this has something to do with the recent Redstone dot change.
Affects 1.16+.
Yes, this is a "repost." Some mod took down my other bug report because I had shaders in them. THIS IS RUNNING ON A VANILLA CLIENT AND SERVER.
There is a new repeater inconsistency that just popped up in 1.16. I tested every single version from 1.11.2 to 1.15.2, and they all exhibit this behaviour:
There is a signal strength of 1 going to a Redstone dust that climbs up onto 2 different blocks. Prior to 1.16, that repeater would not get powered. Now, in 1.16,
the repeater is powered. My guess is that this has something to do with the recent Redstone dot change.
Affects 1.16+.
Yes, this is a "repost."
Somemod took down my other bug report because I had shaders in them. THIS IS RUNNING ON A VANILLA CLIENT AND SERVER.There is a new repeater inconsistency that just popped up in 1.16. I tested every single version from 1.11.2 to 1.15.2, and they all exhibit this behaviour:
There is a signal strength of 1 going to a Redstone dust that climbs up onto 2 different blocks. Prior to 1.16, that repeater would not get powered. Now, in 1.16,
the repeater is powered. My guess is that this has something to do with the recent Redstone dot change.
Affects 1.16+.
Yes, this is a "repost." A mod took down my other bug report because I had shaders in them. THIS IS RUNNING ON A VANILLA CLIENT AND SERVER.
There is a new repeater inconsistency that just popped up in 1.16. I tested every single version from 1.11.2 to 1.15.2, and they all exhibit this behaviour:
There is a signal strength of 1 going to a Redstone dust that climbs up onto 2 different blocks. Prior to 1.16, that repeater would not get powered. Now, in 1.16,
the repeater is powered. My guess is that this has something to do with the recent Redstone dot change.
Affects 1.16+.
Yes, this is a "repost." A mod took down my other bug report because I had shaders in them. THIS IS RUNNING ON A VANILLA CLIENT AND SERVER.
There is a new repeater inconsistency that just popped up in 1.16. I tested every single version from 1.11.2 to 1.15.2, and they all exhibit this behaviour:
There is a signal strength of 1 going to a Redstone dust that climbs up onto 2 different blocks. Prior to 1.16, that repeater would not get powered. Now, in 1.16,
the repeater is powered. My guess is that this has something to do with the recent Redstone dot change.
Affects 1.16+.
Yes, this is a "repost." A mod took down my other bug report because I had shaders on in screenshots in them. THIS IS RUNNING ON A VANILLA CLIENT AND SERVER.







I have this issue on my server
This is an intended feature I think.
Despite other duplicate issues being resolved, this bug still affects client side. When doing this on one of my servers It caused the server to bug out whenever I logged in, and the server crashes immediately. Deleting the player data resolved the issue, but on client this affect does not appear to happen. My launcher for some reason doesn't log crash reports or open a log...
Its item duplication or Item destruction
/kill affects a targeted player and or entity
Due to recent trident changes, this may have accidentally been fixed. After all, it has been nerfed quite a bit. Try recreating it with enchantments in some of the older snapshots.
I can not reproduce, as I have tried multiple methods. Any of these methods work in earlier snapshots. IE:Up to 18w012b (For me anyways)
Conclusion:Bug has been fixed... for now. Hooray! It may return if the trident gets nerfed again... So keep your eyes peeled!
This is expected behavior when it comes to blocks with 1.5 tall collisonboxes.
It's not modded. That's a screenshot from a vanilla server with an forge client. I can go ahead and post a screenshot of this working on a non-forge client. Well, I did. The top screenshot is from a non-modded client, and the bottom screenshot is from a vanilla server with a client with only optifine on it.
Plus, go ahead and test this yourself. You'll see this bug I'm reporting happen.
Sure!
Try /playsound minecraft:music.creative music @p ~ ~ ~ in a creative world with cheats on
You could have music turned off as well
Be patient too, people won't respond right away
Did you use the playsound command?
Hm. I'm annoyed because that broke a lot of my Redstone computers. Time to make a new one, I guess.