mojira.dev

Mahandal

Assigned

No issues.

Reported

MC-267492 My data pack broke with 1.20.4 Duplicate MC-267491 tick.mcfunction no longer running consistently Invalid MC-258709 Scoreboard doesn't track broken oak logs Invalid

Comments

I did read the update logs, that's why I'm guessing it has to do with the tick command being added.

 

Did you have a point or are you just here to agitate?

Thank you for actually trying to help!

Yes the max command limit could explain some of my symptoms, though it's set to the max integer value so I still think it's a bug if it's being hit, and it doesn't explain why my world would randomly run much faster than usual.

It's inconsistent so it's hard to test but sometimes the realm ticks faster than 20 times per second, which breaks things for me. That's why I'm assuming the tick command is involved, indirectly at least (cause I'm not using it).

I didn't ask for help for me and no one else, I reported a bug that is difficult to fix and said that any help would be appreciated because I know that immediately fixing exactly what went wrong is unlikely. Though it does seem you've decided being kind is inappropriate here for some reason, so my bad.

 

But it's not just server-side lag, I made my realm resilient to that years ago. I'm a professional software engineer, I know what lag looks like. There are lines of code that should be run sequentially that are being interrupted by some unknown factor, introduced in 1.20.4 (or 1.20.3).

 

And it does not ONLY affect realms, it also affects the same world in single-player. But I don't care about single-player, I care about my realm. I mentioned the realm to provide context, I am not confused about where I am.

 

If it's hard to recreate, that makes my information that much more valuable, cause whatever is wrong seems like a deep issue in Minecraft's code (again, presumably related to the changes made to enable the tick command). If everyone always had my issue, I wouldn't need to be here to report it in the first place. I know most people aren't experiencing what I'm experiencing, that's why I'm here.

 

If you have no idea and no way to help, that's fine. But I'm providing info on a real bug that developers at Mojang should like to know about. If at some point someone who actually wants to fix things reads this, please let me know if there's anything I can do to help!

What else am I supposed to do when people just ignore my problems? I know it's a weird bug but it's even weirder for me that yall have just decided it's not a bug.

I'm using the latest pack version, and nothing in between version 18 and version 26 changed anything for me. This is a bug report, why you gotta be rude about it?

I am dumb and ashamed.