mojira.dev
MC-267491

tick.mcfunction no longer running consistently

After updating to 1.20.4, my Minecraft Realm has been inconsistent with processing functions in my custom data pack. It's erratic, but every few minutes or so everything I added stops working. I made no changes to the data pack, and combined my players had hundreds of hours on 1.20.2 without issue, so I'm confident it's something to do with the update (I'm guessing related to the new tick command?)

I don't know what's happening exactly so my description is gonna be a little rough, but basically I have my own clock that I increment each tick, which used to work consistently. But now sometimes it gets confused and doesn't process a tick at all, or processes many ticks at once. Both of which break my clock, which breaks my whole data pack.

Also, I'm unsure but it seems like some of my functions are returning early because of it? Or maybe they're just being interrupted, I don't know. All I know is I have several functions where the first line is running but the last line is not, with no logic control in between to make that happen. This may not even be related, but it started happening at the same time.

 

I know this is a weird issue, but any help would be greatly appreciated!

Linked issues

Comments 8

This is not a helpdesk. It's expected that some things in older data packs will break in newer versions of Minecraft. That's why pack version is a thing.

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?

What you're describing is just server-side lag.
My data packs have had no issues at all with functions being skipped or run several times. Make sure your max command chain length and max command fork count aren't being hit.

Also, just to be clear, I am not trying to be rude. You asked for help and this is not the place to ask for help, this is the place to report bugs. That being said, if it only affects Realms, it should be reported in the REALMS project section.

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!

Make sure your max command chain length and max command fork count aren't being hit.

In large data packs, the default values for these game rules can be hit relatively easily, and they cut off functions when it gets hit.

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).

If you do not use the tick command, it should not break anything.

You also need to attach some files to reproduce the bug (for example, the data pack you are using, a debug by /debug command).

Mahandal

(Unassigned)

Unconfirmed

(Unassigned)

1.20.4

Retrieved