Cool!

But what is the name of the fake player, I want the machines to be possible in certain regions?

@danielboyz

The player's name is: Redstone-Bridge

@Lyneira

Thanks! :)

I noticed that the default permissions in the config.yml contain 'machinapump.all'. But that does not include 'machinapump.lava' and 'machinapump.nether-water', right?

@Antalor

Correct, you have to activate lava and nether-water explicitly since those radically change what's possible in the survival experience.

Disregard, permissions issue. My bad.

I can't seem to get this to work, any help? I tried adding the '*' permission to the list of perms in it's config file and it didn't work, nor did it work when i made the rank of Redstone-Bridge an op. I did everything as you said, positioned the repeater directly next to the lever and pointing at it etc. Still no prevail.

Oh, and I also tried giving it all the permissions such as 'modifyworld.*' as well in it's config file and yet it still failed. Am I missing something?

@Adubbz

The default config for the redstone bridge should be enough to let it activate factory machines and such, unless world protection plugins are active.

Using the * permission like in modifyworld.* won't do anything special unless a plugin actually registers a permission like that. Perhaps modifyworld.world (if your main world is called "world") would work for your world protection plugin though.

If that doesn't help, is there any message given to the Redstone bridge in the server console?

I would think that the '*' permission would give it ALL permissions (Well, at least it does in my permissions.yml file) Unless of course this doesn't support that.

Found the issue, seems lwc wasn't being nice,. Anyway, i would suggest you document that you cannot use '*' in the config file even if it works with your permissions plugin.

@Adubbz

Done, added a note about it in the config.yml file for the next release. :)

@Adubbz

How did you resolve your issue? It's throwing the same error for me.

It would be really nice if you could make a way to permanently turn on the relay, instead of it flipping off after a few seconds. It's really hard to keep big factories going when stuff is turning off all the time. Could this be a future update?

@Takaishi

At the moment the tick-based system isn't well suited to it because I repurpose normal minecraft blocks for it. I would like to do something more convenient with the release of the minecraft mod API when it becomes possible to add custom blocks.

It is possible to force an item relay to activate itself using this redstone setup:

I have been using Machinacraft in general for a good while now and everything worked fine. But I got some trouble on the server and had to "up" my security. I installed PEX for the permissions. And obviously I'm doing something wrong cause I can't get the redstone-bridge to work.I tried including the Redstone-Bridge user in my group, I tried giving Redstone-Bridge specific permissions, I tried adding permissions to the conf file. I never got an error, but never got the redstone bridge working ethier. All the rest works perfectly for myself and my users. What am I missing?

@Hahsyra

I've removed my permissions plugin (permissionsEx) and have a similar problem: Great mod, I've always had a bit of a problem running the RedstoneBridge, usually a ton of spout errors, however after removing spout, and updating to 1.3.1 RedstoneBridge partially works. All other modules work flawlessly however when attempting to activate remotely, I am only able to turn off devices, turning on does not cause an error in console, or server.log

@Fendelgast

MachinaRedstoneBridge's fake player does not really exist to permissions plugins except at the point where a permission for it is being checked, that's why you can only configure its permissions in the plugin's config.yml. Trying to add permissions for Redstone-Bridge through a permissions plugin won't have any effect.

If the RedstoneBridge can turn devices off but not on, then it has the needed MachinaCraft permissions, however area protection plugins or inventory protection plugins may be blocking it from turning a machine on. You will have to add the proper permission for WorldGuard/LWC/etc to MachinaRedstoneBridge's config.yml to make it able to activate machines with an inventory for example.

@Adubbz

So what exactly about LWC was blocking it, I am running into same problem, I can turn them off but not back on. Also what "modifyworld" perm does this use, since I can't use the * wildcard?

One question, in the config.yml is this node: Note: "Use of .* permissions as wildcards won't work unless the plugin in question registers a permission that ends with .*" so I can't use "Modifyworld.*", and my question is wich permisions of modifyworld do i need or is there an permision like "modifyworld.all".

mfg IpsumJ

@IpsumJ

I had same problem but it looks like it works fine now, these are the 2 LWC and Modify World perms I used, not sure if LWC one is needed though.

- modifyworld.blocks.interact
- lwc.protect