Land Manager Keeps Growing

Hey everyone,

Over the past week I have been spending a lot of time improving the Land Manager and honestly this update became much bigger than I originally expected.

What started as a small automation helper for my own land slowly started evolving into a more complete management tool. The funny part is that while building all of this I noticed how differently people actually play land.

Recently there was a pretty interesting discussion in the team possible chat and afterwards I also reached out to @azircon to hear how he would personally use a system like this. That conversation honestly opened my eyes a bit because his approach to land management was completely different from mine.

Where I mostly focus on automation convenience and keeping things manageable especially on harvesting resource, larger stakeholders think far more about scale getting land quickly up and running, long term optimization and sustainability.

That actually made me rethink parts of the fee structure because with very large land operations.

Do not want to read any further you can check out the new features here:
https://land.spl-stats.com/land-manager

And that brings us directly into probably the most important change of this update.

Daily Harvest Fee Caps

Originally the Land Manager simply used a flat 2% fee on harvested resources.

For smaller and medium setups that worked perfectly fine and honestly still does. But once I started looking at how larger stakeholders might use the system, things became a little uncomfortable.

In some situations a massive harvest operation could potentially result in over 200K resources being paid as fees and that is absolutely not what I want this project to become.

I want the tool to stay fair and sustainable not punish players for scaling up their land operations.

So daily fee caps are now enforced account-wide.

These caps apply cumulatively across:

• Regions
• Castles
• Keeps

Here are the current limits:

Resource	Daily Max Fee
Grain	40,000
Wood	10,000
Stone	4,000
Iron	1,000

The ratios follow the in-game values:

• 1 Iron = 40 Grain
• 1 Stone = 10 Grain
• 1 Wood = 4 Grain

The system checks today's already-paid fees before every harvest run and even dry runs now fully reflect the cap before execution.

This creates a much more predictable and fair system especially for players operating larger land setups.

It also helps protect my infrastructure a bit.

Honestly I would still recommend harvesting once or maybe twice per week. You can harvest more often but because of the fee structure it becomes less beneficial anyway and only creates more unnecessary server load.

So this approach feels like a pretty healthy middle ground for everyone involved.

Let me know what you think of this new fee structure, to high to low other ideas all are welcome!

🙌 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.

Harvest And Rental Split Apart

One thing became very obvious while adding more and more features.

The Land Manager interface was slowly becoming overloaded.

Harvesting and renting are completely different workflows yet they were sharing the same space which became increasingly messy especially for larger accounts.

So the interface is now split into two dedicated tabs.

Harvest Tab

Focused on:

• Bulk harvest operations
• Alerts
• Mythic overview
• Per-region harvesting status

Rental Tab

Focused on:

• Rental authority status
• Rental bulk actions
• Rental plot overview

Both tabs still share the same top section so important information like config access, Region Resource Summary and the Today panel always stay visible.

This change alone already makes the entire system feel far cleaner and easier to navigate.

Power Core Staking Directly From Rental Overview

One annoying issue with larger land setups is noticing when plots are not powered, find the plot power it up and go back to my side this now can be done directly.

So unpowered plots inside the Rental Overview now include a direct Stake Power Core action.

The process:

• Loads available Power Cores automatically
• Fetches grouped inventory counts
• Retrieves available Power Core IDs
• Broadcasts staking transactions through Hive Keychain
• Waits for blockchain confirmation before refreshing

The nice part is that this entire flow works through posting-key operations which keeps things much safer and easier to use.

Automatic Rental Renewals Before Season End

This is probably the biggest quality of life feature in the update.

Managing expiring rentals near season end quickly becomes painful once land operations start scaling up.

The new Renew Rentals button inside the Bulk Action Panel now helps automate that process.

The system:

• Detects rentals nearing season end
• Refreshes collection data before renewal
• Calculates only the required extension days
• Skips already renewed cards
• Skips cancelled rentals
• Skips invalid market entries

Before confirming you get a full overview showing:

• Card owner
• DEC/day cost
• Extend days
• Total DEC required
• Current rental end
• Assigned plot

There is also a balance verification before transactions are broadcasted.

To stay within Hive limits renewals are processed in batches of 4 transactions per block while waiting for blockchain confirmations between batches.

I tried to make this behave more like a careful human instead of blindly renewing everything automatically.

Do note this still requires the active key because market operations are involved.

SPS Fee Removed

Another important improvement is that SPS harvesting no longer has service fees attached.

Only natural resources are now part of the fee structure:

• Grain
• Wood
• Stone
• Iron

This also removes the active-key Keychain prompt that SPS fee transfers previously required.

So SPS harvesting now stays fully within posting-key permissions which makes the entire process smoother and significantly safer.

Performance And Stability Improvements

Besides the bigger features there were also many improvements focused on handling larger operations more smoothly.

Rent Worker Dialog Improvements

Dry Run and Confirm dialogs now use paginated tables with 20 rows per page which makes huge rental operations much easier to navigate.

A shared RentalPlotTable component was also extracted to improve maintainability and flexibility.

Transaction Polling Improvements

Large rental runs could sometimes overload transaction lookups.

The polling system now uses pLimit(5) to avoid flooding transaction requests during massive batches.

Additional Fixes

Also included:

• DEC balance check fixes
• Plot overview pagination
• General Rent Worker stability improvements

A lot of these changes are not flashy visually but become extremely important once people start operating larger land setups.

Still Experimental But Slowly Becoming Something Bigger

I still consider the Land Manager experimental.

There are simply too many edge cases on land to pretend everything is solved already and I fully expect there will still be situations that need adjustments or improvements.

But I do feel the project is slowly evolving from a small automation helper into a much more complete land management suite.

And honestly the conversations with other players especially larger stakeholders have been incredibly valuable because they force me to think differently about scaling, fairness and usability.

As always feedback is super important especially from people running bigger land operations because those setups usually expose edge cases the fastest.

For now I hope these improvements make land management a little less painful and a lot more enjoyable.

---

One question for the community:

I’m still debating whether I should introduce a limit on the number of plots the rental automation can rent in a single run. Right now, the system simply rents as many suitable cards as it can find.

Potential limits could be something like:
* 10 plots
* 20 plots
* 100 plots
* or leaving it completely unlimited (with risks market not deep enough to rent)

The main reason I’m considering this is because searching the market and finding the best rental deals may become a bottleneck at larger scales, both in terms of performance and overall efficiency.

It’s difficult for me to properly simulate these large-scale scenarios on my own, so feedback from bigger land owners would really help here.

Would you prefer:
* unlimited rentals
* or a configurable limit for better performance/stability?

Curious to hear what people think, especially those managing larger land setups that are into renting.

---

Until next time,

Beaker
See you on your land journey or on the battlefield 😄

Want to be part of this amazing play-to-earn game? Consider using my referral link!