PMWA 3.0
- PMWA is now vastly more flexible/powerful! Two massive new features, and various other improvements.
- First, advancement-based triggers! You can now use any advancement from any mod to limit mob spawning! You can make it so that at least one player in the world must have completed a specific advancement in order for any given mob to be able to spawn. Simply use the advancement ID as the requirement, followed by a dash! (You can get the ID of an advancement from the /advancement command, advancements from mods work)
- And secondly, you can now trigger any commands upon mob activations, not just the default tellraw messages! Use a forward slash at the start of the “message” portion of the entry instead of a color or message, and it will treat it as a command… However, any double quotes (“) included in commands must be replaced by forward slashes (/) due to the config format unfortunately being unable to support inner double quotes. Here’s an example: Original command: /give @p minecraft:diamond_sword{display:{Name:"{"text":"Dragon's Fury"}"}} and modified command for PMWA to use it: /give @p minecraft:diamond_sword{display:{Name:/{/text/:/Diamonds/}/}}. This also means that forward slashes can’t be used in command messages.
- Added multiple extra options to the /pmwa command. One called “adapt_command”. This automatically converts a command to be usable by PMWA by replacing any double quotes with forward slashes, then giving you it in chat in a way that is copyable so that you can easily grab it for pasting straight into the config text file. Another new command option lets you subtract days: /pmwa day subtract (number of days to go back). So now to set to a specific day, the command is /pmwa day set (day to set to).
- Upgraded the clarity of the config file with line breaks and improved examples accounting for all the new features.
- Fixed an issue where distance messages could display repeatedly to all players and alternate in multiplayer.
- Improved function of the radius meter, now shows logged advancements and lets you know distance from x0 z0 just by holding it (hotter messages)
- Global toggle config option added to require a player source for mob kills to trigger kill-based activations.
PMWA 2.1
- New extremely useful feature added - control all mobs from an entire mod by just using the mod ID with a dash after the colon. More convenient than any other options I’m aware of for achieving this result. Used in a format like “modname:-,””,10” (this would disable all mobs from the “modname” mod until day 10)
- Added “never” condition for disabling mobs entirely without needing any condition where they’re able to spawn. Used in a format like “minecraft:zombie,””,never” (this would completely disable natural zombie spawning)
- When you sleep, it will now trigger the next day, as the next day now triggers at day tick 1 instead of the end of the previous day. This prevents players from skipping days by sleeping and delaying the progression indefinitely.
- Added bonus convenient “list” command that lists all stored data from the config file (chat messages only seen by player using the command)
- Improved meter item function
- Fixed issue where distance-based messages would sometimes not display.
PMWA 2.0 Added a new powerful feature that lets you limit mob spawning based on distance from the central world coordinates X=0, Z=0. Like with the other conditions, it can send you a chat message when you cross the spawning boundary (entering message and optional exit message, only visible to the individual player who crossed it). Added a creative mode item for viewing stored PMWA data regarding the current day, the mobs that have been registered as being killed (and as activating other mobs) Fixed an issue where mobs could potentially despawn on world load if they no longer meet the spawn requirements. Once mobs have spawned initially, they should now be unaffected by PMWA from then on (adds a PMWA Boolean NBT tag).