PreciousStones 7.0.8b works fine for me, but 7.1.1 protection stones don't work and I get a lot of error messages about "Could not pass event PLAYER_MOVE to PreciousStones". See below:

2012-01-03 07:15:40 [INFO] Starting minecraft server version 1.0.1
...
2012-01-03 07:15:40 [INFO] This server is running Craftbukkit version git-Bukkit-1.0.1-R1-13-ga0124aa-b1611jnks (MC: 1.0.1) (Implementing API version 1.0.1-R2-SNAPSHOT)
...
2012-01-03 07:15:48 [INFO] [PreciousStones] Version 7.1.1 loaded
2012-01-03 07:15:48 [INFO] [PreciousStones] SQLite Connection successful
2012-01-03 07:15:48 [INFO] PreciousStones fields: 11
2012-01-03 07:15:48 [INFO] [PreciousStones] Payment method found.
...
2012-01-03 07:16:52 [SEVERE] Could not pass event PLAYER_MOVE to PreciousStones
java.lang.NullPointerException
at net.sacredlabyrinth.Phaed.PreciousStones.managers.PermissionsManager.has(PermissionsManager.java:43)
at net.sacredlabyrinth.Phaed.PreciousStones.listeners.PSPlayerListener.handlePlayerMove(PSPlayerListener.java:452)
at net.sacredlabyrinth.Phaed.PreciousStones.listeners.PSPlayerListener.onPlayerMove(PSPlayerListener.java:397)
at org.bukkit.plugin.java.JavaPluginLoader$7.execute(JavaPluginLoader.java:307)
at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:58)
at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:339)
at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:182)
at org.getspout.spout.SpoutNetServerHandler.a(SpoutNetServerHandler.java:679)
at net.minecraft.server.Packet10Flying.a(SourceFile:126)
at net.minecraft.server.NetworkManager.b(NetworkManager.java:226)
at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:93)
at org.getspout.spout.SpoutNetServerHandler.a(SpoutNetServerHandler.java:550)
at net.minecraft.server.NetworkListenThread.a(SourceFile:108)
at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:527)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:425)
at net.minecraft.server.ThreadServerApplication.run(SourceFile:457)

Same as Issue #132, fix added, releasing soon.