Blocking what the Redpower Deployer can deploy

[Gunre]

My brain has slightly melted after hours trying to research a solution for this, so I'm just going to post it here and see if anyone knows a fix.

I want to ban an machine type block. It doesnt matter what, but for this example lets say the EE Condenser.

I can turn off the condender in ee_props, use modifyworld to ban a player form crafting, having, or interacting with it. Fine, a player cant craft it themselves, and if theres one in the world they cant interact with it with right click.

BUT, a player could still put down an automatic crafting table, use it to craft the Condenser, pipe the output to a deployer, deploy the Condenser block, then put items in and get items out using pipes or other appropriate machines.

So, I don't want to ban the auto crafting table, and I don't want to ban the deployer. Is there any way to add permissions to what the deployer can do? Either with modifyworld or with another plugin?

The simple solution is to just ban the deployer or auto crafting table, and that is what I will do if I can't find a deployer-permissions based solution.

[Phuriousgeorge]

Since Deployers and Block Breakers act as a player (forcing us to OP [RedPower]), it may be possible to impose permissions similar to a player and use modifyworld to prohibit placement. Not sure.

I'd thought about that this morning on my way into work because I'm having issues with Block Breakers and cobble farms. I don't want to disable Block Breakers entirely, but need an alternative option to disable cobble farms. I'll have to try it out myself once I get home this evening, but just a thought.

[Gunre]

Blarg!

I finally found 2 solutions, and I feel stupid. I dont know how I missed this in the redpower2 config file, but there are options for blacklists for both the deployer and block breaker. Also, if you set fakeplayer login to 1, then PEX will finally be able to 'see' the [redpower] user and apply modifyworld permissions to it.

[Phuriousgeorge]

Oh dang, I might be wrong, but I think the option in the config is new >.<

Edit: I can't find any guide on the configuration of redpower. Anyone happen to know how to properly configure the blacklists?

[Gunre]

I just tested it and at least the block breaker blacklist takes a comma delimited list, e.g. "1,4"

[Notvis]

Has anyone had any luck making the deployer blacklist work? Im trying to block placement of a couple items which I cant seem to block, particularly the RM and DM blocks.

[Gunre]

In my test the blacklist worked fine for simple block ids, but I did not test an EE item like 128:1.

However, I am successfully blacklisting EE items through the deployer with modifyworld.

In the RP2 config file I set fakeplayer login=1.

I have [redpower] op'd.

I'm not clear if these are necessary to make it work, but In my permissionsEx config file I have:

superperms:

allow-ops: false

strict-mode: true

And in the permissions file I have:

users:

'[RedPower]':

group:

- rpfakeplayer

and:

groups:

rpfakeplayer:

default: false

permissions:

- -modifyworld.items.(craft|drop|have|pickup|place|use).(128:1|126:?*|129|137:3|169|190:7|194:1|4303:?*|4304:?*|4305:?*|27527:?*|27528:?*|27529:?*|27530:?*|27531:?*|27532:?*|27533:?*|27534:?*|27535:?*|27536:?*|27537:?*|27538:?*|27541:?*|27543:?*|27544:?*|27545:?*|27546:?*|27547:?*|27548:?*|27549:?*|27550:?*|27551:?|27552:?*|27553:?*|27555:?*|27556:?*|27558:?*|27559:?*|27560:?*|27561:?*|27563:?*|27564:?*|27565:?*|27566:?*|27567:?*|27568:?*|27569:?*|27570:?*|27571:?*|27572:?*|27573:?*|27574:?*|27575:?*|27576:?*|27577:?*|27578:?*|27579:?*|27580:?*|27581:?*|27582:?*|27583:?*|27584:?*|27588:?*|27589:?*|27590:?*|27591:?*|27593:?*|27594:?*)

- -modifyworld.blocks.(place|interact|destroy).(128:1|126:?*|129|137:3|169|190:7|194:1|4303:?*|4304:?*|4305:?*|27527:?*|27528:?*|27529:?*|27530:?*|27531:?*|27532:?*|27533:?*|27534:?*|27535:?*|27536:?*|27537:?*|27538:?*|27541:?*|27543:?*|27544:?*|27545:?*|27546:?*|27547:?*|27548:?*|27549:?*|27550:?*|27551:?|27552:?*|27553:?*|27555:?*|27556:?*|27558:?*|27559:?*|27560:?*|27561:?*|27563:?*|27564:?*|27565:?*|27566:?*|27567:?*|27568:?*|27569:?*|27570:?*|27571:?*|27572:?*|27573:?*|27574:?*|27575:?*|27576:?*|27577:?*|27578:?*|27579:?*|27580:?*|27581:?*|27582:?*|27583:?*|27584:?*|27588:?*|27589:?*|27590:?*|27591:?*|27593:?*|27594:?*)

- modifyworld.*

(That block id format requires 'use-material-names: false' in the modifyworld config)

[Nentify]

Even easier - In the latest version of RedPower, there's a configuration for what deployers can deploy. There's already a configuration for block breakers in the Tekkit version. I can't link you right now as their site seems to be down. But there's a link on http://mcportcentral.co.za/.

[Notvis]

Even easier - In the latest version of RedPower, there's a configuration for what deployers can deploy. There's already a configuration for block breakers in the Tekkit version. I can't link you right now as their site seems to be down. But there's a link on http://mcportcentral.co.za/.

This is actually what I was referring to in my above post. The blacklist doesn't seem to accept tekkit block IDs, only vanilla ones.

[Phuriousgeorge]

In my test the blacklist worked fine for simple block ids, but I did not test an EE item like 128:1.

However, I am successfully blacklisting EE items through the deployer with modifyworld.

Thanks, I'll have to try that out.