MMOB command not spawning creature when called from a plugin.
P-paj opened this issue ยท 8 comments
/mmob spawn raider x y z world 3 spawns 3 - properly spawns raiders when ran by me in game.
using it in console works to spawn them as well.
However when using a custom plugin to dispatch a console command using
Bukkit.getServer().dispatchCommand(Bukkit.getServer().getConsoleSender(), "mmob command")
Doesnt work! =(( It says they are spawned, tells me the location where they are supposed to be spawned, (i quintuple checked that they are spawning at the correct location and world) but they never really show up
Are you sure something's not blocking mob spawning at the target location?
I just tried it myself from console, mmob spawn warlock 15575 70 20192 world
and it worked. You've tried it yourself from console as well?
Only conflating plugin would be griefprevention, which i'm fairly sure magic has some support for correct? Thanks for this insanely fast response haha. I'd love to know some greifprevention settings to mess with to allow them to spawn and fix this issue (the mobs are being spawned in admin claimed areas so players cant grief these locations)
Magic has no plugin integration having to do with mob spawning, it's just pvp and build permissions for the most part. I'm not familiar enough with GP to know if it would block mobs from spawning.
WorldGuard would be the main suspect- but if the command works when you run it manually from the console, but not via your plugin, there may be something else wrong.
Plugins Here:
GriefPrevention
Essentials
EssentialSpawns
Holograms
Luckperms
Mcmmo
Votifier
Worldedit
MAGIC <3
No worldguard right now.
But yeah it definitely runs through console, the same exact command when ran through the plugin though makes console say the the mobs were spawned, but nothing happens.
There should be literally no difference between dispatchCommand(consoleSender) and running a command via console- so that is really pretty weird.
I would suggest having your plugin log the exact command it's running, then try running that command yourself.