Would there be any way we could actually disable the rendering of the world itself, but rather use a hand drawn map as a backslash pic and just have the characters themselves rendered upon it instead?
when i start the Fullrender with Dynmap v1.6-643 i and CB# 2526 (have to use this Built because of the JSONAPI Issue) get this NPE-Error: http://pastebin.com/DK5LyvF4
when i start the Fullrender with Dynmap v1.6-643 i and CB# 2526 (have to use this Built because of the JSONAPI Issue) get this NPE-Error: http://pastebin.com/DK5LyvF4
What does that mean?
No idea how we could cause that - the null is on internal data for the world object in Bukkit. Was the world unloaded while you were rendering?
I'm having a little trouble using dynmap with Apache, would appreciate any suggestions!
The chrome renders perfectly, labels show up, tiles render and load, and the list populates with players. But, after one second, the players' names in the sidebar are greyed out and they never show up on the map. Here's where I am config-wise:
Files have been left in plugins/dynmap/web and are symlinked to the appropriate web directory. All files are 755 and owned by the bukkit user. dynmap is running with internal server disabled and configuration.txt altered appropriately for json. Nothing has been enabled (and has experimentally been explicitly disabled) regarding greying out the player based on height, brightness, sexual orientation, etc..
So. Where do I poke next?
EDIT: Made a discovery. This is my map's current json - the timestamp updates, but server time is -1 and it isn't fetching my position/health/armor/astrological sign. And I should have mentioned this first, but I'm using Spigot.
Would there be any way we could actually disable the rendering of the world itself, but rather use a hand drawn map as a backslash pic and just have the characters themselves rendered upon it instead?
I'm having a little trouble using dynmap with Apache, would appreciate any suggestions!
The chrome renders perfectly, labels show up, tiles render and load, and the list populates with players. But, after one second, the players' names in the sidebar are greyed out and they never show up on the map. Here's where I am config-wise:
Files have been left in plugins/dynmap/web and are symlinked to the appropriate web directory. All files are 755 and owned by the bukkit user. dynmap is running with internal server disabled and configuration.txt altered appropriately for json. Nothing has been enabled (and has experimentally been explicitly disabled) regarding greying out the player based on height, brightness, sexual orientation, etc..
So. Where do I poke next?
Which things did you disable - sendposition being false will cause the players to never appear on the map.
Which things did you disable - sendposition being false will cause the players to never appear on the map.
I went back to vanilla config, removing the internal client update section and un-commenting only writeInterval (1), sendHealth (true), and sendPosition (true) under the json section. Config here.
Strangely I find the rectangles in the middle. It was rendered 2 days ago. But now it's dark. Are this Chunkfiles broken and Dynmap can't render it? :S
version: 0.20
#
# Default template for "Normal" environment worlds (deftemplatesuffix="lhires")
# Uses the HDMap renderer with view from the SE with the "hires" resolution (16 pixels per block edge)
#
# This file MAY need to be replaced during an upgrade - rename file to 'custom-normal-hires.txt' if you wish to customize it
#
templates:
# Template for normal world (HDMap hires)
normal-hires:
enabled: true
# Number of extra zoom-out levels for world (each level is twice as big as the previous one)
extrazoomout: 2
#center:
# x: 0
# y: 64
# z: 0
maps:
- class: org.dynmap.hdmap.HDMap
name: flat
title: "Flat"
prefix: flat
perspective: iso_S_90_lowres
shader: stdtexture
lighting: shadows
mapzoomin: 1
version: 0.20
#
# Default template for "Normal" environment worlds (deftemplatesuffix="lhires")
# Uses the HDMap renderer with view from the SE with the "hires" resolution (16 pixels per block edge)
#
# This file MAY need to be replaced during an upgrade - rename file to 'custom-normal-hires.txt' if you wish to customize it
#
templates:
# Template for normal world (HDMap hires)
normal-hires:
enabled: true
# Number of extra zoom-out levels for world (each level is twice as big as the previous one)
extrazoomout: 2
#center:
# x: 0
# y: 64
# z: 0
maps:
- class: org.dynmap.hdmap.HDMap
name: flat
title: "Flat"
prefix: flat
perspective: iso_S_90_lowres
shader: stdtexture
lighting: shadows
mapzoomin: 1
- class: org.dynmap.hdmap.HDMap
name: surface
title: "Surface"
prefix: t
perspective: iso_SE_30_hires
shader: stdtexture
lighting: brightnightandday
mapzoomin: 1
- class: org.dynmap.hdmap.HDMap
name: cave
title: "Cave"
prefix: ct
perspective: iso_SE_60_lowres
shader: cave
lighting: default
mapzoomin: 3
to
version: 0.20
#
# Default template for "Normal" environment worlds (deftemplatesuffix="lhires")
# Uses the HDMap renderer with view from the SE with the "hires" resolution (16 pixels per block edge)
#
# This file MAY need to be replaced during an upgrade - rename file to 'custom-normal-hires.txt' if you wish to customize it
#
templates:
# Template for normal world (HDMap hires)
normal-hires:
enabled: true
# Number of extra zoom-out levels for world (each level is twice as big as the previous one)
extrazoomout: 2
#center:
# x: 0
# y: 64
# z: 0
maps:
- class: org.dynmap.hdmap.HDMap
name: flat
title: "Flat"
prefix: flat
perspective: iso_S_90_lowres
shader: stdtexture
lighting: shadows
mapzoomin: 1
version: 0.20
#
# Default template for "Normal" environment worlds (deftemplatesuffix="lhires")
# Uses the HDMap renderer with view from the SE with the "hires" resolution (16 pixels per block edge)
#
# This file MAY need to be replaced during an upgrade - rename file to 'custom-normal-hires.txt' if you wish to customize it
#
templates:
# Template for normal world (HDMap hires)
normal-hires:
enabled: true
# Number of extra zoom-out levels for world (each level is twice as big as the previous one)
extrazoomout: 2
#center:
# x: 0
# y: 64
# z: 0
maps:
- class: org.dynmap.hdmap.HDMap
name: flat
title: "Flat"
prefix: flat
perspective: iso_S_90_lowres
shader: stdtexture
lighting: shadows
mapzoomin: 1
- class: org.dynmap.hdmap.HDMap
name: surface
title: "Surface"
prefix: t
perspective: iso_SE_30_hires
shader: stdtexture
lighting: brightnightandday
mapzoomin: 1
- class: org.dynmap.hdmap.HDMap
name: surface2
title: "Surface2"
prefix: t
perspective: iso_NW_30_hires
shader: stdtexture
lighting: brightnightandday
mapzoomin: 1
- class: org.dynmap.hdmap.HDMap
name: cave
title: "Cave"
prefix: ct
perspective: iso_SE_60_lowres
shader: cave
lighting: default
mapzoomin: 3
shoudn't this work? I get an error starting the server. when i try to config the worlds.txt i get an instant error.
Regars,
Marcel
Can't tell - your indentation looks funky (those files are YAML, so indentation is very sensitive - and don't use tabs).
Result of a very long series of discussions/testing/feedback (see https://github.com/w...map/issues/1191), particularly with folks using MCPC+ with FTB Ultimate. We're getting blamed for all kinds of memory leaks that appear to be quite a bit worse with the Bukkit APIs on MCPC+ and other mods and/or plugins - none of which I can fix, and many of which appear to be due to mismatches between what the Bukkit API assumes as behavior, as well as some of the other enhancements to Bukkit/Spigot that have been pulled into MCPC+, and the behavior assumed by other Forge mods (particularly ones that hook into the chunk loading/unloading).
That is some sad news. I did try the forge version but it broke a bunch of my bukkit plugins (yes I used the bridge). I guess, atm I'm gonna run my server without dynmap. Damn, haven't done that well, ever...
That is some sad news. I did try the forge version but it broke a bunch of my bukkit plugins (yes I used the bridge). I guess, atm I'm gonna run my server without dynmap. Damn, haven't done that well, ever...
Try last night's dev builds - should work with pretty much everything (update both DynmapForge and DynmapCBBridge)
Have you rendered the map yet then? Let people play and place blocks or done a /dynmap fullrender [mapname]?
I have one thing I'm curious about.
"Latest Alpha/Pre-release Builds (1.6-alpha-3)"
This version doesn't have the bukkit plugin listed as usable by MCPC+ but the mod is instead.
Since I'm been using the plugin for well, ever, I don't really want to switch from the bukkit plugin I know and love to the mod I don't know. So why is MCPC+ not listed on the bukkit version? Does the bukkit version still work with MCPC+?
I tried doing the /dynmap fullrender [map name]. It said, "Full render starting on world 'overworld'..." which is the name of my world. I looked back at the map website using my ip, but it still didn't work. Is there anything else I can configure so that I can see the terrain on the map?
Add support for using v1.5.x texture packs (pre v1.5.x texture packs are still supported)
[Forge] Fix memory leak on MCPC+ v1.4.7 and v1.5.1
Update web UI library (Leaflet) and jQuery to better support mobile and new browsers (thanks to crussell52!)
[Bukkit] Switch logger to use logger provided for plugin
Handle 'top-on-all-sides' block rendering for non-standard double-slab blocks
Handle exception in rendering with some add-on BC pipes
Fix issue with MFR support on older builds
[Forge v6-5.0-7.7.1] Add API support
Update Biomes O Plenty support (configuration breaks, new blocks)
Fix render exception when encountering unsupported BC-style pipes
Add option (initial-zoomout-validate setting) to disable startup-time zoom out tile validation (can be quite expensive on large maps)
Add robots.txt file to web to discourage indexing of map by bots (Google, etc)
Fix ExtraBees to support new config values
Avoid writing tile files for all transparent tiles - reduces file count somewhat (15-20%)
[Forge v6.5.0-v7.7.1] Add support for Dynmap API on Forge, and support for Bukkit API compatibility bridge (DynmapCBBridge) - lets Bukkit mods be used on MCPC+ or BukkitForge modded Forge servers when DynmapCBBridge is added as a Bukkit plugin
Switch support for MCPC+ from Bukkit build to Forge builds to fix memory leak issues
[Bukkit] Remove MCPC-Plus supprt from Bukkit version - add message directing use of Forge version
Note: The links for the forge versions were incorrect when I posted them last night - if you downloaded a ZIP named 'Dynmap-1.6-alpha-3-forge-*.zip', download again - the 1.6 release level files should not contain the name '1.6-alpha-3', just '1.6'.
i just wanted to let everyone know the directions to add Dynmap to another server makes no mention of how to setup if you have a virtual server setup, specifically i'm talking about debian .
you should not add the lines to the default.conf
they should be installed in the conf for the website you want it under.
also those lines should be integrated into the proper location in the conf file and not just added at the end as you most likly will be duplicating commands already there.
when i start the Fullrender with Dynmap v1.6-643 i and CB# 2526 (have to use this Built because of the JSONAPI Issue) get this NPE-Error: http://pastebin.com/DK5LyvF4
What does that mean?
No idea how we could cause that - the null is on internal data for the world object in Bukkit. Was the world unloaded while you were rendering?
I'm having a little trouble using dynmap with Apache, would appreciate any suggestions!
The chrome renders perfectly, labels show up, tiles render and load, and the list populates with players. But, after one second, the players' names in the sidebar are greyed out and they never show up on the map. Here's where I am config-wise:
Files have been left in plugins/dynmap/web and are symlinked to the appropriate web directory. All files are 755 and owned by the bukkit user. dynmap is running with internal server disabled and configuration.txt altered appropriately for json. Nothing has been enabled (and has experimentally been explicitly disabled) regarding greying out the player based on height, brightness, sexual orientation, etc..
So. Where do I poke next?
EDIT: Made a discovery. This is my map's current json - the timestamp updates, but server time is -1 and it isn't fetching my position/health/armor/astrological sign. And I should have mentioned this first, but I'm using Spigot.
No - nothing like that is supported.
Which things did you disable - sendposition being false will cause the players to never appear on the map.
I went back to vanilla config, removing the internal client update section and un-commenting only writeInterval (1), sendHealth (true), and sendPosition (true) under the json section. Config here.
Having found: https://github.com/webbukkit/DynmapCore/blob/master/src/main/java/org/dynmap/ClientUpdateComponent.java#L110
this is obviously something dumb I'm doing with plugin interactions or something being outdated. Thanks for your time, I'll figure it out.
No, the Rendering works at the beginning: http://pastebin.com/7daRk2pR
Here is the Address to my Dynmap: www.dynmap.revoplay.de
Strangely I find the rectangles in the middle. It was rendered 2 days ago. But now it's dark. Are this Chunkfiles broken and Dynmap can't render it? :S
Can't tell - your indentation looks funky (those files are YAML, so indentation is very sensitive - and don't use tabs).
Is there any way to change the black tile background to a transparent background?
That is some sad news. I did try the forge version but it broke a bunch of my bukkit plugins (yes I used the bridge). I guess, atm I'm gonna run my server without dynmap. Damn, haven't done that well, ever...
Try last night's dev builds - should work with pretty much everything (update both DynmapForge and DynmapCBBridge)
under dynmap/web/css/dynmap_style.css
Change
background: #000;
to
background: transparent;
the black background is gone!
http://pastebin.com/A2KGfFt9
my texture pack 'defscape' is 1.5.1 version
Edit:
Btw, the link for MC 1.4.7 still points to a zip named 1.6 Alpha 3, is this intended?
Good catch on the links - all are good now.
you should not add the lines to the default.conf
they should be installed in the conf for the website you want it under.
also those lines should be integrated into the proper location in the conf file and not just added at the end as you most likly will be duplicating commands already there.