Axle

You could try added Reinforced Doors to the blacklist for World Guard. Though are the players on your server using WG as the default grief protection? or is it just used by admins to protect server buildings.

I have never once seen this plugin crash the server... what version of Tekkit are you running/can you provide an error log?

Yep, one of the easiest ways to remove all world anchors, and even prevent them it to install Tekkitcustomizer and place World Anchors in the World Ban section of the configuration and run the server. The plugin will remove all of the anchors (Along with everything else you place in the ban list). I warn you though, before starting your server, have a look at the configuration as it comes with quite a few items preconfigured which may need to be removed before you start your server.

That is pretty minimal for a tekkit server... not saying it can't run it, but it also depends on how many chunks are forced to be loaded, along with the number of plugins installed and how much is running within those loaded chunks.

If it says 'Cannot bind port' Go into server properties and delete both the IP and the Port in the file... Though usually that error only happens when you try to load a server twice.

A lot of ISP's have issues with bandwidth, yes it is easy to configure... just not worth it if you don't have the bandwidth to support a server, or have an isp like mine that has a DHCP that changes my IP weekly... makes everything a hassle.

Well... PEX if very picky I find... what may be the cause is the group name is identical to the ladder name. Try changing the group name to Default or something other than player.

A way you could do this... and bare with me this is kind of 'Outside the box' thinking... With Tekkitcustomizer, assign all of the tools to usage ban... then under permissions, assign the exempt permission for each of the tools you want to a work. Example: Farmer: default: false inheritance: - Default worlds: world: permissions: - tekkitcustomizer.283.*.* - tekkitcustomizer.284.*.* - tekkitcustomizer.285.*.* world_nether: - tekkitcustomizer.286.*.* - tekkitcustomizer.294.*.* options: rank: '899' prefix: '[Farmer]&f ' In this example, the person in this group is able to use the gold sword, shovel and pick in the normal world and not the nether, and only allowed to use the axe and the hoe while in the nether (Yes I know the tools are terrible choices for each, but I did a very rough example with the first thing I seen)

Thats easy but long winded... put everything you want disabled under Crafting Ban and Ownership Ban. Then using your permissions add tekkitcustomizer.[itemid].* under the rank you want to be able to craft and use the item. So basically, you need to set up a ban for each item, then a permission to allow the item for a rank... that is a lot of work...

From just a brief view at the error, the server doesn't have enough memory (RAM) to support tekkit... how much RAM do you have on this server?

Few ways to do this. Using Tekkitcustomizer, you can have the server wipe out any Anchors, Tethers, carts placed and it won't allow new ones placed. You can remove the dimensional anchor mod completely without affecting the server (Yes I know the item is called Tether, the mod is actually called Dimensional Anchor) Under the railcraft config, you can change cube.world.anchor to false. Or if you feel really adventurous, you can change all of the mentioned items to have an ID of 0, thus causing a conflict with AIR... but it wont cause any issues on the server, besides not being able to spawn the mentioned items.

You could try tekkitcustomizer (http://dev.bukkit.org/server-mods/tekkitcustomizer/) It can at least disable the use of items defined within it. A good example would be the Swift Wolf, by placing it under Usage Ban, it allows players to fly with it, but can not use it for it's push back or lightning abilities.

What you are asking is pretty ludicrous and probably the only way you will succeed in this is if you can literally configure a server from the ground up and offer to be a server support position to whoever wants to use the server design.

PEX is good, bit script I find but I still use it. groups: Default: default: true permissions: - bukkit.command.save.perform options: rank: '900' prefix: '[Default] ' Anyway, that is what the configuration would look like for what was requested.