- Plan the amount the recipient will receive after Trading Post tax, not just the amount you send.
- Split large requests according to shipment capacity and when the player will actually use the resources.
- Treat a guild bank as a player-managed arrangement with clear rules, not a protected game feature.
CONTENTS
Before KvK, a guild member needs resources to finish healing. They post the request in chat, and three players offer to help. If everyone sends resources at once without checking the amount, the recipient may end up with more exposed stock than they need. The total sent by donors may also differ from the amount the recipient receives.
The key to guild resource transfers in Lords Mobile is not gathering more. It is getting the right resource to the right player close to the time they will use it. Account for Trading Post tax, shipment limits, and the recipient’s safety together, and you can reduce waste and cut unnecessary chat during a fight.
Get the net requirement first
“I need resources” is not a shipment instruction. Ask the recipient for the resource type, the amount they are short, and its purpose: healing, training, or research? They should also count their exposed stock and the resources they are willing to open from their bags. That way, the guild does not resend what the player can already cover.
Suppose a player hypothetically needs 8 million ore for healing. If they have 3 million ore in exposed stock and can open another 2 million from bags, the request should be for 3 million net ore, not 8 million. Opening bag resources only when needed is more controlled than leaving them exposed in a castle for hours. We cover that distinction in the resource reserve guide.
R4/R5 can use a simple request format: “Resource type — net amount needed — purpose — time I’ll be ready to use it.” If the player cannot get back online yet, agree on a time rather than sending immediately. That matters when the resources would otherwise sit exposed in their castle.
Four questions before shipping
- Which resource does the recipient need, and how much net?
- Do they have usable resources in bags or exposed stock?
- What action will they use the resources for?
- When can they start that action?
Calculate tax and shipment capacity
Do not confuse the amount you send through the Trading Post with the amount the recipient receives. Check the tax and capacity shown on the in-game sending screen, then work backward from the net amount the recipient needs. The rates below are examples, not the current values on your account.
Say the screen shows 10% tax. In this example, sending 10 million delivers 9 million. If the recipient needs 9 million, the calculation is straightforward. If they need 10 million net, sending 10 million is not enough. Adjust the shipment until the screen shows that the recipient will receive 10 million. Let the game interface settle any rounding or other conditions.
Check capacity at the same time. If the hypothetical per-shipment limit is 2 million, you cannot send a total of 10 million in one transaction; you need to plan at least five shipments. Before sending all five back-to-back, ask whether the recipient is online and will start using the first delivery. For urgent healing, getting the right resource there first matters more than the size of the total shipment.
Example shipment calculation
| Hypothetical condition | Planning outcome |
|---|---|
| Send 10 million with 10% tax | The recipient gets about 9 million; confirm the net amount on the game screen. |
| 2 million per-shipment limit | Plan at least five shipments to send a total of 10 million. |
Set limits for the guild bank
What players call a “guild bank” is, in practice, resources held for the guild in a member’s castle. It is not a separate, automatically protected guild account. That castle’s shield can expire, its owner can go offline, or they may be unable to distribute the resources. Concentrating everything in one castle is not always a sound economy plan.
If three members are contributing resources for an upcoming fight, name one distribution coordinator and one backup first. Limit the bank’s stock to what will actually be used in the next distribution. Where possible, resources whose recipients are not ready should remain in the donors’ bags. Keep a brief guild record of what each reserve is for; do not spend healing stock on something else.
Consider the shield and when the player will return. A shield does not provide indefinite safety; once it expires, exposed stock in the castle is at risk. If you can send directly to the player who needs the resources instead of parking them in a bank, you also avoid the tax and coordination involved in an extra transfer.
A bank is not automatic protection
A castle used as a guild bank still belongs to a player. Consider its shield duration, whether the distribution coordinator is available, and how much exposed stock is waiting there.
Split shipments by order of use
Imagine two players request resources at the same time: one is ready to heal after a fight, while the other will finish research in the evening. Sending both equal amounts immediately may look fair. But the second player’s resources could sit exposed for hours while the first delays healing because they are still short. Prioritize when each player will actually use the resources, not their rank.
For a large request, send enough to start the action, then confirm what remains. In a hypothetical 6 million request, the recipient might open bag resources or change plans after the first 2 million arrives. A quick confirmation before the next two shipments can prevent unnecessary exposed stock.
If the guild cannot cover the full requirement internally, record the remaining shortfall. Ready-made RSS resource packages are available on our site. First, though, calculate the net gap after accounting for in-game bags, production, and guild support. A transfer plan is no substitute for knowing the real requirement.
Close out the stock after delivery
Delivery is not the end of the job. Did the recipient complete the action? Are resources still exposed? Do they need anything else? Three short answers stop the guild from sending the same player duplicate shipments. On a war night, “received and used for healing” is more useful than “sent.”
Tracking resource tiles is a separate step toward covering the next shortfall. In LordsRally, !rss lets you check resource tiles, while !guildtiles shows the guild’s tiles. These commands do not show a player’s bag stock or Trading Post tax. See commands and features for tools you can use in tile planning, or browse the blog for more economy guides.
Keep the final check simple: the net amount requested, the amount received, and the exposed stock left after use. If they do not line up, ask why before sending more. Good guild economy is not just finding resources—it is making sure delivered resources do their job.
If you are setting up a shipment routine for your guild, start with rules for net requests and delivery confirmation. Contact us if you would like help with tile tracking.
Frequently Asked Questions
How should I account for tax on guild resource transfers?
Use the amount the in-game screen says the recipient will receive, not the amount you send. Check tax and capacity before every shipment.
Do resources have to go to the guild bank first?
No. If the recipient is ready, sending directly can avoid exposed stock sitting in the bank and an unnecessary second transfer.
Should I send resources while the recipient is offline?
Unless it is urgent, agreeing on a usage time and waiting is more controlled. If you must send them, assess the risk of exposed stock building up in their castle.
LordsRally tracks your target castles, finds them again after they teleport and alerts your guild.
Buy Now
