Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

1.20.1 Forge Redstone differs from Vanilla and Fabric #9973

Open
eeble1 opened this issue May 14, 2024 · 3 comments
Open

1.20.1 Forge Redstone differs from Vanilla and Fabric #9973

eeble1 opened this issue May 14, 2024 · 3 comments
Labels
Triage This request requires the active attention of the Triage Team. Requires labelling or reviews.

Comments

@eeble1
Copy link

eeble1 commented May 14, 2024

Minecraft Version: {1.20.1}

Forge Version: {Forge version. 47.2}

Steps to Reproduce:

  1. download the linked world (Orbital Strike 4.0)
  2. use the cannon
  3. set the command blocks to use @ A instead of the username present
  4. go to spectator and watch the bottom TNT duper (first one to activate)

Description of issue:
It seems that both the timing as well as the normal game features differ in forge as whenever I use the cannon the timing for pushing the TNT is off as well as whatever TNT does get put on the cannon never makes it to target.

Link to Files
https://www.mediafire.com/folder/88qrgise22lax/Orbital_Strike_Cannon

@eeble1 eeble1 added the Triage This request requires the active attention of the Triage Team. Requires labelling or reviews. label May 14, 2024
@LexManos
Copy link
Member

To debug this I need something far simpler then this massive contraption. At the end of the day its the TNT duplicator that is the issue, so find a isolated case to test that.

@eeble1
Copy link
Author

eeble1 commented May 15, 2024

I will try to create a simpler version of the mechanism used in the cannon later. I also want to ask whether the main mechanisms behind the cannon such as building momentum on the TNT stuck in stasis would still work on forge and whether it would make its way to target or whether the main mechanisms behind it are broken by forge. if the mechanisms work on forge what I could do is fine tune the cannon in order to make it work within forge.

@LexManos
Copy link
Member

Chunk loading is modified by Forge, however in theory it should use the same chunk ticketing system as vanilla. Just with the ability for mods to add extra ticket types.
So.. in theory it should be fine.
The issue is that this entire process exploits bugs in Minecraft. Sometimes bugs are fixed by Forge. But typically with intentional fixes and links to the bug reports on Mojang's tracker. I can't say if any of those changes interact with anything in this specific contraption. Which is why smaller reproduction cases are needed.

Also for future note, a bit more detailed reproduction steps is also helpful.
We had no idea that use the cannon meant that we needed to grab at least a trim x, trim z, and payload type from the chest, add it to the minecart right click one note block, then right click another. I only found that out by googeling the name that was in the command blocks and seeing what I could find.

set the command blocks to use @ A instead of the username present also was slightly better because we only found 3 command blocks, but what we actually had to do was edit the two touching each other and then add a button to the pair. and then press that button after starting the firing sequence {the 2nd note block}

And then go to spectator and watch the bottom TNT duper (first one to activate)
Took us feakin ages to figure out where the tnt duper even was, as the contraption is quite large, and it does literally nothing unless you do the first step correctly {which again we had no way of knowing how to do}
I was able to find a TNT duper explanation here and here. But none that looked anything like what your setup is.

Overall, my main point is that when reporting issues, its nice to have a example of the issue but it needs to be something A LOT simpler and better explained. So even tho we tried, and it was kinda fun digging into it, we had no idea how to isolate the issue and verify it. Which is needed to be done before we can fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Triage This request requires the active attention of the Triage Team. Requires labelling or reviews.
Projects
None yet
Development

No branches or pull requests

2 participants