Press add mod, and browse to the jar you just downloaded. Connect to the server as usual.
By the way, following further analysis, the sheer amounts of lag were being caused by chunkloaders. All chunkloaders have been removed, please use them sparingly!
It also seems the entity count is extremely high (spawners?).
Known bugs (to be updated as we discover them):
- Chargepads mod not working (requires update)
As all of you must be aware, the Feed The Beast server has been down for a few days. Unfortunately, a bug in Industrial Craft 2 is preventing the server from running in a stable state. A piece of "debug code" left in by a developer causes certain block placements to spit out a message on every tick. Since the tick rate is around 20 tick / sec this means that there is a lot of IOWait whilst the server writes to disk and console causing high disk IOPS. For the same/some other reason the JVM is maxing out the CPU and RAM then crashing.
The options are:
When I find a newer build of IC2, manually patch up to the latest version. Clients will be required to manually do the same.
Wait for an FTB update to fix this.
Attempt to purge all IC2 blocks from the map.
Use a new world until this is fixed.
If anyone else out there knows of any alternatives, or the location of a dev build of IC2, please let me know.
The Feed The Beast server has been re-instated, however I'm somewhat at a loss determining what could be causing the intermittent excessive resource consumption (perhaps too many loaded ages?). The issue is game specific (i.e. is a problem within the code running in the JVM itself), so if anyone has any ideas which may help, since those of you with a deeper understanding of the architecture are more likely to get to the crux of the issue, then please reply to this thread with your suggestions.
We are seeing extremely high resource usage from the Feed The Beast server and are currently unable to identify the root cause. As such, the service has been temporarily suspended pending further investigation. This decision has not been taken lightly as I know many of you use this on a regular basis. Our aggregate resource usage has spiked significantly today, and the FTB VM is responsible for excessive consumption of CPU time affecting the performance of other Pipe3 services. As soon as the cause has been identified and resolved, the service will be re-instated.
