Minecraft Forums

It works with 158 from my testing. However I don't have all the mods you do, just ForgePerms, MyTown, and the bridge. But try and see if 156 works.

I can also confirm that it works with 158. I'm thinking there's a conflict somewhere with a mod or plugin. I would recommend setting up a test server with no extra mods or plugins and seeing if it works. If so then start adding things one by one until you find the offending mod or plugin.

not a fan of OpenJDK. I would remove it and replace it with Java JDK.
heres the simple way to install java:

http://m.webupd8.org/2012/01/install-oracle-java-jdk-7-in-ubuntu-via.html?m=1

Most likely a java 6 issue

Paktosan: You should always be using Java 7. As TrenTech said, its probably a Java 6 issue and not directly related to OpenJDK

floh22: I can look into it

First thing that come to mind is that permissions are not setup correctly. Be sure your default group has the nodes needed to run the commands. Also be sure they are not already in a town somehow.

Hmm. Make sure they are running the command correctly. Also, if you have Essentials, it can cause problems when using /t. Ask them to try /town and /mytown as alternatives. Also, what error do they get when they run the command?

Hmm, very odd. ForgePermsCBBridge has some logging that can be enabled temporarily, it should show the perm nodes being requested when the commands are run. That may help determine where the issue is.

Quote from floh22

no error. nothing. essentials /t is been changed to /bukkit in bukkit.yml so that works fine. even /mytown doesnt work. its very strange

What message do the players receive when they attempt to create a town?

Quote from floh22

just the regular: 1 chunk requested out of which 1 was able to be claimed and 0 owned.oh also, which logging level should i set it to and where does it log to?

Wait! I thought you said they couldn't create towns. This is the message you receive when attempting to claim plots, in which case a town has already been created.

As for logging I'll quote a previous post

You can enable logging for ForgePermsCBBridge in plugins/ForgePermsCBBridge/config.yml and setting loggingLevel to FINEST (case matters) that should start logging everything. I recommend not leaving it on for long as it will log all perm nodes being requested, but it should help to find out what may be causing the issue.

I believe it just logs to the console

Sounds similar to the problem above. Just to rule out any conflicts recommend removing MyTownEcon if you guys have it, I know Turnip does, and see if the problem still persists.

floh22, I know you fixed it but, the bridge logging will output what perm nodes are being requested, who requested them, and whether the person has the node (true/false). I use it to make sure MyTown is actually checking the nodes and to make sure things are getting returned correctly.

TurnipTheBeet, check your config (especially the database options) to make sure everything is correct. Either that or the database is corrupt. I am not sure what could be the issue. What mods and plugins are you using? Perhaps something is interfering with MyTown.

Updated ForgePermsCBBridge to 1.5.1.15 to fix bPermissions not returning prefix and suffix. Also, we have a website! http://mytown.mineyourmind.net

Quote from TurnipTheBeet

ill take a go at removing mytownecon to test if im still getting the problem. and legobear i havent messed with the config for mytown because it already works exactly how i like it with the default settings. most likely its what you said about the database, but im wondering if it could be caused by me moving myself between towns when i need to set a permission or claim for a town (i find it easier than using the admin commands). ill let you guys know what i find.

Actually Lego is right about the config. If you've been updating from old versions, some config options have changed and could cause problems.

TurnipTheBeet, due to a bug I discovered in Forge, I had to do a workaround so it would read and write the configs correctly. I had a red notice on the post for a while, but removed it since I figured everyone had seen it and been updated just fine. I don't remember which version I introduced the change. The workaround just forces the config options to be lowercase instead of case sensitive, before there would be duplicate entries and the config would load one, but save to the other entry thus causing problems with some things. Most should have been fine, especially database, but its always good to check to make sure.