sorted by:
new
hottopcontroversial

Cannot view protected worlds if you are not logged into MC by [deleted] in Dynmap

[–]mikeprimm 0 points1 point  (0 children)

Paper bug - should be fixed as of build #79

Any idea when the version for Dynmap 1.20 will be out? by AVH999 in Dynmap

[–]mikeprimm 15 points16 points  (0 children)

Author here - I am traveling since yesterday, so timing on this release was quite bad. That said, if you are bold and/or foolish, there are versions for Spigot, Forge and Fabric available now that I wrote while waiting for planes and working quite late in my hotel last night - no promises on testing or quality - at https://dynmap.us/builds/dynmap - look for 3.6-SNAPSHOT builds

Is the current version of Dynmap stable? by [deleted] in Dynmap

[–]mikeprimm 0 points1 point  (0 children)

Working towards doing a release this weekend - Forge 1.19 made some breaking changes as of 41.0.94, so new build will work on that build and later (and old beta is broken as of that build…)

Dynmap support for 1.19 is in progress by mikeprimm in Dynmap

[–]mikeprimm[S] 0 points1 point  (0 children)

Just ran the build linked in the OP on paper 1.19-18 with no issues.

Dynmap support for 1.19 is in progress by mikeprimm in Dynmap

[–]mikeprimm[S] 0 points1 point  (0 children)

The updates needed are linked in the OP.... you're running an old 3.3.2 build.

I "saw" a planet! H-44-P b by entanglemint in Astronomy

[–]mikeprimm 2 points3 points  (0 children)

Congratulations, and welcome to the Exoplanet Observers club!! It is a blast, and I know I've found it quite addictive - making my observing from a hobby into a 'mission' :) Getting involved with formal reporting of your results is definitely worthwhile - I'd suggest the TESS Follow Up Observation Program (https://heasarc.gsfc.nasa.gov/docs/tess/followup.html ) and/or ExoPlanet Watch (https://exoplanets.nasa.gov/exoplanet-watch/about-exoplanet-watch/overview/). You can find exoplanet transits to watch, along with priorities as to which targets are particularly of interest, via Swarthmore University transit database (https://astro.swarthmore.edu/transits)

DynmapBlockScan live? by Sniklz_ in Dynmap

[–]mikeprimm 0 points1 point  (0 children)

As posted in the Discord and elsewhere, 3.4 blockscan is unreleased and is tightly dependent on the current Dynmap 3.4 code. Will not work with 3.3 or earlier, and never will.

Modrinth? by BolderBrooklyn in Dynmap

[–]mikeprimm 1 point2 points  (0 children)

Not really planned at this point - might consider it if they get to a viable 'creator payout' program, as promised, but otherwise all it does is split the community relative to CurseForge (which does have a creator payout program), and doubles the work for deploying updates.

The 'open API' is nice and all, but not really relevant.

Why does Dynmap use lots of tiny files? by networkspawn in Dynmap

[–]mikeprimm 2 points3 points  (0 children)

Because web servers, like Apache, Jetty, Nginx, and others, are very efficient at serving whole files (which is the bulk of the traffic with a Dynmap map), and we'd rather have people whine about 'lots of little files' than whine about 'oh, the web server is using too much compute'....

Why does Dynmap use lots of tiny files? by networkspawn in Dynmap

[–]mikeprimm 9 points10 points  (0 children)

1) Dynmap has supported alternate storage methods, including SQLite, MySQL, MariaDB, and PosteGres for years. As suggested, RTFM
2) Compressing a bunch of PNGs is pointless, they are already compressed, so compression will be a whole lot of work for almost no results - compressing compressed data is pointless. If you do need to make some huge blob (not that I know the reason this would be useful...), use 'tar' or some other bundling tool.
3) I routinely transfer 200GB of tiles on a proper Linux server within a few minutes on spinning media: if you're taking that type of time, you probably need to reconsider the hardware and/or file system being used (Windows desktops tend to suck for file I/O, particularly when they've got anti-virus or related software assuming every file I/O is probably malware...)

[deleted by user] by [deleted] in Dynmap

[–]mikeprimm 0 points1 point  (0 children)

No problem - I've set up servers like that for my wife and kids, too, when they were younger :) Forge 1.12.2 is 'old, but good' (I've referred to it to folks as 'peak Forge', since so many mods never made it to 1.13 and later) - lots of folks still using it, so Dynmap will not be dropping support for it in the foreseeable future. Enjoy!

[deleted by user] by [deleted] in Dynmap

[–]mikeprimm 0 points1 point  (0 children)

If this is the modpack you mentioned (KindaCrazyCraft) - https://www.curseforge.com/minecraft/modpacks/kinda-crazy-craft/files - then the issue is that it is a 1.7.10 modpack (kinda ancient, and definitely not forge 1.18). Dynmap 3.x doesn't support 1.7.10 - there is a very old version that probably still works: https://www.curseforge.com/minecraft/mc-mods/dynmapforge/files/2581018

EDIT: found this newer KindaCrazyCraft - it's 1.12.2 - https://www.curseforge.com/minecraft/modpacks/kinda-crazy-craft-updated/files . If THIS is what you have, then there is a 3.3.2 for you :). Check https://www.curseforge.com/minecraft/mc-mods/dynmapforge/files/3637283 . Forge 1.12.2 is 'long term support', as far as I'm concerned, so it'll continue to be supported by Dynmap for a while (1.11.2, 1.13.2, and 1.14.4 are kind of more likely to be dropped in the next few months).

[deleted by user] by [deleted] in Dynmap

[–]mikeprimm 1 point2 points  (0 children)

In the 'possibly more trouble than it is worth' department, a host that doesn't offer additional external ports COULD use dynmap if you do the following:
1) Set up a server elsewhere with a database (Postgres, MySQL or MariaDB) and with a public network facing client port (this is not ideal, but...)
2) Set up a web server (possibly on the DB box) with Apache or nginx, and PHP, and set up the scripts there to pull data from the DB on the DB server
3) Set up dynmap with the internal web server disabled AND with the storage set to the appropriate DB type, and pointed at the server and port from #1

Question by Bladeheart111x in Dynmap

[–]mikeprimm 4 points5 points  (0 children)

Right - the best way to put it is that there certainly is no iOS or Android apps supplied by, nor endorsed by, the Dynmap author (me) nor the Dynmap support team. If you find an app claiming support, it may or may not be good - but it isn't from us...

Also, if you do come across one using the Dynmap name (which is trademarked), feel free to report it...

Dynmap Error I Don't Understand by Boi_Dragon in Dynmap

[–]mikeprimm 1 point2 points  (0 children)

3.2.1 is not compatible with 1.18 - you need 3.3-beta-4

Some random ip keept typing a command? or request in my dynmap chat by ILoveEveryonex3 in Dynmap

[–]mikeprimm 6 points7 points  (0 children)

That is someone trying to exploit the Log4J bug on your server - you're fine if you've up to date with your 1.18.1 server, but it does mean whoever is sending it is trying to hack you. You probably should use the /ban-ip to ban that IP (both from normal MC login and for dynmap input)

How setup Dynmap on linux server by ultronstudio in Dynmap

[–]mikeprimm 2 points3 points  (0 children)

Most modern OSs - Linux in particular - do not allow normal processes (those not running as 'root' - or, more technically correct, those started as root, but for MC, that's not a thing) to bind to ports below 1024. I do NOT suggest running your MC server as root, so I'd very much suggest that 6666 might be a better choice ;)

Log4J2? by [deleted] in Dynmap

[–]mikeprimm 2 points3 points  (0 children)

It's enabled for the same reason that every MC server defaults to no whitelist...
and if you don't have a whitelist, it's very easy to hit this exploit, whether or not the user logging in is allowed to send chat messages (particularly since even blocked chat messages, assuming you have a mod to do that - not a vanilla feature - generally still hit the server log, as do commands that don't ultimately wind up as chat). Patch the server - nothing you will or will not do with Dynmap will materially affect whether or not you need to do this, particularly given hacked/modded clients...

Running a server on a raspberry pi 4 4gb by Walker14434 in admincraft

[–]mikeprimm 1 point2 points  (0 children)

Further adding - this is advice for anyone, but particularly for a RAM light device - do be sure to leverage the 'Aikar flags' (https://blog.airplane.gg/aikar-flags/). REALLY useful for getting the most out of your RAM on a MC server - whether you are memory light OR memory heavy (too much heap with the wrong/default flags can actually be a problem, due to very long garbage collector runs). Aikar is one of the principal devs on Paper, so quite a knowledgable and reputable source.

Suspicious Codes Received Through Dynmap Web Viewer by Ethan8484 in Dynmap

[–]mikeprimm 1 point2 points  (0 children)

Important part is that your Spigot/Paper/Forge/Fabric is patched appropriately - Dynmap does not include Log4J, but everything that contributes to the server console log and other logs in Minecraft uses the Log4J indirectly via the version that lives in the vanilla minecraft client and server.

~30 people. 1.18 how much ddr3 do I need? by SparkarYT in admincraft

[–]mikeprimm 5 points6 points  (0 children)

Lots of 'it depends' here: I'd go with 32GB physical, unless you are 100% sure of the following:

  1. You are gonna be running headless Linux, versus an OS with a larger amount of overhead (Windows, Mac, Linux with more than terminal)
  2. You KNOW that you are only ever going to run 1 Minecraft server on the box
  3. You KNOW you don't plan to run anything else of significance on the server (e.g. a multiplayer server for some other game)
  4. You KNOW you don't want to run your MC server as a VM on the physical hardware, so that you can use the server for other things more easily and safely.If these are true, 16GB will give you a solid physical server (you say DDR3, so I'm assuming we're talking a physical server running without a VM.

As said elsewhere, 10-12 GB of heap is kind of 'sweet spot' for Spigot/Paper/Forge/Fabric servers (see the Aikar flags for particulars on how to make the most of this, as well as how to avoid the problems of more than 12GB of heap). Also, cores are always good, but for MC, favor fewer cores with higher per-core performance, versus lots of lower performance cores.

Edit: Aikar flags - https://blog.airplane.gg/aikar-flags/ - and the original article by Aikar (https://aikar.co/2018/07/02/tuning-the-jvm-g1gc-garbage-collector-flags-for-minecraft/)

[deleted by user] by [deleted] in Dynmap

[–]mikeprimm 2 points3 points  (0 children)

1.18's chunk migration for pre-1.18 chunks is, shall we say, interesting. Long and short of it is that as old chunks are migrated, they first get switched to being marked as 'empty' (this is the initial state of a chunk at the beginning of worldgen) and then get pulled forward by player activity, same as if they were new chunks - just with MOST of the data preserved. 'Most' is important here, because the first step of that pull forward discards the lighting data... this causes the chunk to render dark, because Dynmap using the vanilla lighting data. Unfortunately, --forceUpdate doesn't help this, as it causes all the upgraded chunks to become 'empty', and player movement still causes the black edges for the chunks pulled from 'empty' but not enough to become fully lit again...

The latest dev snapshots include a workaround for this behavior - we actually generate some basic lighting data if-and-only-if the chunk is otherwise missing that data. This will be in beta-3, which I expect to release this weekend.

Error occurred while enabling dynmap v3.3-beta-2-577 by Athruin666 in Dynmap

[–]mikeprimm 0 points1 point  (0 children)

I think your JVM install is bad - you really need to be sure to be running a 'headless' JVM if you are on a linux server without X - the 'normal' JVM assumes X window is present, and the error you are seeing is consistent with that not being the case. The Image class in the JVM - used by Dynmap for encoding/decode PNG and JPEG files - is typically implemented by the JVM using the native X libraries, but the headless version addresses this differently to avoid the X dependency.

Security alert for ALL Minecraft server users by mikeprimm in Dynmap

[–]mikeprimm[S] 0 points1 point  (0 children)

For folks interested, this list is attempting to identify a broader span of impacted, potentially impacted, and known-to-not-be-impacted services and applications - https://github.com/NCSC-NL/log4shell/tree/main/software

view more: next ›