Remove that file and download plugin anew. It seems you have a decompiled (developer's) version of mod in the folder, instead of regular one.
ah i bet that's it, i usually use the developer versions when available since they're most up to date.
Rollback Post to RevisionRollBack
24 hours gone again, wasted in futility, welcome to minecraft modding, that is (unfortunately) our community.
(an ode to minecraft modding)
i keep making the same mistake, i think "oh, i've given them a few months, surely it'll be fixed by now" THAT is why i seem to ALWAYS be angry to some of you, my advice is to get the lead out.
there were nice things here, until the mod author threw a tantrum.
I tried to check how to disable the nether and the end, but whatever I do it isn't working so I guess I do something wrong?
Everything in the worlds.txt already has a # in front of it, so I'm not sure if I just need to remove those tags or something else, somebody able to assist me?
ah i bet that's it, i usually use the developer versions when available since they're most up to date.
Don't confuse head build (the so-called "bleeding edge" version) with deobfuscated JAR (which is sometimes called a "dev" version). They are parallel categories. Deobfuscated version exists for developers to debug mod interaction, and you probably need a special server for it to run.
So, I'm having an issue where it's not rendering Nightmaps properly with the latest 2.3 alpha version for MC1.9 from the bukkitdev page. Figured I'd mention, see if it's a known issue, if it's fixable, or what. No rush on it if it's the first time hearing about it, just status update on that issue is fine.
forge on mineOS (latest forge, MC 1.7.10), the latest from mike primm's build server, unsure, yes from the console haven't tried from the client though, they appear to work normally.
it seems to function just fine although i never see the dynmap message i used to about starting the web server and all that in the console when the server starts up and also the webpage to view the map doesn't load, logs here: http://paste.ubuntu.com/15202233/
You are running an ancient version of Java 7. Update to Java 8, current release.
Then try running the latest release for Forge for Minecraft 1.7.10 instead of a dev build.
Rollback Post to RevisionRollBack
HappyDiggers is a small Minecraft community with several different servers: Adventure, Arena PvE, Feed The Beast, Skyblock, Small World, Towny, Prison, Vanilla and Snapshot.
So I'm having an interesting issue with the alpha 2.3 release for 1.8.9. On my personal instance of Minecraft I'm able to view dynmap through localhost:8123. Now on my 1.8.9 server (this is a dedicated server in a data center) I can not view it through http://ipaddresss:8123. I know the appropriate ports are open because I also have a 1.7.10 server. When I boot up the 1.7.10 server I'm able to connect from the outside to http://ipaddress:8123. It seems to me that when I launch my modded 1.8.9 server that dynmap isn't even downloaded the necessary files it should on start. This is all been with the forge version btw. I've tried it with the following two versions of forge:
forge-1.8.9-11.15.1.1750-universal
forge-1.8.9-11.15.1.1764-universal
Any help would be welcomed. Thanks!
edit: I resolved it. It was a huge derp on my part. so no worries!
I installed DynMap 1.9 today, I reloaded the server and the DynMap plugin was in my server. I followed the "First time use" guide on Bukkit (http://dev.bukkit.org/bukkit-plugins/dynmap/). I did what you wrote there, and went to the website of the map of my worlds.
(Before Minecraft 1.9 my server was in 1.8, and after the relase of Minecraft 1.9 I restarted my words, and started with new words and inventory. So now I use the new map in 1.9.)
And on the website I see only the old map I used in 1.8
I have heard from several people (and even md_5 on irc) that dynmap is making mobs freeze and getting people stuck in minecarts sometimes (entities are still in game but you cant interact with them) is that something that you are working on fixing?
latest spigot 1.9 image, with logblock, bukkitstatistics & dynmap running
The Meaning of Life, the Universe, and Everything.
Join Date:
3/24/2016
Posts:
46
Member Details
does dynmap work fine with the latest forge 1.7.10 #1614? i ask because i've never seen the messages from it that dynmap has successfully started when the server loads.
edit, i think i found the problem the full version number for FML version i have to use (yes, have to, mods require 1614, not a choice) is "10.13.4.1614" and in the OP it states it's used with forge version 10.13.2.xxxx, can anyone confirm/deny?
As far as I can tell so far, everything appears to be working. Is this error something to worry about? I understand this is an alpha build, but just curious. Thank you!
does dynmap work fine with the latest forge 1.7.10 #1614? i ask because i've never seen the messages from it that dynmap has successfully started when the server loads.
edit, i think i found the problem the full version number for FML version i have to use (yes, have to, mods require 1614, not a choice) is "10.13.4.1614" and in the OP it states it's used with forge version 10.13.2.xxxx, can anyone confirm/deny?
ah i bet that's it, i usually use the developer versions when available since they're most up to date.
24 hours gone again, wasted in futility, welcome to minecraft modding, that is (unfortunately) our community.
(an ode to minecraft modding)
i keep making the same mistake, i think "oh, i've given them a few months, surely it'll be fixed by now" THAT is why i seem to ALWAYS be angry to some of you, my advice is to get the lead out.
there were nice things here, until the mod author threw a tantrum.
I tried to check how to disable the nether and the end, but whatever I do it isn't working so I guess I do something wrong?
Everything in the worlds.txt already has a # in front of it, so I'm not sure if I just need to remove those tags or something else, somebody able to assist me?
Don't confuse head build (the so-called "bleeding edge" version) with deobfuscated JAR (which is sometimes called a "dev" version). They are parallel categories. Deobfuscated version exists for developers to debug mod interaction, and you probably need a special server for it to run.
Hey Mike,
FYI looks like grass paths (right click with shovel) are not rendering correctly.
Dynmap for 1.9 seems way more heavy then 1.8?
With Dynmap turned on and 15 players I recieve a tps of 8-13. When I disable dynmap /plugman disable dynmap the tps is back up 19,5+
Is this going to be updated to 1.9? Because I absolutely love dynmaps.
Not as long as you keep pestering.
So, I'm having an issue where it's not rendering Nightmaps properly with the latest 2.3 alpha version for MC1.9 from the bukkitdev page. Figured I'd mention, see if it's a known issue, if it's fixable, or what. No rush on it if it's the first time hearing about it, just status update on that issue is fine.
You are running an ancient version of Java 7. Update to Java 8, current release.
Then try running the latest release for Forge for Minecraft 1.7.10 instead of a dev build.
HappyDiggers is a small Minecraft community with several different servers: Adventure, Arena PvE, Feed The Beast, Skyblock, Small World, Towny, Prison, Vanilla and Snapshot.
So I'm having an interesting issue with the alpha 2.3 release for 1.8.9. On my personal instance of Minecraft I'm able to view dynmap through localhost:8123. Now on my 1.8.9 server (this is a dedicated server in a data center) I can not view it through http://ipaddresss:8123. I know the appropriate ports are open because I also have a 1.7.10 server. When I boot up the 1.7.10 server I'm able to connect from the outside to http://ipaddress:8123. It seems to me that when I launch my modded 1.8.9 server that dynmap isn't even downloaded the necessary files it should on start. This is all been with the forge version btw. I've tried it with the following two versions of forge:
forge-1.8.9-11.15.1.1750-universal
forge-1.8.9-11.15.1.1764-universal
Any help would be welcomed. Thanks!
edit: I resolved it. It was a huge derp on my part. so no worries!
On the new version, I'm getting errors for TerrainControl biomes that I didn't before:
[01:35:00] [Dynmap Render Thread/WARN]: java.lang.IllegalArgumentException: No enum constant org.bukkit.block.Biome.SOULDESERT
Any help?
Hello!
I installed DynMap 1.9 today, I reloaded the server and the DynMap plugin was in my server. I followed the "First time use" guide on Bukkit (http://dev.bukkit.org/bukkit-plugins/dynmap/). I did what you wrote there, and went to the website of the map of my worlds.
(Before Minecraft 1.9 my server was in 1.8, and after the relase of Minecraft 1.9 I restarted my words, and started with new words and inventory. So now I use the new map in 1.9.)
And on the website I see only the old map I used in 1.8
My server is in Craftbukkit 1.9
The plugin works, no crash report.
What can I do?
I have my new world there, but it is black bars everywhere, how to fix?
I deleted the old DynMap folder, yes. I'm using the same word(name) just removed the files in the folders.
I have heard from several people (and even md_5 on irc) that dynmap is making mobs freeze and getting people stuck in minecarts sometimes (entities are still in game but you cant interact with them) is that something that you are working on fixing?
latest spigot 1.9 image, with logblock, bukkitstatistics & dynmap running
does dynmap work fine with the latest forge 1.7.10 #1614? i ask because i've never seen the messages from it that dynmap has successfully started when the server loads.
edit, i think i found the problem the full version number for FML version i have to use (yes, have to, mods require 1614, not a choice) is "10.13.4.1614" and in the OP it states it's used with forge version 10.13.2.xxxx, can anyone confirm/deny?
Hello,
I just installed v2.3-alpha-1 for 1.9. I'm using CraftBukkit and it's a brand new server. I currently have 4 plugins installed:
- BuyCraft
- ClearLag
- Ding
- Dynmap
I have this error in the console: [Server] ERROR [dynmap] Error reading plugins/dynmap/markers.yml
My markers.yml file looks like this (I didn't change anything):
As far as I can tell so far, everything appears to be working. Is this error something to worry about? I understand this is an alpha build, but just curious. Thank you!
server crash report: http://pastebin.com/VDdNt7fn
i also get this client crash report if i push J while on the server to try to open the journeymap dialogue:
http://pastebin.com/wyW3NEXW
bumping for a response...