if the changes seem pretty minor we could always roll back to the working version from a few days ago; the server restarts seemed to greatly help lag-wise and could happen more often, twilight could be deleted map-wise and a ban placed on going there. Better than a map wipe if nothing much has changed surely ?

water based.

it looks nothing in the jar file has changed, but some mods have.

squaffle, restarts should be happening every 24 hours.

yeah, the daily restarts have helped immensely; was just thinking if people wanted it even smoother then even more frequent ones would probably help even more

I don't know the effect / load on the server, but I reckon a server restart every 6 or 8 hours should keep things running smoothly, without affecting gameplay too much

Since the upgrade to 1.2.1 - I have now been able to log in. I have found 1 bug so far - and that's if you try to right click (anything) whilst holding the red book you get to start with (which has no name), I instantly get crashed out of the game with a fatal error, but can log right back in without any issues.

throw that book in lava, it hasn't worked for some time now

as a random point of interest I haven't been able to log in since the update; I just timeout.
Looking at the log I would imagine it's something to do with

[14:01:42] [Netty Client IO #1/ERROR] [FML]: NetworkDispatcher exception
io.netty.handler.timeout.ReadTimeoutException

though I don't know too much about that sort of thing; can't be on much atm as very busy so it's no biggie, just if someone's experienced something similar

you double sure u've updated to 1.2.1? have u tried deleting/renameing the folder and re-downloading it?

the server seems to have developed a substantial amount of lag that seems to come in small/medium bursts rather frequently even after a restart.

I'm worried that someone has setup a under-performing quarry (spewing stuff everywhere) or has perhaps by accident has something chunk loading (there are some blocks not listed as chunk loaders) that can be causing this?

It's something at your base causing a crash. I went to have a look see, but now constantly crash when trying to log back in.

seems to be a NetworkDispatcher exception being thrown.

[14:52:42] [Client thread/INFO] [journeymap]: World ID has been reset.
[14:52:43] [Netty Client IO #11/INFO] [FML]: Attempting connection with missing mods [AromaBackup, CustomMainMenu, journeymap, notenoughkeys, ResourceLoader, WailaHarvestability] at SERVER
[14:52:46] [Client thread/INFO]: Connecting to minecraft.crazy-fools.co.uk, 24000
[14:52:48] [Netty Client IO #12/INFO] [FML]: Server protocol version 1
[14:52:48] [Netty Client IO #12/INFO] [FML]: Attempting connection with missing mods [AromaBackup, CustomMainMenu, journeymap, notenoughkeys, ResourceLoader, WailaHarvestability] at SERVER
[14:52:48] [Netty Client IO #12/INFO] [FML]: Injecting existing block and item data into this client instance
[14:52:48] [Netty Client IO #12/INFO] [FML]: Applying holder lookups
[14:52:48] [Netty Client IO #12/WARN] [FML]: Unable to lookup chisel:cobblestoneWall for public static com.cricketcraft.chisel.block.BlockMarbleWall com.cricketcraft.chisel.init.ChiselBlocks.cobblestoneWall. Is there something wrong with the registry?
[14:52:48] [Netty Client IO #12/INFO] [FML]: Holder lookups applied
[14:52:48] [Client thread/INFO] [OpenMods]: openmods.network.IdSyncManager.decodeIds(IdSyncManager.java:113): Received data store for key events, packet size = 196
[14:52:48] [Client thread/INFO] [OpenMods]: openmods.network.IdSyncManager.decodeIds(IdSyncManager.java:113): Received data store for key rpc_methods, packet size = 336
[14:52:48] [Client thread/INFO] [OpenMods]: openmods.network.IdSyncManager.decodeIds(IdSyncManager.java:113): Received data store for key rpc_targets, packet size = 107
[14:52:48] [Client thread/INFO] [FML]: [Client thread] Client side modded connection established
[14:52:49] [Client thread/INFO] [journeymap]: Requesting World ID
[14:52:50] [Client thread/INFO] [ThermalExpansion]: Receiving Server Configuration...
[14:52:50] [Client thread/INFO] [THAUMCRAFT]: Client received server config settings.
[14:52:50] [Client thread/INFO] [THAUMCRAFT]: CHEAT_SHEET[true], WARDED_STONE[true], MIRRORS[true], HARD_NODES[true], WUSS_MODE[false], RESEARCH_DIFFICULTY[0], ASPECT_TOTAL_CAP[64
[14:52:50] [Client thread/INFO] [Mantle-STDERR]: [minetweaker.runtime.MTTweaker]: Loading scripts
[14:52:50] [Client thread/INFO] [Mantle-STDERR]: [minetweaker.runtime.MTTweaker]: MineTweaker: Loading intermod
[14:52:50] [Client thread/INFO] [Mantle-STDERR]: [minetweaker.runtime.MTTweaker]: MineTweaker: Loading binniesmods.zs
[14:52:50] [Client thread/INFO] [Mantle-STDERR]: [minetweaker.runtime.MTTweaker]: MineTweaker: Loading chiselChisel.zs
[14:52:50] [Client thread/INFO] [Mantle-STDERR]: [minetweaker.runtime.MTTweaker]: MineTweaker: Loading voidstonePatch.zs
[14:52:50] [Client thread/INFO] [Waila]: Received server authentication msg. Remote sync will be activated
[14:52:50] [Client thread/INFO] [NEIAddons]: World changed, resetting
[14:52:50] [Client thread/INFO] [NEIAddons]: Available server commands: SetForestryWorktableRecipe
[14:52:50] [Client thread/INFO] [journeymap]: Got the World ID from server: 42f3d192-3931-4246-a920-2d8a0d6dbb50
[14:52:50] [Client thread/INFO] [journeymap]: World UID is set to: 42f3d192-3931-4246-a920-2d8a0d6dbb50
[14:52:50] [Client thread/INFO] [journeymap]: Loaded 2 waypoints from G:\FTB\direwolf20_17\minecraft\journeymap\data\mp\CF_42f3d192~3931~4246~a920~2d8a0d6dbb50\waypoints
[14:52:51] [Client thread/INFO] [journeymap]: Loaded 2 waypoints from G:\FTB\direwolf20_17\minecraft\journeymap\data\mp\CF_42f3d192~3931~4246~a920~2d8a0d6dbb50\waypoints
[14:52:51] [Client thread/INFO] [journeymap]: Mapping started in G:\FTB\direwolf20_17\minecraft\journeymap\data\mp\CF_42f3d192~3931~4246~a920~2d8a0d6dbb50\DIM0. Memory: 2015MB total, 1127MB free
[14:53:08] [Client thread/INFO] [inventorytweaks]: net.minecraft.client.gui.GuiChat
[14:53:10] [Netty Client IO #12/ERROR] [FML]: NetworkDispatcher exception
io.netty.handler.timeout.ReadTimeoutException
[14:53:10] [Netty Client IO #12/INFO] [THAUMCRAFT]: Restoring client configs.
[14:53:10] [Netty Client IO #12/INFO] [OpenMods]: openmods.network.IdSyncManager.onDisconnect(IdSyncManager.java:124): Disconnected, restoring local data
[14:53:10] [Client thread/INFO] [journeymap]: Mapping halted in G:\FTB\direwolf20_17\minecraft\journeymap\data\mp\CF_42f3d192~3931~4246~a920~2d8a0d6dbb50\DIM0
[14:53:10] [Client thread/INFO] [FML]: Applying holder lookups
[14:53:10] [Client thread/WARN] [FML]: Unable to lookup chisel:cobblestoneWall for public static com.cricketcraft.chisel.block.BlockMarbleWall com.cricketcraft.chisel.init.ChiselBlocks.cobblestoneWall. Is there something wrong with the registry?
[14:53:10] [Client thread/INFO] [FML]: Holder lookups applied

Ive been having random disconnects when going from dimension to dimension so ive looked at the logs and compared them.. journeymap seems to be the culprit so you might want to use mapwriter instead of journeymap to reduce the "fatal exception: connection terminated" count

Never put a hive on a hive. It will bug out the top one to be unbreakable...

on a random note, just so it's mentioned, in a worst-case scenario where we change pack, resonant rise was dismissed as it would require users to manually select mods there's a tool specifically for servers to hand out a link that allows auto-selection and auto-install https://forums.atlauncher.com/thread-8693.html details are here, I found it interesting to read at least

server is getting horrible lag atm for all players.. wasn't there last night.. :/

can we try opis now?

Crippling lag confirmed.

Opis looks like a good bet. Another complementary tool is WarmRoast by sk89q

The lag is pretty unbearable, aye. Also interested in a lag finder and killer thing o3o

Good news!

Nand and I have made a discovery. The lag almost completely goes away so long as there is at least one person in the nether!

Makes zero sense! Kind of inconvenient for that one person! But it's better than nothing!

#stillneedsfixing

That's what happened last time we ended up with a rollback. How do the spawns in the nether look? if it's barren thats an indication we might need to check all gates for witherparties

we could delete the nether and see what happens?

if it is the nether causing it, could it be possible to do a nether wipe once a fortnight?

Good news!

Nand and I have made a discovery. The lag almost completely goes away so long as there is at least one person in the nether!

Makes zero sense! Kind of inconvenient for that one person! But it's better than nothing!

#stillneedsfixing

Discharge

I found this out yesterday too, I was the only one on the server atm and wile in nether, I had 0 lag, totally gone.. but when I came back to overworld it came back too..

maybe, just maybe, if no one is in nether it starts loading all those wither skelly chunks (for ones that don't know there was odd and uncontrollable spawning of 1000s of wither skeletons in some chunks..), but if 1 person goes in, it starts loading only the current chunk? just an assumption..

btw I checked mine last time and it seemed fine and wither free..

I logged in this (Saturday) morning.. nobody was online except me. Lag was moderate in the overworld, but I was randomly disconnected several times for no apparent reason.

I tried going to the nether but contrary to what Alex and Nand discovered.. It didn't seem to be any better there and I was randomly disconnected once while in the nether.

Saw and killed 1 whither skelly.. no parties, mobs moving very slowly in nether.

I stopped logging in because the pattern seems to be the same as last times. Lag will get worse and worse over time, just lagging badly one day, causing occasional disconnects the day after and being plain unplayable tomorrow

I was getting random disconnects/crashes too..
what ever we do from now on, we have to add opis or similar tools to fight the source of lag.. so that what Chista said doesn't happen again.. otherwise we would have a perpetual pattern that will stop us from playing
having either rerolls or resets etc doesn't fix the problem, it's a temporary solution that fails in the long run

I've reset the Nether.