ZombieTwiglet

Good work sct, will test it when I get home. Thanks.

Conductive pipes do work, but I'm pretty sure you need to start with a full 4 stacks of each ingredient to get a farm going.

No, that's exactly what you are asking for. You just worded it differently.

First off, check for user error. I thought I was having the exact same issue with PEX. Turns out I was assigning the permissions to "Members" not the correct group "Member", also PEX doesn't seem to update immediately sometimes on my tekkit server so give it a nudge with /pex reload or whatever the command is for PermissionsBukkit. I also half remember seeing something saying PermissionsBukkit didn't play will with Tekkit, I may however be completely wrong on this so have a search on that.

You need to forward the port to the server most likely. http://portforward.com/

Is the server using Towny or some other king of area protection? If it is you'll need to add the fake users to the ops list or give them the needed build/destroy perms or it'll do nothing. There are multiple threads on how to do this.

http://www.lmgtfy.com/?q=lwc+bukkit

This isn't a Tekkit problem, it's a Bukkit problem (I'm guessing you're missing Vault or Register), and this isn't the bug board.

There is a sticky in the BUG board; http://forums.technicpack.net/index.php/topic,2834.0.html Protip, it's called bug board because it has bug reports, and solutions to bugs.

Why not a giant cock made of luminators? Or you could use your imagination...

Well what do you know? They have an entire wiki full of information, including a first time setup walk through. https://github.com/PEXPlugins/PermissionsEx/wiki

Re: Next Go-Around, please configure the pack better for balance and gameplay While there are some major balance problems with the combination of mods in the Technic/Tekkit pack, just getting them all to work together is a job and a half in itself without having to tweak the settings to improve balance of mods that were not made to work together (in a balance sense). Rather than just say how broken you think it is why not get involved and either share your config tweaks so the community can benefit or offer your services to the team? These guys put this together and spend a whole load of money on bandwidth (1TB a day was the latest I've heard) and don't ask for a penny in return while making it as simple as uploading the pack to your server and making a launcher that runs with a few clicks. Have you tried to get this number of mods all working together then explaining to your users just how to install all the mods? It's not fun.

Ok, so after a lot of searching I have found LWC can do what I'm after. I'm just having a few issues with it not protecting blocks automatically and only working on select blocks, i've got the block IDs from NEI in game but either they are incorrect or LWC doesn't like them... So far it will protect with the command /cprivate then clicking on: Standard blocks (doors, chests, default rails etc...) Detector Rail But doesn't work on anything else. Anyone have any experience with LWC, or even getting LWC to protect rails/pipes/cables automatically on placement? core: locale: en flushInterval: 10 cacheSize: 10000 precache: -1 showNotices: true showMyNotices: false opIsLWCAdmin: true disableHistory: false townyBorders: false groupPrefix: group. updater: branch: STABLE method: MANUAL optional: onlyProtectWhenOwnerIsOnline: false onlyProtectWhenOwnerIsOffline: false exemptBlocks: [] optOut: true database: adapter: mysql path: plugins/LWC/lwc.db host: localhost database: tekkit_lwc username: <snip> password: <snip> prefix: lwc_ protections: denyRedstone: true autoRegister: true ignoreBlockDestruction: true ignoreLeftClick: false ignoreRightClick: false ignoreExplosions: true quiet: false blocks: chest: enabled: true autoRegister: private furnace: enabled: true autoRegister: private dispenser: enabled: true autoRegister: private sign: enabled: true autoRegister: private wooden_door: enabled: true autoRegister: private iron_door: enabled: true autoRegister: private trap_door: enabled: true autoRegister: private # Rails '66': enabled: true autoRegister: private '27': enabled: true autoRegister: private '28': enabled: true autoRegister: private '210': enabled: true autoRegister: private '7261': enabled: true autoRegister: private '7266': enabled: true autoRegister: private '7268': enabled: true autoRegister: private '7269': enabled: true autoRegister: private '7271': enabled: true autoRegister: private '7274': enabled: true autoRegister: private '7278': enabled: true autoRegister: private '7281': enabled: true autoRegister: private '7282': enabled: true autoRegister: private '7284': enabled: true autoRegister: private '7287': enabled: true autoRegister: private '7290': enabled: true autoRegister: private '7292': enabled: true autoRegister: private '7298': enabled: true autoRegister: private '7300': enabled: true autoRegister: private '7301': enabled: true autoRegister: private '7313': enabled: true autoRegister: private '7316': enabled: true autoRegister: private '7319': enabled: true autoRegister: private '7321': enabled: true autoRegister: private # Pipes '4298': enabled: true autoRegister: private '4299': enabled: true autoRegister: private '4300': enabled: true autoRegister: private '4301': enabled: true autoRegister: private '4302': enabled: true autoRegister: private '4303': enabled: true autoRegister: private '4304': enabled: true autoRegister: private '4305': enabled: true autoRegister: private '4306': enabled: true autoRegister: private '4307': enabled: true autoRegister: private '4308': enabled: true autoRegister: private '4309': enabled: true autoRegister: private '4310': enabled: true autoRegister: private '4311': enabled: true autoRegister: private '4312': enabled: true autoRegister: private '4313': enabled: true autoRegister: private '4314': enabled: true autoRegister: private '4315': enabled: true autoRegister: private '4316': enabled: true autoRegister: private '4317': enabled: true autoRegister: private '4320': enabled: true autoRegister: private '4322': enabled: true autoRegister: private '4324': enabled: true autoRegister: private '30184': enabled: true autoRegister: private # Cables '31084:1': enabled: true autoRegister: private '31084:2': enabled: true autoRegister: private '31084:3': enabled: true autoRegister: private '31084:4': enabled: true autoRegister: private '31084:5': enabled: true autoRegister: private '31084:6': enabled: true autoRegister: private '31084:7': enabled: true autoRegister: private '31084:8': enabled: true autoRegister: private '31084:9': enabled: true autoRegister: private '31084:10': enabled: true autoRegister: private '31084:11': enabled: true autoRegister: private modes: droptransfer: enabled: true persist: enabled: true

I'm looking for a plugin that works in the same way as the Essentials Protect plugin works for rails/signs. Basically it protects rails and signs and the blocks supporting them when placed, allowing only the owner/ops to remove them. The only problem is that Essentials protect doesn't let me define which blocks are protected. I'm not looking for any area protection just a block protection one with the ability to add custom block id's to the protection so users just lay down (railcraft) rails, pipes, and cables without having to worry about people destroying them. It has to be compatible with bukkit it 1.1-R4 (the current Tekkit version obviously), my Google fu has failed me.

Set the following in you server.properties file # Allow flying allow-flight=true Also Google, Learn to use it.

In addition to Yuriy, If you are indeed forwarding the ports on your router correctly then make sure your computer (you only need to forward TCP) has a static IP and the ports are forwarded to that IP. If you have DHCP then each time you reboot you are (most likely) going to get a new IP. Changing your IP: XP Vista/7. Check http://portforward.com/ and track down your router. to make sure you're doing it correctly.

Also if you are changing ops.txt the server will need to restarted between edits.

Use a bukkit plugin to protect the area, Residence, Towny etc... Or a plugin like LWC to lock doors, a combination of both?

You've given us no useful information on the software used to control the server or if you can even run custom server jars, depending on the software they are running will determine how you would go about getting Tekkit to work. The best bet is to contact them, this isn't asking for help to get a bukkit plugin working, this is a request to run a completely different server wrapper working. If they say they won't help, or that they wont let you run a custom wrapper, then go find another host, they are a dime a dozen and a fair number will no doubt give you the help you need just to get your custom. If you can't leave or don't want to leave your going to need to provide a lot more details about the setup of the server you have, if your not 100% sure of the software controlling it you will at least know the file structure of the server folder you can ftp into eg: /craftbukkit.jar /plugins/plugin.jar /ops.txt etc... If they are using Multicraft as their hosting software try following my solution here: http://forums.technicpack.net/index.php/topic,4943.msg30843.html#msg30843

There are two types of copper and tin ores, if you smelt them directly you'll have two types of copper and tin ingots, if however you macerate them they will be turned into the same kind of copper/tin dust. So if you're sorting them you'll need to have both types of each ore in a pipe to sort them.

I was having issues with this the other day, how I eventually got it to work was this: Upload all the Tekkit files to the multicraft/servers/servername diretory Crete the jar folder in multicraft/servers/servername Move the "mods" and "config" directories to the multicraft/servers/servername/jar directory Move the "Tekkit.jar" file to the multicraft/servers/servername/jar directory In multicraft find the server, and click the "show advanced option" checkbox so it expands the options Make sure the "Look for JARs in" option is set to "Server JAR directory*" Then set the "JAR File" option to Tekkit.jar Start the server and open the console window Check it's loaded and generated the worlds and says "Done blah blah 23s" as it will not show as online in Multicraft (the green circle icon) for some reason Hop on the server and see if it's generated the custom blocks Rejoice (hopefully) Stop the server in Multicraft rename the jar from "Tekkit.jar" to "craftbukkit.jar" Change the "JAR file" option to craftbukkit.jar Start the server, Multicraft should now show it as online (the green circle) Reconnect and if all has gone well it should all be working This is what I did after hours of arsing about trying to get it working, YMMV. Debian 6 x64 Sun Java 7 Hope that helps.