On this page
Key takeaways
5- Compare plugin requirements and supported Minecraft versions against the server you actually run.
- LocoPillars requires Paper 1.21+, WorldEdit or FAWE, and PlaceholderAPI 2.11+.
- FortunePillars offers four modes and arena auto-reset; Pillar Peril lists seven configurable modes and no dependencies.
- Choose an arena layout and starting pillar count to suit your intended player count, then test with a full group.
- Use the schematic file that matches your server version and test the paste in a backed-up area first.
This guide is for server owners who want to run a Pillars of Fortune or Lucky Pillars minigame. You will be able to compare several plugin routes, check the requirements that matter for your server version, and prepare an arena with a suitable pillar count. You can also paste a ready-made map using WorldEdit or FastAsyncWorldEdit.
Choose a plugin that fits your server
These plugins offer different setup styles and version ranges. Check the project page for the Minecraft version you run before installing, especially when the listed versions stop short of your server version.
| Plugin | What stands out | Check before choosing |
|---|---|---|
| LocoPillars | Editor wizard, multiple arenas, solo and team play, scriptable LuckyBlocks, cosmetics, achievements and stats. | Requires Paper 1.21+, WorldEdit or FAWE, and PlaceholderAPI 2.11+. Its listed game versions end at 26.1.2. |
| FortunePillars | Four modes, mode voting, cosmetics, stats, spectators and arenas that can reset automatically. | Lists Minecraft 1.21 to 1.21.11 on Paper and Folia. Its licence is All Rights Reserved. |
| Pillar Peril | Seven configurable modes and a queue system, with no dependencies listed. | Lists Paper and Purpur across 1.20.x, 1.21.x, 26.1.x and 26.2. |
| Pillars of Fortune+ | GUI arena editor, lobby platform and generated pillars with adjustable height and materials. | Its listing was last updated in December 2025 and lists versions up to 1.21.10. Check compatibility before using it. |
| Pillars of Fortune by Kammoun | Paid plugin listing with a public test server. | The listing says a licence key is obtained through its Discord. Try the test server before deciding. |
Check dependencies and version support
For LocoPillars, the required components are Paper 1.21 or newer, WorldEdit or FAWE, and PlaceholderAPI 2.11 or newer. TAB, ProtocolLib, Vault and ItemsAdder are optional. LocoPillars supports H2 by default and also lists MySQL, MariaDB and PostgreSQL databases.
FortunePillars lists Paper and Folia for Minecraft 1.21 through 1.21.11. Pillar Peril lists Paper and Purpur versions through 26.2 and does not list dependencies. Pillars of Fortune+ lists Paper and Spigot for 1.21.x, but its listed versions stop at 1.21.10. Treat each listing as the compatibility check for your exact server version.
To install a plugin, get its jar from the project page and place it in the server's plugins folder. Install the required dependencies listed for your chosen plugin too, then restart the server so it can load them.
Stop the server, upload the plugin jar and any required dependency jars into plugins/, then start the server again. Check the startup log for load errors.
Stop the server, use the File Manager or SFTP to upload the plugin jar and dependencies into plugins/, then start it from the Console. Check the Console for load errors.
Stop the server, upload the plugin jar and dependencies through Files / FTP into plugins/, then start it from the console. Check the console for load errors.
For a new server, follow our Paper setup guide first, then return to configure the game plugin.
Build an arena with the plugin editor
LocoPillars has a guided setup wizard: run /editor setup, then use /editor create <name> to create an arena. FortunePillars uses explicit arena commands: create one with /tof create <name>, set its two boundaries with /tof setpos <arena> 1 and /tof setpos <arena> 2, then set cage positions with /tof setcage <arena> 1 through 8. Add a spectator spawn, save the arena with /tof save <arena>, and test it with /tof join <arena>.
Pillar Peril is configured and operated differently: its listing documents commands such as /game start, /queue join and /pp-config. Read the project instructions for the command arguments and mode settings before opening a match.
Decide on the arena footprint and pillar layout before building. A compact layout can bring players into contact sooner, while a larger layout leaves more room between starting positions. Match the number of starting positions to the player count you intend to support, and test the layout with a full group before launch.
Paste a schematic when you want a ready-made map
Our team made Pillars of Fortune Arenas | x4 Maps, a build pack rather than a minigame plugin. It includes Dark, Bamboo, Pink and Nether arenas with 8, 12, 12 and 16 pillars respectively. The schematics are native to 1.21.11, with converted files listed for 1.8 through 1.21+. The pack requires WorldEdit or FAWE.
Download the schematic that matches your server version from the folder for the arena you want. Upload it to the WorldEdit or FAWE schematics folder, load it, stand at the intended paste location, and paste it. Our schematic guide explains the upload, paste and undo workflow.
Stop the server before changing the world. Upload the schematic to the WorldEdit or FAWE schematics folder, start the server, then run the commands below in game as an operator.
Stop the server and upload the schematic with the File Manager or SFTP to the WorldEdit or FAWE schematics folder. Start the server, then run the commands below in game as an operator.
Stop the server and upload the schematic through Files / FTP to the WorldEdit or FAWE schematics folder. Start the server, then run the commands below in game as an operator.
//schem load <name>
//pasteUse the schematic's name in place of <name>. Paste into a test world or a backed-up area first, and check orientation and clearance before opening the arena. See our backup guide if you need a restore plan.
Test a full match before opening the server
Join with the same permissions and player flow your community will use. Check that cages, spawn points, spectator access, loot timing and arena reset behave as expected. FortunePillars documents player commands including /tof join, /tof leave, /tof vote, /tof stats and /tof cosmetics. LocoPillars documents player commands for joining, stats, cosmetics, achievements and team chat.
Our team also makes Lucky Pillars Setup | Modern Series, a ready-to-use setup built around Pillars of Fortune with a modern minigame style. Its listing offers a free test server. The listing does not state its plugin list or requirements, so check those details before planning an install.
Keep the server online during scheduled matches so players can join when the round starts.
Partner Need a server? Use code ARROWTAN for 15% off at iTitan.
Frequently asked questions
How do I make a Lucky Pillars Minecraft server?
Choose a plugin whose listed server software and Minecraft versions match your server. Install the plugin and required dependencies, configure its arena or editor, then test a complete match before opening it to players.
Does LocoPillars need WorldEdit?
LocoPillars requires WorldEdit or FastAsyncWorldEdit, as well as Paper 1.21+ and PlaceholderAPI 2.11+. Its listing also names TAB, ProtocolLib, Vault and ItemsAdder as optional.
Which Pillars of Fortune plugin supports my Minecraft version?
Check the plugin's project page for your exact Minecraft version and server software. The listed ranges differ: for example, FortunePillars lists 1.21 to 1.21.11, while Pillar Peril lists versions through 26.2.
How many pillars should a Pillars of Fortune arena have?
Choose a starting layout based on the player count and space you want between players, then test it with a full group. The arena pack from our team includes layouts with 8, 12 and 16 pillars.
How do I install a Pillars of Fortune arena schematic?
Upload the schematic that matches your server version to the WorldEdit or FAWE schematics folder. Load it with //schem load , stand where it should go, and run //paste. Test in a backed-up area first.
