Core Protect problems with pipe LWC

[xjjon88]

I have been using coreprotect but it cannot roll back BC pipes, so I was thinking to add the BC pipes to LWC. Now the problem is that when I look up the IDs of the the BC pipes,

http://minecraftbuildcraft.wikia.com/wiki/IDs

I am not sure which ID to use, the block ID or the pipe ID. Because core protect registers the block id (166), which causes it to give errors.

Also, would anyone recommend core protect, or hawkeye? For a tekkit server.

Thanks for your help guys.

[Phuriousgeorge]

HawkEye is no longer being supported it seems and neither is Guardian. Your best bet would be to go to CoreProtect or LogBlock, but I've had issues with LogBlock and pipes as well.

As to your other question with LWC. The BEST way and only way to be sure about item IDs is to log into Tekkit either multiplayer or singleplayer and look it up on your NEI.

[xjjon88]

Sorry, I wasn't clear enough in my post. the reason I ask is because in NEI the IDs are the "pipe ids" on the build craft wiki, but when core protect tries to roll them back, they become the block id (166) which can't be spawned or it will corrupt your .dat file for that player with it.The actually ids for each pipe to spawn them are 4051-4070.

I'm not sure if I have to protect the block ID or the pipe ID. When it's placed down, does the ID change?

[Phuriousgeorge]

Hmm, interresting question. I'll have to check what's logged in my database when I place one when I get home. You got me thinking...

[xjjon88]

Okay, please share your findings. I will be testing LWC with the various IDs now.

[xjjon88]

I just tested Core Protect and LWC.

Here are my results:

Test 1: Copper Cable (30184) when placed down, becomes block id (228)

Core Protect: Can be restored. LWC: Registers with ID 228

Test 2: Stone Transport Pipe (4308) when placed down, becomes block id (166).

Core Protect: Cannot be restored. LWC: Registers with ID 166

Now I still need to test with someone else to see if LWC actually protects the blocks from being broken, but for the time being, I need to figure a way to stop core protect from trying to restore pipes, since it leaves the ghost blocks and makes errors.

[Phuriousgeorge]

Thanks for the results. I found the same. As to stopping the rollback, I know LogBlock has a blacklist for not rolling back specific blocks, but I haven't seen anything similar on CoreProtect. Maybe the author would be kind enough to add a feature.

[Skuli]

Thanks for the results. I found the same. As to stopping the rollback, I know LogBlock has a blacklist for not rolling back specific blocks, but I haven't seen anything similar on CoreProtect. Maybe the author would be kind enough to add a feature.

Core protect has an exclude parameter in the rollback itself.

[Phuriousgeorge]

Core protect has an exclude parameter in the rollback itself.

Very true, it would just be much easier to have a blacklist field so I don't have to worry aobut staff including the argument each and every time, especially since we don't have to do rollbacks often.

[Skuli]

Very true, it would just be much easier to have a blacklist field so I don't have to worry aobut staff including the argument each and every time, especially since we don't have to do rollbacks often.

When I was using core protect I remapped the /co command to "/co exclude 166" with commandhelper.

[Phuriousgeorge]

Ah, not a bad idea. Hadn't thought about that. I've used that plugin in the past, guess I need to pick it up again. Thanks for the tip!