TB Oracle
RSS contributions

How to set fair Total Battle RSS contribution standards

Set Total Battle RSS contribution quotas using transparent resource targets, rolling pace, member context, and a fair review routine.

There is no universal weekly RSS number that is fair for every clan. A useful standard is visible, measurable, connected to the clan's actual needs, and reviewed with enough context to avoid punishing new or developing members.

Start from the capital need

Define the resource mix and total the clan needs for the next upgrade or operating cycle. Convert it into a roster target only after accounting for active member count and the people who cannot reasonably carry the same load.

Publish the five resource targets

Silver, food, iron, stone, and lumber should be visible separately. A single combined number can hide a critical shortage behind a surplus in an easier resource.

Use a rolling pace view

A seven-day rolling window reduces reset-day noise. Show who is on pace, who can recover with one push, and who has a repeated gap.

Trends matter when a member has a valid reason for one weak cycle or when a strong contributor is quietly burning out.

Make the follow-up predictable

Use the same review time and the same evidence. Recognize consistent contribution publicly, handle exceptions privately, and revise a target when most of the roster cannot meet it despite real effort.

See RSS contribution tracking

See your own clan record.

Start a 30-day trial with no credit card, then request a historical import from Settings if you are switching tools.

Start free

Keep reading