Jump to content

Recommended Posts

Posted

Hi there,

I've managed to use WorldGuard to disable the Right-Click of the Philo Stone, but I need a way to stop people using the "C" ability open the Crafting UI. The reason for this is that with NoItem people can't craft things with the "nocraft" in a normal crafting table, but they can in the Project Table and Philo Stone Crafting UI.

Either that or a cure for the problem rather than treating the symtoms.

Cheers.

Posted

You could stop people from holding the philosophers stone? noitem.nohold.<item id>. Use this permission node for all items you want to disallow. This will allow them to make in the project table but won't let them hold it meaning that can't use or place it either.

Posted

That Philosopher's Stone solution is so simple! Feel dumb not having thought of it myself haha,thanks! They'll still be able to to use it in recipes but not hold it to use C, brilliant.

As for the Project Tables/Auto Tables, my permissions stop they using/holding/breaking, etc a banned item if they manage to craft it, but unfortunately my deployer blacklist won't work with Tekkit IDs, so they could still say, craft a nuke and put it into a deployer beside a redstone torch to detonate it.

EDIT: The Philo Stone idea didn't work, they can still switch to it and really quickly press C before it gets moved by NoItem.

Posted

You may also want to disable the holding of a Mercurial Eye! It does pretty the same thing as a Philosophers Stone. I'm not too sure how to fix the nuke problem! There might be away to globally remove it from the server somehow. I'll have a look round.

Posted

Its a bit more limited, but the disablecraft plugin works for me to block recipes from all methods of crafting.

DisableCraft seems to be a good one, but the examples are lacking. Could you give me an example of your Permissions file for multiple block disables (e.g. can you use commas to seperate them or do you need to have a massive list with each one in it's own node?). Can I just do - disablecraft.disable.126.-10,126.-11,237 or something different? I can't quite get it to work.

Posted

well, we are using an older version that does not support permissions based disabling, never got around to updating.

you can just use the config file in /plugins/disablecraft/

the format goes

- (block ID)::(data value, -1 for all data values)

If you wanted to block orange wool, but not any other wool, it would be

- 35::1

I really should update that plugin, sorry i cant help with the permission based disabling.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...