Yamipa: Display Custom Images in Minecraft Without Client Mods
Imagine walking through your Minecraft server and seeing a massive, animated GIF plastered on a wall — a piece of art, a server logo, or even a meme — all without requiring players to install any extra mods. That is exactly what Yamipa delivers. This Spigot plugin is a game-changer for server owners who want to add visual flair, create custom map art, or build interactive galleries without the usual hassle of resource packs or client-side modifications.
What Is Yamipa and How Does It Work?
Yamipa is a lightweight Spigot/PaperMC plugin that allows you to place image files — including animated GIFs — directly onto any surface in your Minecraft world. It achieves this by cleverly using two vanilla features: item frames and maps. However, unlike traditional map art, Yamipa does not actually spawn item frame entities. Instead, it sends custom network packets to players’ clients, making them see a placed image where there is none. This approach drastically reduces server lag because no real entities are created or tracked.
For animated images, Yamipa pre-caches all frames and then sends tiny packets to cycle through them, creating smooth animations. The result is a seamless, high-performance way to decorate your server with custom visuals that every player can see, regardless of their installed mods.
Installation and Requirements
Setting up Yamipa is straightforward. Download the latest JAR file from the official release page and place it into your server’s plugins directory, just like any other Spigot plugin. After a restart, the plugin will generate its default configuration and you’re ready to go. For those managing a modded server, you might also appreciate that Yamipa can be easily installed via the foxygame.net launcher — a convenient, flexible, and modern Minecraft launcher that lets you download plugins right from the menu, streamlining your server setup process.
Before installing, ensure your server meets these requirements:
- Server software: Spigot, PaperMC, Purpur, or Folia (1.16.x through 1.21.x).
- ProtocolLib v5.3.0 or higher must be installed as a dependency.
Yamipa is compatible with a wide range of Minecraft versions, as shown in the table below:
| Minecraft Version | Spigot | PaperMC | Purpur | Folia |
|---|---|---|---|---|
| 1.16.x | Yes | Yes | Yes | No |
| 1.17 – 1.17.1 | Yes | Yes | Yes | No |
| 1.18 – 1.18.x | Yes | Yes | Yes | No |
| 1.19 – 1.19.x | Yes | Yes | Yes | No |
| 1.20 – 1.20.x | Yes | Yes | Yes | Yes |
| 1.21 – 1.21.x | Yes | Yes | Yes | Yes |
Configuration Made Simple
Yamipa works out of the box with sensible defaults. Upon first run, it creates a plugins/YamipaPlugin folder containing:
- cache/ – stores cached image data for faster rendering (do not modify).
- images/ – the directory where you place the image files you want to use.
- images.dat – a database file tracking all placed images and their coordinates (do not modify).
You can customize paths and behavior by creating a config.yml file. The default settings are:
verbose: false– set to true for detailed logging.animate-images: true– disable to prevent GIFs from playing.images-path: images– relative path to your image folder.cache-path: cache– path to the cache directory.data-path: images.dat– path to the placed images database.allowed-paths: null– a regex to restrict which image files players can access.max-image-dimension: 30– maximum width or height in blocks for any image.
Restricting Access with Allowed Paths
The allowed-paths option uses Java regular expressions to control which images a player can see or download. You can use special tokens like #player# (player name) and #uuid# (player UUID) to create private directories. For example, setting allowed-paths: ^(private/#player#|public)/ ensures that player "john" can only access images under private/john/ and the shared public/ folder. This restriction also applies to non-player entities like command blocks, but the tokens will match any string in those contexts.
Commands and Usage
Yamipa adds a comprehensive set of commands under the /image base. Here are the most important ones:
- /image download <url> <filename> – download an image from a URL directly into the images directory.
- /image list [page] – browse all available image files.
- /image place <filename> <w> [h] [flags] – start an interactive UI to place an image of a given width (and optional height).
- /image place-at <x y z world> <face> <filename> <w> [h] [flags] – place an image at exact coordinates without player interaction.
- /image give <player> <filename> <amount> <w> [h] [flags] – give a player image items they can place later.
- /image remove – start UI to remove a placed image.
- /image remove-at <x y z world> <face> – remove an image at specific coordinates.
- /image clear <x z world> <r> [placed-by] – remove all images in a radius, optionally filtering by the placer.
- /image describe – show details about a placed image.
- /image top – list players with the most placed images.
For example, to place a 3-block-wide image named "logo.jpg" that glows in the dark, you would use /image place "logo.jpg" 3 2 +GLOW. To give a player 10 removable image items of a 3x5 picture, run /image give TestPlayer "test.jpg" 10 3 5.
Permissions and Player Variables
Yamipa uses a tree-based permission system. By default, only operators can use administrative commands, while all players can place and remove image items. Key permissions include:
yamipa.command.place– use the /image place command.yamipa.command.give– give image items to others.yamipa.item.place– place image items (granted to everyone by default).yamipa.item.remove.own– remove only your own images.
You can fine-tune access with permission plugins like LuckPerms or GroupManager. Additionally, Yamipa supports player variables — key-value pairs that override global settings for specific players or groups. For instance, to limit a player named "test" to 5x5 images, you would set the variable yamipa-max-image-dimension to 5 via your permission plugin.
Protection Plugin Compatibility
On large servers, you likely use region protection plugins. Yamipa automatically respects the rules of WorldGuard and GriefPrevention. Players can only place or remove images in areas where they have build permissions, with no extra configuration needed.
Image Flags for Fine Control
Every placed image can have boolean flags that modify its behavior. The available flags are:
- ANIM – enables animation (on by default for GIFs).
- REMO – allows any player to remove the image by left-clicking.
- DROP – makes the image drop an item when removed.
- GLOW – makes the image glow in the dark (Minecraft 1.17+).
You can add or remove flags using +FLAG or -FLAG syntax. For example, +GLOW,-ANIM creates a static glowing image. Default flags for /image place are only ANIM, while /image give items default to ANIM, REMO, DROP.
Performance and Memory Considerations
Because Yamipa caches image data in memory when players are nearby, your server needs a bit of spare RAM. A good rule of thumb is about 100 KB per unique loaded image, or 1 MB for animated ones. If the same image is placed multiple times with identical dimensions, it counts as a single instance, keeping memory usage efficient. The plugin also uses bStats for anonymous usage reporting, which you can disable in the bStats config if desired.
Conclusion
Yamipa is an incredibly versatile tool for any Minecraft server owner who wants to enrich their world with custom visuals. Its no-client-mod approach, low performance footprint, and deep integration with protection plugins make it a safe choice even for large public servers. Whether you’re building an art gallery, displaying server rules, or just having fun with animated memes, Yamipa gives you the power to turn any surface into a canvas. With straightforward commands, flexible permissions, and player-specific variables, you can tailor the experience exactly to your community’s needs. Give it a try and watch your server’s creativity come to life — one block at a time.