AtomicBlom / WeirdingGadget

A server friendly chunk loader for Minecraft
GNU Lesser General Public License v3.0
8 stars 7 forks source link

Doesn't reactivate on reboot? #9

Open generrosity opened 6 years ago

generrosity commented 6 years ago

Hello!

We are playing on a slightly modified Foolcraft3 server. The pack is set to one-chunk I believe. It seems after the daily reboot that gadgets aren't reactivating.

Is there any good way you suggest to test/confirm this? Is it intentional?

AtomicBlom commented 6 years ago

Do you mean that the gadget is set to 1 chunk, or the server is set to a player can only load a single chunk?

I have heard reports of this happening, but I've been struggling to reproduce it, any further information you have would be useful.

Also, what version of Minecraft/Weirding Gadget are you using?

arketec commented 6 years ago

I too play on a Foolcraft 3 server that has this issue. The gadget is configured to only load 1 chunk, but players load chunk normally.

Tech info: Minecraft version: 1.12.2 Mod version: 1.12.2-2.0.5 Mod pack version: 1.4.5

The gadgets stop spinning after the server restarts, and must be manually activated again. This didn’t happen immediately, but after the server had been up for about a month and a half, and I specifically noticed when the mod pack was last updated to 1.4.5, so it may be a conflict with one of the other mods in the pack.

generrosity commented 6 years ago

I'll see if I can get edge cases, and situations that look a little unusual. I'll wait for the overnight reboot, but I've got an initial query below;

Forge 14.23.4.2705 Weirding - 1.12.2-2.0.5

After a standard /stop reboot of the server, the Weirding is still spinning. But, on first right click, the server notes this below;... and each one does this ...

[20:15:51] [Server thread/INFO] [weirdinggadget]: Waking up Chunk Loader at BlockPos{x=-766, y=52, z=-1769} because generrosity placed/interacted with it [20:15:51] [Server thread/INFO] [weirdinggadget]: Active state of chunk loader at BlockPos{x=-766, y=52, z=-1769} is now true

On logout, there is a confirmation (maybe the seconds-past-X can be turned into a datetime?) ...

[20:16:00] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer]: generrosity left the game [20:16:02] [Server thread/INFO] [weirdinggadget]: All players have gone offline. Ticket is scheduled to expire at world time 98603263

AtomicBlom commented 6 years ago

I could calculate it, but world time isn't a specific time of day, and will only ever be accurate as long as the server doesn't restart or skip any ticks, so you'd have to take it with a grain of salt.

I'll have to double check, but if the spinner is rotating, that should mean that it is correctly chunk loading.

My initial concern was that Forge was rejecting our request to load chunks, but the logs you've provided don't suggest that is the case (otherwise the active state wouldn't change).

generrosity commented 6 years ago

Thanks! Unfortunately I didn't get a change to re-confirm this morning after the FTBU 3am reboot if the spinning had stopped again. And I haven't tested a force-kill-java of the server yet either.

I still find it strange that after logging in, and finding it spinning, then righclicking gave the 'Waking up Chunk' log once. That doesn't .... sound right?

I see what you mean with the time. I thought Weirding was based on real life time, rather than ingame ticks. I think that saying "scheduled to expire in 7k ticks (2.6hr of uninterrupted game time)" is more useful than worldtime which I don't know how to look up?