ignored-directories Setting

[ReaperSoulMate]

Expected behavior

Expected Behavior: The ignored-directories: [".paper-remapped"] setting in paper-global.yml should prevent Paper from scanning the plugins.paper-remapped\ directory for plugins, eliminating errors like java.lang.IllegalArgumentException: Directory 'plugins.paper-remapped\Expansion-advancements.jar' does not contain a paper-plugin.yml or plugin.yml!.

Observed/Actual behavior

Observed Behavior: Despite the correct configuration, Paper recreates the .paper-remapped\ directory during startup, remaps files (e.g., Expansion-advancements.jar, Expansion-vault.jar), and attempts to load them as plugins, causing log errors.

Steps/models to reproduce

Steps to Reproduce:
Set up a Paper 1.21.4 server with build #207.

Install PlaceholderAPI with expansions (e.g., Expansion-advancements.jar, Expansion-vault.jar) in plugins/PlaceholderAPI/expansions/.

Add plugin-loader: ignored-directories: [".paper-remapped"] to paper-global.yml.

Start the server, delete plugins.paper-remapped\ if it exists, and observe it being recreated with errors in latest.log.

Plugin and Datapack List

Paper Plugins (2):
CrazyCrates, EconomyShopGUI

Bukkit Plugins (56):
AdvancedEnchantments, AdvancedJobs, AdvancedPortals, AdvancedShops, AxTrade, BleepFishing, Bookshelf, Citizens, ClearLag, CommandAPI, CoreProtect, CustomCrops, DecentHolograms, DiscordSRV, Essentials, Fadah, GriefPrevention, GSit, GUIAdminTools, HoloMobHealth, InteractionVisualizer, InteractiveChat, IridiumSkyblock, ItemEdit, JumpPads, LFC, LuckPerms, mcMMO, mcMMO-placeholders, mcFeward, Multiverse-Core, Multiverse-Inventories, Multiverse-Portals, Nexo, NexoAddon, PlaceholderAPI, PlayerParticles, PlayerVaults, PlayerWarps, Polymart, ProtocolLib, TAB, TagsPlus, Vault, VotifierPlus, WorldBorder, WorldEdit, WorldEditSelectionVisualizer, WorldGuard, XGlow

There are 5 data packs enabled:
[vanilla (built-in)]
[file/bukkit (world)]
[paper (built-in)]
[file/nexo_custom_blocks (world)]
[file/nexo_music_discs (world)]

Paper version

Paper version 1.21.4-207-main@1a7288a (2025-03-09T18:15:59Z) Implementing API version 1.21.4-R0.1-SNAPSHOT

Other

latest.log

ignored-directories Setting in paper-global.yml Fails to Prevent Scanning of .paper-remapped Directory on Paper 1.21.4 Build #207

Description:
The ignored-directories setting in paper-global.yml does not prevent Paper from scanning the plugins.paper-remapped\ directory for plugins, resulting in errors when it attempts to load PlaceholderAPI expansions as plugins.

Expected Behavior:
The ignored-directories: [".paper-remapped"] setting should prevent Paper from scanning plugins.paper-remapped, eliminating errors like java.lang.IllegalArgumentException: Directory 'plugins.paper-remapped\Expansion-advancements.jar' does not contain a paper-plugin.yml or plugin.yml!.

Observed Behavior:
Paper recreates plugins.paper-remapped\ during startup, remaps PlaceholderAPI expansions (e.g., Expansion-advancements.jar, Expansion-vault.jar), and attempts to load them as plugins, causing errors in latest.log.

Steps to Reproduce:
Set up a Paper 1.21.4 server (build #207) on Windows 10.
Install PlaceholderAPI and Vault.
Place Expansion-advancements.jar and Expansion-vault.jar in plugins/PlaceholderAPI/expansions/.
Add to paper-global.yml:

[Malfrador]

Where are you getting that ignored-directories setting from? That is not something that exists at all, lol.

The remapper also won't deep-scan the plugin directory for .jars. So you probably just put the expansions into the /plugins/ directory accidentally.

[ReaperSoulMate]

ignored-directories was something I tried to setup with AI..aha....but when I moved the expansions from the plugins directory to expansions in the Placeholder API it would automatically make the same .Jar files in the plugins folder again and reproduce the same errors

[electronicboy]

ignored-directories is not a thing, and paper doesn't scan recursively, or inside of the remapped folder, for plugin jars; the remapper showing in the path is just a side-effect of how remapping works; if a jar is inside of the plugins folder, it will try to be loaded; as for what is going on with PAPI and that, you'd need to take that to them.