Troublesome Items on Public Servers

  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord

Seanbeag

New Member
Jul 29, 2019
106
0
0
I thought I'd start a thread for people to list items they consider to be bad for a public server at the moment. The two I've had to ban are the laser and descriptive book. The laser can cause massive lag if used irresponsably and the descriptive book, well that's pretty obvious. I've also noticed the gravity gun appears to cause lag issues. IC2 machines seem to have a bug that spams the server too but I believe that's been addressed in the next update.

With the bukkit plugins becoming available and forge essentials coming along I think it would be good for us to discuss potential problems that we can address on servers.
 
Get the newest build of IC2 from here: http://141.28.27.36:8080/job/IC2_lf/?

That should fix the console spam. Personally, I would disable HTTP for ComputerCraft. Instead, just have a community folder be accessible by Dropbox. Then you can have people send you the programs, and if they seem harmless, put them on all computers. Also ban nukes, not the reactors though. The reason for both of these should be obvious, if not just look at the ending for Season 3 of ForgeCraft from Direwolf20. They murdered the server.
 
You might want to make clear what Mod pack.
here is what we have banned in mindcrack v7

Wand of Excavation
Wand of Equal Trade
Quarries
Fillers
Minning laser
World Anchors
Chunk Loaders
and the placing of any explosive
 
For our MindCrack we have dissabled ComputerCraft, ChickenChunks, PortalGun, OmniTools and Rainmaker. Some minor stuff like coins have also been dissable due to that theyre useless etc.

The 4 mods basicly due that they are bugged and the rainmaker due to well ... the name say it all. As for IC2 explosives, those can be toggled in the IC2 configs themselfe to be "harmless".
 
Get the newest build of IC2 from here: http://141.28.27.36:8080/job/IC2_lf/?

That should fix the console spam. Personally, I would disable HTTP for ComputerCraft. Instead, just have a community folder be accessible by Dropbox. Then you can have people send you the programs, and if they seem harmless, put them on all computers. Also ban nukes, not the reactors though. The reason for both of these should be obvious, if not just look at the ending for Season 3 of ForgeCraft from Direwolf20. They murdered the server.

Is that server addition or is it required client side too?

You might want to make clear what Mod pack.
here is what we have banned in mindcrack v7

Wand of Excavation
Wand of Equal Trade
Quarries
Fillers
Minning laser
World Anchors
Chunk Loaders
and the placing of any explosive

Actually I didn't state a specific modpack because I thought the thread might be useful for people using all modpacks.

For our MindCrack we have dissabled ComputerCraft, ChickenChunks, PortalGun, OmniTools and Rainmaker. Some minor stuff like coins have also been dissable due to that theyre useless etc.

The 4 mods basicly due that they are bugged and the rainmaker due to well ... the name say it all. As for IC2 explosives, those can be toggled in the IC2 configs themselfe to be "harmless".

Yes the IC2 config is great.
 
Upgrading to a newer IC2 will require doing it server side and client side. Not hard really, just delete the old IC2 jar, and replace it.
 
I am still seeing some warnings with build #184, even though that one is supposed to fix it?

What build are you using?

Example:
Code:
2013-01-21 17:05:44 [WARNING] [IC2] EnergyNet.emitEnergyFrom: ic2.core.block.wiring.TileEntityElectricBatBox@66ea846 is not added to the enet
2013-01-21 17:06:44 [WARNING] [IC2] EnergyNet.emitEnergyFrom: ic2.core.block.wiring.TileEntityElectricBatBox@4aac65a is not added to the enet
2013-01-21 17:07:44 [WARNING] [IC2] EnergyNet.emitEnergyFrom: ic2.core.block.wiring.TileEntityElectricBatBox@1d170a81 is not added to the enet
2013-01-21 17:08:44 [WARNING] [IC2] EnergyNet.emitEnergyFrom: ic2.core.block.wiring.TileEntityElectricBatBox@24c10e95 is not added to the enet
 
Use Build 198, there is no reason not too. It fixes some bugs, even if you didn't notice them. Also, I don't recall seeing an IC2 ENET spam in the console when I had an MFSU and a couple transformers feeding my macerators.
 
Well, I didn't want my users to update for no reason, since my test with the latest build did no show a difference.

I did stumble over a work around though. I am doing periodic save-off/save-all/save-on to save the world and noticed that the messages stopped during that time. So I switched it around to save-on/save-off/save-all and it is looking much better. This sequence is run every 5 minutes, so the loss in case of crash is small. On top of it, this may be good for performance because disk isn't written continuously. Anyways, just wanting to give an update, in case someone else is struggling with this.