Automatic regears for Albion Online guilds
AlbionZVZ reads your guild's deaths from the battle data, matches each one to a player on the event roster and the build they were seated on, prices it, and lets officers approve or deny it before it reaches anyone's balance.
How regears work
A regear is the silver you pay a player to replace the set they lost on a guild event. Doing it by hand means scrolling a killboard, guessing who was wearing what, and arguing about it afterwards. AlbionZVZ does the lookup and the maths, and leaves the decisions to your officers.
- Set your prices once. Under Administration, Regears, give each playstyle a default silver value per death, then override individual builds. Rank rules go here too.
- Run the event. Players sign up, the caller seats them on builds from the comp, and you finish the event.
- Open the regear step. It is one of the settlement steps on the finished event, next to loot split, attendance and player split. Pick the source: Battleboard or Manual.
- Check the rows. Every signed-up player gets a row with their deaths, build, silver per set and total.
- Review deaths. Approve or deny each death, or change its build or percent.
- Pay. Continue to payout. Regear lands on each player's guild balance along with their share of the loot.
Prices: playstyle defaults and build overrides
Each build has a regear value. If the build has an override, that is the price. If not, the price falls back to the default for the build's playstyle: Caller, DTank, OffTank, Support, Healer, DPS or BattleMount. A build with no price pays nothing, and the review dialog says so.
You do not have to type every number. Apply EMV regear value fills build prices from market data: the lowest royal-city prices for each item, a percent of that total (the dialog starts at 80%), and a switch for each gear slot, so you can leave out food, potions or the mount. The builds table shows an estimated market value next to your override so you can sanity-check it.
The price of one set is the build price times the percent, rounded down. A 1m set at 130% pays 1.3m.
Rank rules
A guild usually does not regear everyone equally. Rank rules let leaders write that policy down once instead of arguing about it after each fight.
- Scope. Rules attach to the Member baseline or to a custom rank, for all roles or for one playstyle.
- What a rule sets. Whether regears are paid (or None), what percent of the set price is paid, and the maximum number of sets for that rank.
- Inheritance. Empty fields inherit from Member, and a rule for one role beats the rank's all-roles rule.
- Several ranks. If a player holds more than one rank, any rank that allows regears wins, and the highest percent and highest set cap among them apply.
A finished event applies the guild's rules automatically. In the regear step each player shows a chip with the rule that decided their pay, and a rank rules dialog lets you change a rank for this event only without touching the guild setting. For one player, set Rank rule to Always regear or Never regear. Refresh rules picks up changes you made after the event was opened, and a toggle turns rank rules off for the event.
Reviewing deaths
The review dialog lists every matched death. Selecting one shows the kill, and you choose Approve or Deny, optionally with a comment. You can also change the build or the percent for that one death, and the dialog shows exactly what it will pay, for example the build price, the percent, and whether a cap applied.
A death the rank rules would refuse shows Denied by rank. Approving it pays it. Denying a death removes that set from the player's total.
Limits and funding
- Max sets per player caps how many deaths are paid per player. When a cap bites, the earliest deaths are the ones paid.
- Fund from loot split takes regear out of the event's net loot pool before the remainder is split. Max loot split for regear is a ceiling on that share of the pool. If the regear total would exceed it, every player's regear is scaled down proportionally.
- With Fund from loot split off, regear is paid from the guild bank on top of the loot split, so the whole pool is still divided between players.
Edge cases officers ask about
- Fought but never signed up. Rows come from the roster, so a player who is not on it has no row. Add them to the event first.
- No linked in-game guild. Battleboard mode needs your in-game guild linked on the guild's Integrations page. Without it, use Manual.
- Wrong fight window. The battles come from the event's CTA window, which can be at most 24 hours. Open the CTA window on the event, drag the markers to the real start and end, and re-check the payout afterwards.
- A payout was a mistake. Officers can revert a payout from the payouts page, and the silver comes back off the balances. If a member has already moved it, reverting can leave them owing the guild the difference. Payout history is kept for 30 days, so older payouts cannot be reverted.
Compared with spreadsheets and killboard bots
A spreadsheet is fine for five deaths. At fifty it becomes a night of copy and paste, and the rank policy lives in someone's head. A killboard bot tells you who died, but it does not know your build prices, who was seated on what, or which rank gets what.
AlbionZVZ ties the killboard to the roster, so a death arrives already linked to a player, a build and a rule. The trade-off is that it only works for people on the event roster. If your regears are decided one-off by a leader reading a thread, a spreadsheet may still be quicker.
Who it is for
Guilds that run regular ZvZ and regear their members: officers who handle the payouts, leaders who set the policy, and players who want to see what they are owed and why.
Frequently asked questions
How does it know who died?
After the event is finished, the regear step reads the battles in the event's CTA window that involve your linked in-game guild. Each death is matched to a signup by the player's linked Albion character id, then by character name, and finally by Discord display name (only for players with no linked character). You can move the window if the fight started early or ran late.
Does the site pay out silver in game?
No. Silver stays in game. The site keeps the books: the regear is added to the player's guild balance, and an officer hands the silver over and marks it paid. Every change is logged with who made it.
Can different ranks get different regears?
Yes. Rank rules set, per rank and optionally per playstyle, whether regears are paid, what percent of the set price is paid, and how many sets. A Trial rank can get nothing while Core gets 130%. Officers can override a rank for one event, or one player.
What if a player switched builds in the middle of the fight?
Price each death on its own. In the review, you can pick a different build or a custom percent for a single death, so a player who swapped to a healer set is paid for the set they actually died in.
What if the battle data is late or missing?
Switch the regear step from Battleboard to Manual and type the death counts yourself. Build prices and values still fill in automatically.
Can regears come out of the loot split?
Optionally. With Fund from loot split on, regear silver is taken from the event's loot pool before the rest is split. A cap on the share of the pool you allow for regears scales every payout down proportionally if the total would go over it.
Do I need Discord to use regears?
No. Regears work from the website. If your guild has Discord linked, players can check their balance with /balance, and officers can opt in to a Discord receipt for each payout.
Why did a death show as Denied by rank?
The rank rules would not pay it, for example because the player's rank is set to no regear for that role. An officer can approve that single death and it is paid anyway. Officer decisions always beat rank rules.