Bukkit

@UrWrstThnMe

I assume Retherz_ Is busy with school or something of that nature. If you haven't seen my updated post, give 1.1.2 a try if you don't have factions. It still works fine for me!

@Retherz_

I'll have to play with it more when I get home, but at first install 1.1.4 doesn't work. I haven't tried ANYTHING though, like deleting/playing with the config file. It may be as simple as the default dig level is too high :)

I'll check when I get home though! But if you have free time between now and then, you should too ;-)

EDIT: Tried deleting the config file to no success.

EDIT2: Reverted back to 1.1.2 for now :) (Last functional version for anyone who DOESN'T use factions!)

@Retherz_

Should I revert back to 1.1.2? or will 1.1.4 be forthcoming this week some time? :) No rush in the least, just wondering how lazy I should be :)

Btw, in the mean time, am I allowed to have MULTIPLE items that work? In my case, I'm thinking all diamond tools. This will indirectly solve my glitch as it will allow me to include the shovel I use for gravel that causes the glitch :p

@Retherz_

You're REALLY going to hate me! :p

Tested this: http://dev.bukkit.org/bukkit-plugins/bedrockmine/files/13-bedrock-mine-1-1-3/

Doesn't seem to work at all for me. Either with the default config or with this:

Min-Break-Y: 2 Item: 278 Time: 1 Drop-Bedrock: true Factions: false

The only value above I changed from the default config file is changing the item name to a number.

I'll test out more tomorrow :p Sorry I'm useless!

@FlOppythp

Do you require multiple people to be able to create quests? I'm not certain how the bedrock would be tied to this.

I ask because you have the ability to give some users the permission to use Bedrockmine while not granting it to others?

I'm highly curious what you have in mind for the quest?! :)

Perhaps very similar functionality could be achieved with COMPLETELY different programming on both your and Merciless' behalf would be the following: - Create "/minebedrock user" as a new command - Create "bedrock.command" as a new permission. This one granting/removing the users ability to access /minebedrock on the server, while still allowing him to actually mine bedrock if the OTHER permission is enabled. - PERHAPS alter /minebedrock and /minebedrock user to accept true/false or enabled/disabled as well as it's current toggling between? That way for certain you could do "/minebedrock Gergith enable" instead of risking disabling someone you want to enable?

That's the fix on Merciless' end. (Please don't hate me Merciless ;-))

This way people on FlOppythp's server could then use a simple command block to achieve this same goal. Either to check the player somehow, or to Enable minebedrock for the player at the beginning of the quest, and disable it at the end? :) Using the newly created command this way "/minebedrock @p" perhaps? :)

JUST a suggestion :D but that makes a bit more sense to me.

@Retherz_

i know I probably suck to hear from all the time ;-) But if you ever need a beta tester; I'm clearly up for the task :D