Skip to content

Palvolve 1.8.0

Choose a tag to compare

View all tags
@DooDesch DooDesch released this 13 Aug 12:24
· 2 commits to main since this release
v1.8.0
f55e90c

Twenty settings used to live in a file every update overwrites. Now they sit in your own config, and the website shows all of them.

Added

  • Your config_user.lua can now set twenty settings it could only read about before. The animation timings, the finale style, the multiplayer request limits, the talent bonus per stage, how many stones an evolution costs, which key confirms. All of it used to mean editing scripts\config.lua, which the next mod update overwrites. The website writes them and config_user.lua carries them through updates.

  • Every setting is on the website, grouped and searchable. palvolve.doodesch.de/simple keeps the four quick switches at the top and puts the full list under them, with a search box, a running list of what you changed, and a reset for each value.

  • Each setting says which file it belongs in. "Server file" or "Player file", and for the ones the host hands to its players, that too. Guessing which half of a dedicated setup a value belongs to was the most common way to set it in the wrong place.

  • You can load your running config back into the website. Drop your config_user.lua on the quick setup page, change the two values you came for, download it again. Your tree and every other setting survive the trip.

  • The settings you changed copy out as text. One block for a Discord thread or a ticket, with both the readable name and the line to put in the file.

  • A server decides how an evolution looks, not each player. The five sequence timings, the top spin speed, the element colours and the finale style now travel to a client with the tree, the way the costs and the stone rule already did. What stays with the player: the confirm key and its timings, the effect budget, and the diagnostics. Leaving the server gives all of it back.

  • A config dropped next to the mod moves itself somewhere an update cannot reach. The mod's own scripts\ folder is the one people find on their own, and the one a mod update replaces. A config_user.lua left there is now moved to %LocalAppData%\Pal\Saved\Palvolve\, or on a server to <server>\Pal\Saved\Palvolve\, and a note stays behind saying where it went. A config already at that path is kept as config_user.lua.bak.

  • A value the mod cannot use says so in the log. A number outside its range names the range and what it was read as, an unknown chatMessages or confirmKey lists what is accepted. Values used to be corrected in silence.

Fixed

  • unlockCatchTech = false in a user config did nothing. The README has described that switch since 1.4.0, but the loader never read it. The only way to get the vanilla rule back was editing the mod's own copy, which every update replaced.
  • An unknown confirmKey took the whole key binding down with it. A key name UE4SS does not know reached the binding as an empty value. The config now accepts sixteen keys and says so in the log when it rejects one. The binding checks the name before it registers.

Build your tree: https://palvolve.doodesch.de
Uninstall guide: https://github.com/DooDesch-Mods/Palworld-Palvolve/blob/main/UNINSTALL.md

Assets 4
Loading