Novârch

It seems that was the issue, setting the arrows velocity to 0 instead of setting it's position every tick fixed the issue, but now I have a new issue, all arrows face south during timestop. I've been trying to do that, but to no avail, how am I supposed to send ALL the velocities in one packet and map them to the correct entity?

Make your own thread, your issues are mostly likely unrelated.

Update, 1.7 is no longer supported on this forum.

Stop using MCreator.

Why does the MuddyPigEntity.GoToMudGoal have a higher priority than TemptGoal? Seems like an obvious issue.

http://export.mcpbot.bspk.rs/

Reflection.

Thanks for the help, I think I've made some progress on this, the packet should in theory set an entities velocity on the client to it's velocity on the server, but I'm still getting the same graphical issues, I have the effect down, everything stops, but some entities like arrows look glitchy. Here's a gif of the glitch, and no that is not a continuous loop of an arrow falling, it just stays like that until I undo the effect. Yeah, I am. I'm pretty disappointed will all the current ones, they're rarely updated and a certain 1.12 ones creator is incompetent at modding.

In a tick event.

What should I send SEntityVelocityPacket to, PacketDistributor#TRACKING_ENTITY? I haven't found much info online on how to send packets to entities.

Why..?

In my mod I've made a "timestop" effect where all entities are supposed to stop moving and keep their velocity after the effect is undone. Everything currently works perfectly except the rendering of certain entities(arrows, item entities, etc.), they appear to continue moving and continuously snap back to their original position, but when I disable the effect their position and velocity are correct. Is there a way to fix this rendering issue, if so how? The mod's code can be found here, on GitHub, the event fires each tick from a custom entity.

1.12 is no longer supported on this forum. Please update to a modern version of Minecraft to receive support.

I gave you 2 good examples, the vanilla dropper and hopper classes.

A file called debug.log, your OS's file browser should have a search function.

Hard to believe someone actually updated, great! I'd start with looking at how the vanilla hopper and dropper classes worked then maybe write an int that I would increment once per tick and write to NBT, then check if n % 600 == 0.

ClientPlayerNetworkEvent#LoggedInEvent

debug.log

1.12 is no longer supported on this forum. Please update to a modern version of Minecraft to receive support.

1.14

Please learn how basic reflection works.

Reflection

Post your version and debug.log.

Not sure if this is it but doesn't this method have 4 parameters? It's in the docs and it seems pretty important. It seems like you are working for an unsupported version, please update to a modern version on Minecraft to receive support. To break it down, FMLPreInitializationEvent no longer exists, @EventHandler no longer exists and your message registration code is completely different than it is in supported versions.

What about when they're fired from a crossbow?