v2.1.0

Fixed some bugs:

• 'images' folder is now reliably created (again)
• no longer throws rendering errors upon creating new map

v2.0.2

Fixed some bugs:

• image folder is now reliably created
• data.yml is now only deleted if all image files have been updated successfully

v2.0.0

Rewrote backend

3 years ago when i initially wrote this plugin, I had no sense of what good code was whatsoever

This overhaul is to remedy that, here are some things that are new:

- no more data.yml
Minecraft maps are stored via their 'id' (which is the number you see when you hover over the map item). Prior to this update, a data.yml file was created to store each id managed by the plugin and the file path to its corresponding image. This was just straight up bad... for one you couldn't move the server to another part on the computer without manually updating the file paths.. secondly, it's just dumb, you can easily store the id in the file name
Thank you to SlyCedix for pointing this out to me

- optimized image storage
Maps in Minecraft are always rendered at a resolution of 128x128, hence making it pointless to store any image of higher res to that. Hopefully this change can reduce the storage requirement by a good amount

Many things have changed on the backend and hopefully it should lead to a more optimized experience overall (at least a little bit)

v4.9

Item frames, very cool

You can now specify in the command whether or not you want to receive Item Frames (or Glow Item Frames) along with your maps.

This can be disabled in the config (for specifically Item Frames or Glow Item Frames) and access can also be limited through permissions (also on a per Frame type basis.)

These are the useless things I do when I get too much time to myself..

Permission Nodes:

imagemaprenderer.map

description: allows player to run the /map command
default: true

imagemaprenderer.itemFrames

description: allows player to receive Item Frames when they render map(s)
default: true

imagemaprenderer.glowItemFrames

description: allows player to receive Glow Item Frames when they render map(s)
default: true

v4.8

Added support for perms cause I'm cool and people use my plugin

Cool new feature.. you no longer have to decompile, change the code, do it wrong, ask ChatGPT to do it for you, then recompile the plugin to edit who can perform the map command.

Using a permission manager plugin or smth (idfk how it works I'm not a good server host), you can change who has permission to the /map command.

ig this means at some point I need documentation but for right now, the node is right here:

imagemaprenderer.map:

description: allows player to run the /map command
default: true

v4.7

"Minor bug fixes" -every developer ever when changing the entire underlying framework

jkjk, actual bug fixes

-You now do not break everything when running the "map" command from a console
-When rendering an image onto a grid of more than 1 map, it will only send the confirmation message once (instead of per every map rendered)

Of course if you find any bugs and/or want something added, let me know and I'll try

v4.5

There is now an option in config.yml called "giveItemFrames" that when set to true, will give the player who runs the command the same amount of item frames as maps given

v4.4

Bug Fixes:
-Added proper size limitations for map dimensions that are calculated

-Added proper error messages for maps commands that use a "~" for requesting too large of maps

v4.3

This release offers the ability to use a "~" in place of either of the width or height parameters and have the plugin calculate the optimal opposite dimension.

When ~ is used in replace of a width (args[0]) or height(args[1]) parameter, it will use the other integer given to calculate the optimal opposite dimension for the given image.

Example:
/map ~ 3
When the URL leads to a 1200x900 image, the plugin will calculate the optimal number of maps wide it should be and output a 4x3 array of maps

v4.2

Current working version of this project