Pocketpair pushed v0.7.3 on April 6, and while it's a small patch by Palworld standards, it fixes two things that have been driving base builders and server admins quietly insane. If you run a dedicated server, here's what you need to know.
What changed
This is a bug-fix and balance patch. No new content, no new Pals, no sweeping mechanic overhauls. Two targeted fixes and some general construction polish.
Blueprints in chests now work for crafting. Prior to this patch, blueprints stored in base chests weren't recognized by the crafting system. You had to pull them out of the chest and into your inventory before the crafting bench would acknowledge they existed. It sounds minor, but if you've ever watched someone reorganize their entire storage system because they couldn't figure out why crafting wasn't working, you know this was a real friction point. Now the crafting system scans base chests automatically. Store your blueprints wherever you want.
Floating structures are gone. This is the bigger one for server admins. There was a bug where placing non-foundation structures – pillars, specifically – could leave roofs and other building pieces suspended in mid-air after the support was removed. People were using this (intentionally or not) to build structures that defied the game's support rules entirely. On a PvE server it was mostly cosmetic weirdness. On PvP servers it was being exploited for unreachable bases.
v0.7.3 enforces structural support rules properly. If a piece doesn't have valid support, it won't stay up. Existing floating structures in your world should collapse once the server updates and the affected chunks load in.
General construction stability improvements. Pocketpair's notes mention that "overall construction stability and usability have been refined," which is the kind of vague patch note that could mean anything from minor collision fixes to placement grid adjustments. In practice, building placement feels a bit more reliable – fewer cases where a wall segment refuses to snap where it obviously should.
How to update your server
If you're on LOW.MS, this is a one-click operation:
- Log into the control panel at control.low.ms
- Stop your server
- Hit Steam Update in the panel
- Start the server back up
The whole thing takes a couple of minutes. Your world save carries over without any manual intervention – this patch doesn't change the save format.
If you're self-hosting, update through SteamCMD the usual way. Make sure your server version matches your clients. Palworld isn't forgiving about version mismatches – players on v0.7.3 can't connect to a server still running v0.7.2, and the error message is an unhelpful "connection timed out" rather than anything that actually tells you it's a version problem. We've written about that specific headache before in our connection timeout troubleshooting guide.
Should you back up first?
Yes. Always yes. But especially this time, because the floating structure fix will cause some buildings to collapse retroactively. If anyone on your server was relying on the pillar exploit (or stumbled into it accidentally), their base is going to look different after the update. Having a pre-patch backup means you can at least show them what happened and help them rebuild.
On LOW.MS, cloud backups run automatically, so you've already got a snapshot from before the update. If you're self-hosting, grab a copy of your Pal/Saved/SaveGames/ directory before running the update.
Does this affect server settings?
No. v0.7.3 doesn't add, remove, or change any PalWorldSettings.ini parameters. Your existing config carries over as-is. If you've been running a tuned setup from our best server settings guide, nothing needs to change.
The bigger picture
v0.7.3 is a maintenance patch, and that's fine. Not every update needs to be a content drop. The blueprint-in-chests fix removes a genuine quality-of-life annoyance, and the structural integrity fix closes an exploit that was becoming a problem on competitive servers. Both are the kind of thing that makes the existing game better without adding complexity.
Pocketpair is still working toward the v1.0 full release sometime in 2026, and these incremental patches between major updates are a good sign that they're actually listening to bug reports rather than just pushing forward on new features. For server admins, small stable patches are always preferable to massive updates that break half your config.
Update your servers, warn your builders about the floating structure fix, and get back to catching Pals. If you're not running a server yet, plans are on our Palworld hosting page, and the getting started guide will have you up in a few minutes.