Solved [Super Spleef] Starting Server Problem

A while back, I set up my Spleef arena, spawn points, floor, etc. But when I decided to restart the server, it revealed an error message, as shown below.

Code:

2013-06-10 16:19:33 [SEVERE] Error occurred while enabling SuperSpleef vB 0.1.7 (Is it up to date?)
java.lang.NullPointerException
    at org.mcsg.double0negative.spleef.Game.loadFloor(Game.java:156)
    at org.mcsg.double0negative.spleef.Game.loadGame(Game.java:87)
    at org.mcsg.double0negative.spleef.Game.setup(Game.java:70)
    at org.mcsg.double0negative.spleef.Game.<init>(Game.java:65)
    at org.mcsg.double0negative.spleef.GameManager.LoadGames(GameManager.java:62)
    at org.mcsg.double0negative.spleef.GameManager.setup(GameManager.java:31)
    at org.mcsg.double0negative.spleef.Spleef.onEnable(Spleef.java:34)
    at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:217)
    at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:457)
    at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:381)
    at org.bukkit.craftbukkit.v1_5_R3.CraftServer.loadPlugin(CraftServer.java:282)
    at org.bukkit.craftbukkit.v1_5_R3.CraftServer.enablePlugins(CraftServer.java:264)
    at net.minecraft.server.v1_5_R3.MinecraftServer.j(MinecraftServer.java:304)
    at net.minecraft.server.v1_5_R3.MinecraftServer.e(MinecraftServer.java:283)
    at net.minecraft.server.v1_5_R3.MinecraftServer.a(MinecraftServer.java:243)
    at net.minecraft.server.v1_5_R3.DedicatedServer.init(DedicatedServer.java:151)
    at net.minecraft.server.v1_5_R3.MinecraftServer.run(MinecraftServer.java:382)
    at net.minecraft.server.v1_5_R3.ThreadServerApplication.run(SourceFile:573)

Thanks,
HerbPlaysMinecraft

 

It looks like another plugin may be conflicting this problem, have you tried restarting your server again? If these don't work i would recommend you go here and introduce your problem.

 

Any way to check what plugins are afflicting each other? And as it says in the first post, I already restarted.

And I already introduced my problem.

EDIT: Many people are having the same problem.

 

If alot of people are having this probelm, Then this will have to be a fix on the plugin authors side.

 

Okay.