Where can I find the build with the 1.8 block compatibility? Is it going to be under Latest Alpha/Pre-release Builds?
Because there's nothing there, currently.
It's in the section under that:
Latest Development Builds: (use at your own risk!)
Bukkit/Spigot v1.6.4-v1.8.0: Dynmap v2.1-alpha-1: [Direct]
Minecraft v1.8.0 with Forge v11.14.0: Dynmap v2.1-alpha-1: [Direct]
These aren't released - just available. I'm hoping to drop an alpha release in the next day or so, at least for Spigot 1.8 and for Forge 1.8
Latest Development Builds: (use at your own risk!)
Bukkit/Spigot v1.6.4-v1.8.0: Dynmap v2.1-alpha-1: [Direct]
Minecraft v1.8.0 with Forge v11.14.0: Dynmap v2.1-alpha-1: [Direct]
These aren't released - just available. I'm hoping to drop an alpha release in the next day or so, at least for Spigot 1.8 and for Forge 1.8
I do have one issue that wasn't fixed in this version. Whenever I do /dynmap fullrender it renders 100 chunks and stops and says it can't find any chunks. It's on a custom map, but more than 100 chunks from spawn have been explored. It's also very spotty with black chunks on the map that don't go away unless you stand in the area for like 10 minutes -- you can't just fly through it.
I'm using DynMap 2.0.0 (at present; previously 1.9.4, and also tried 2.1 alpha) DynMapCBBridge (same version), and DynMapTowny on Cauldron server version cauldron-1.6.4-1.965.21.204-server. The web server comes up, it talks to Towny and gets town limits and displays them, but it won't create the actual map. It renders from one or two to a half dozen or so tiles on each startup of the server, and then stops. This problem first appeared while using 1.9.4; I just moved my server to a machine with much faster disk in case it was a disk I/O problem, but that didn't help. It had built up a pending queue of several thousand tiles, but would not process the queue. So then I tried updating DynMap from 1.9.4 to 2.0.0 and to 2.1 alpha1, in the hope one of them would work, and still no joy.
Any tips for how to get DynMap going again? Is there any way to get internal diagnostics out of it and see why it's not rendering anything?
I am also having this problem using the Spigot 1.8 alpha release download (File name is dynmap-HEAD). Is this a common issue with a simple fix, or is it simply because an outdated version of spigot is being used? (I believe my server on the other hand is running the current build of Spigot.)
I am also having this problem using the Spigot 1.8 alpha release download (File name is dynmap-HEAD). Is this a common issue with a simple fix, or is it simply because an outdated version of spigot is being used? (I believe my server on the other hand is running the current build of Spigot.)
I'm running this on the CraftBukkit build taken from 1.8 spigot supply.
"dynmap-2.0.1alpha_HEAD.jar" works fine after I deleted the contents of the target web server location and copied in the new /web folder from the plugins directory. Don't forget that you have to restart a few times, once to create the new plugins\web and again after you copy this to the server folder.
I'm running this on the CraftBukkit build taken from 1.8 spigot supply.
"dynmap-2.0.1alpha_HEAD.jar" works fine after I deleted the contents of the target web server location and copied in the new /web folder from the plugins directory. Don't forget that you have to restart a few times, once to create the new plugins\web and again after you copy this to the server folder.
dynmap-2.0.1alpha_HEAD.jar from where exactly...? I'm trying to find a version that works with Cauldron-1.6.4-1.965.21.204-server (formerly known as MCPC-Plus). I currently have Dynmap-1.9.4-forge-9.11.1.jar, Dynmap-2.0.0-forge-9.11.1.jar, and Dynmap-2.1-alpha1-forge-1.6.4.jar, with Dynmap-2.0.0 currently actually installed, but none of them will render tiles other than just two or three tiles on intial server start. (Even though 2.0.0 generates and displays a working map ... it just doesn't have any tiles in its map.)
mikeprimm, any advice...? Any ideas what's going wrong here? It's obviously able to render tiles, it just won't render more than three or four per server start.
mikeprimm, any advice...? Any ideas what's going wrong here? It's obviously able to render tiles, it just won't render more than three or four per server start.
I, too have been unable to have the map generate. It just kinda sits there, empty. Every once in a while the map will render a few times, and after a long while I had around 1/3 of the screen generated with map. But then changing the view starts it all again.
This is both with the internal webserver and apache (though I doubt it makes much of a difference). I'm running the latest spigot on openjdk 7 on Linux.
I tried in-game /dynmap render, /dynmap fullrender, etc, etc... as well as console dynmap fullrender, and nothing works. Dynmap is generating a handful of tiles on each start of the server, and then it stops. I have something like 6000 tile renders queued, but nothing will make it process the queue.
Update: It's possible this is a Cauldron issue in my case. I've poked bloodmc to see whether he has any insights.
Hi. Yesterday i updated my server to spigot 1.8 build 1958. I use dynmap 2.1 alpha 1 . but if someone move on the already explored map it looks like this: MyLivemap
it seems that dynmap isn't able to create correct surface.
Can i fix that, or do i have to wait für the next update. sometimes my browser send a message like web files has to be on version 2.1 or something like that. if i press f5, it loads perfect.
help please.
edit:
my presumption is: the changes of the designation of the blocks. in terms of the irem ID's. these were not abolished?
Is your server primarily German-speaking? I'd like to join.
It's in the section under that:
Latest Development Builds: (use at your own risk!)
Bukkit/Spigot v1.6.4-v1.8.0: Dynmap v2.1-alpha-1: [Direct]
Minecraft v1.8.0 with Forge v11.14.0: Dynmap v2.1-alpha-1: [Direct]
These aren't released - just available. I'm hoping to drop an alpha release in the next day or so, at least for Spigot 1.8 and for Forge 1.8
[dynmap] Enabling dynmap v2.1-SNAPSHOT-1077
Dynmap is disabled (unsupported platform)
No other errors - just those two lines. Spigot 1.8 R0.1 (da32fe1)
PS: this is another plugin, but Dynmap-WorldGuard player names shows as UUID
I do have one issue that wasn't fixed in this version. Whenever I do /dynmap fullrender it renders 100 chunks and stops and says it can't find any chunks. It's on a custom map, but more than 100 chunks from spawn have been explored. It's also very spotty with black chunks on the map that don't go away unless you stand in the area for like 10 minutes -- you can't just fly through it.
Any tips for how to get DynMap going again? Is there any way to get internal diagnostics out of it and see why it's not rendering anything?
Regards and Thank you so much mikeprimm
I am also having this problem using the Spigot 1.8 alpha release download (File name is dynmap-HEAD). Is this a common issue with a simple fix, or is it simply because an outdated version of spigot is being used? (I believe my server on the other hand is running the current build of Spigot.)
I have exactly the same problem. Anyone?
Thanks, I will try it.
Regards
dynmap-2.0.1alpha_HEAD.jar from where exactly...? I'm trying to find a version that works with Cauldron-1.6.4-1.965.21.204-server (formerly known as MCPC-Plus). I currently have Dynmap-1.9.4-forge-9.11.1.jar, Dynmap-2.0.0-forge-9.11.1.jar, and Dynmap-2.1-alpha1-forge-1.6.4.jar, with Dynmap-2.0.0 currently actually installed, but none of them will render tiles other than just two or three tiles on intial server start. (Even though 2.0.0 generates and displays a working map ... it just doesn't have any tiles in its map.)
mikeprimm, any advice...? Any ideas what's going wrong here? It's obviously able to render tiles, it just won't render more than three or four per server start.
I, too have been unable to have the map generate. It just kinda sits there, empty. Every once in a while the map will render a few times, and after a long while I had around 1/3 of the screen generated with map. But then changing the view starts it all again.
This is both with the internal webserver and apache (though I doubt it makes much of a difference). I'm running the latest spigot on openjdk 7 on Linux.
World protection is not working with the latest version for spigot 1.8. /dmap worldset WORLDID protected:true
players can still see the worlds/maps
What's the difference between protected and disabled? Is there something more that protected:true does than disabled:true?
Update: It's possible this is a Cauldron issue in my case. I've poked bloodmc to see whether he has any insights.
Is your server primarily German-speaking? I'd like to join.