Land Manager Update: Bulk Worksite Actions & Smarter Pool Top-Ups

Welcome to another Land Manager release!
This week we have some Worksite improvements, bulk actions, visual fixes and one major update to the Top Up Pools strategy.
But first, a small story from last week.
Sometimes you hop into Discord just to talk a bit about Splinterlands, and suddenly you have several large landowners in the same room. Last week we had people like @leveluplifeph (Splinterlands guy), @azircon / @jeffopenscards and @lunacysystem all chatting about land.
For me these discussions are super useful. I currently have 63 plots, which already gives me plenty of things to manage, but hearing about the problems people run into when managing hundreds/thousand plots gives me a completely different perspective.
And one thing became very clear:
Bulk actions matter. A lot. 🤣
So that became one of the focuses for this release.
🙌 Support the Project
✅ Upvote this post – it really helps!
👉 Vote for My SPS Validator Node
💬 Ideas and feature requests are always welcome. No promises but I will take a look and try my best.
Bulk Actions for Worksites
A while ago I introduced the Worksites tab inside the Land Manager.

At the time I thought the individual actions were probably good enough. After all, you normally construct a building once, feed the workers and then you probably do not change 50 worksites at the same time.
A few extra clicks, right?
Then I saw @azircon's screen.
Okay...
I understand the request for bulk buttons now. 🤣
So this week the Worksites tab received proper bulk actions.
You can now select plots using the existing filters and perform actions on everything currently selected.
The available bulk actions are:
- Feed Workers
- Fix Grain Deficit
- Change Worksite
The buttons also show exactly how many plots can use that action.
For example:
Feed Workers (8)
or:
Logging Camp (12)
This means you can filter down to exactly the plots you want and immediately see what actions are available for that selection.

Feed 100 Plots at Once?
There is one small problem with developing features for giant landowners.
I am not one.🤣
I could test the new bulk actions with two plots. I even changed the buildings on them just for testing purposes.
So everything works nicely with my two plots...


Now I am curious what happens when somebody hits Feed Workers on 100 plots at once.
The operations are packed into as few transactions as possible, and the grain calculations are handled per region. If a region cannot afford to feed every selected worksite, the ones that can be fed are still processed.
So in theory we are ready.
Now I need you crazy land barons to put it through some real world testing.
If you run a large bulk action, definitely let me know how it goes.
Plan First, Execute Second
The Fix Grain Deficit bulk action also uses the same planning flow as the single plot version.

Before anything is broadcast, the Land Manager calculates the complete plan.
You can review the regional breakdown and operation log before confirming anything.
This is especially important when multiple regions are involved. The planner calculates all affected regions together, making sure donor resources, DEC balances and liquidity are not accidentally allocated twice.
Only after you confirm the plan are the transactions sent.
Smarter Top Up Pools Strategy
Now for the change I am personally most excited about this week.
Last week I released the Top Up Pools strategy.
I really like the idea behind it. Build enough resources into the pools, keep topping them up and eventually have a pipeline where resources can be withdrawn without worrying about the 30 day lock.
But something was bugging me.
The calculated deposits were simply way too high.
The strategy was safe, but too conservative.
So I sat down again this week and changed how the required resources are calculated.
And in my own situation, the difference is massive.
The Old Calculation
Previously the calculation basically asked:
How much resource will my regions consume this week?
It took the complete weekly consumption and added a 10% safety margin.
For my account that resulted in:
| Resource | Old weekly target |
|---|---|
| GRAIN | 816,923 |
| WOOD | 21,067 |
| STONE | 8,427 |
| IRON | 2,107 |

For GRAIN alone, that meant depositing more than 816K GRAIN into the pools.
That required roughly 6,676 DEC for the actual pool additions.
Safe?
Sure.
Efficient?
Not really. 🤣
The problem is that my regions are producing resources themselves.
Why should the pool provide 100% of the consumption when the region already produces a large part of what it needs?
The New Calculation
The new strategy asks a different question:
How much of the consumption does each region actually need from outside?
The calculation is now:
External need = max(0, consumed per hour minus produced per hour)
This calculation happens per region and per resource.
That last part is important.
If Region A produces a massive WOOD surplus, that does not magically solve a WOOD shortage in Region B.
First we calculate the external need for every individual region.
Only after that are those deficits combined.
Then the weekly pool target becomes:
Weekly external need × 110%
The 10% safety margin is still there.
The 30 day vesting and withdrawal logic also remains unchanged.
We are simply calculating much more accurately how many resources actually need to enter the pool.

A Simple Regional Example
One region from the calculation makes this pretty easy to see.
Region 81 consumes:
481.875 GRAIN/hr
But it also produces:
359.370 GRAIN/hr
So the pool does not need to cover 481.875 GRAIN every hour.
The actual external requirement is only:
122.505 GRAIN/hr
That changes the weekly requirement from roughly 81K GRAIN to around 20.6K GRAIN before the safety margin.
Apply that same logic across every region and suddenly the pool requirements start looking very different.
My GRAIN Requirement Dropped by Around 60%
Across my regions I currently have:
- Consumed: 4,420.578 GRAIN/hr
- Produced: 4,342.064 GRAIN/hr
- Gross weekly consumption: 742,657 GRAIN
- Actual weekly external need: 296,223 GRAIN
- Target including the 10% margin: 325,846 GRAIN
So my weekly GRAIN target changed from:
816,923 → 325,846 GRAIN
That is roughly a 60% reduction.
And instead of around 6,676 DEC for the pool additions, it drops to approximately 2,663 DEC.
Now we're talking. 🤣
WOOD Is an Even Better Example
WOOD shows perfectly why the new calculation needs to happen per region.
Across my regions the totals are:
- Consumed: 114 WOOD/hr
- Produced: 755.621 WOOD/hr
And more importantly, none of the individual regions have a WOOD deficit that needs to be funded.
So the old strategy said:
Deposit 21,067 WOOD
The new strategy says:
Deposit 0 WOOD
Makes much more sense.
The regions already produce everything they need, so there is no reason to unnecessarily put more WOOD into the pools.
STONE and IRON Improve Too
The same calculation applies to the other resources.
STONE changes from:
8,427 → 2,772 STONE
IRON changes from:
2,107 → 693 IRON
Put everything together and this is the difference for my account:
| Resource | Before | After | Reduction |
|---|---|---|---|
| GRAIN | 816,923 | 325,846 | ~60% |
| WOOD | 21,067 | 0 | 100% |
| STONE | 8,427 | 2,772 | ~67% |
| IRON | 2,107 | 693 | ~67% |
That is a pretty significant difference.
More Details in the Plan
Because the calculation became smarter, I also wanted the plan to explain why it wants a certain amount.
For every resource you can now see:
- Consumed per hour
- Produced per hour
- External need per hour
- Gross weekly consumption
- Actual weekly pool target
If your regions completely produce a resource themselves, the resource is skipped and the plan tells you why.
The low pool buffer alert has also been updated. It now compares your reserves against the weekly external need instead of gross consumption.
So all parts of the Top Up Pools strategy now use the same logic.

Why I Think This Is Much Better
The important part is not simply that the new strategy deposits fewer resources.
It is that the calculation now better represents what I actually want these pools to do.
The old strategy asked:
How much will my regions consume?
The new strategy asks:
How much of that consumption do my regions actually need to import?
That sounds like a small distinction, but as you can see from my numbers it makes a huge difference.
The goal is still to build that 30 day pipeline and keep enough resources inside the pools so they can eventually be withdrawn without penalties.
But I do not want to unnecessarily lock hundreds of thousands of resources and extra DEC in liquidity to achieve that.
I think this new calculation gets much closer to that goal.
As Always, I Need Your Feedback
Especially with these bulk actions and the Top Up Pools strategy, there are situations I simply cannot reproduce with my own land.
I can test feeding two plots.
Some of you can test feeding half of Praetoria. 🤣
So if you are using the bulk actions on large selections, let me know how they behave.
The same goes for the new pool calculations. I will be monitoring my own numbers over the coming weeks, but if you see something that looks wrong for your regions, send it my way.
Every discussion, bug report and feature request helps me understand how people actually manage their land and keeps improving the Land Manager.
See you in the next release!
Beaker signing off.

Want to be part of this amazing play-to-earn game? Consider using my referral link!
this looks like powerful work mr.beak
Well thank you 😍
Nice update! 👍 Bulk worksite actions and smarter pool top-ups sound like useful improvements, especially for making everyday management quicker and easier. Looking forward to trying out the new features! 🚀
Thanks let me know if you have questions!
Thanks for sharing! - @azircon
