Coordinate guild relic resources without losing the reason behind a decision

A player’s relic goal is personal until it uses a shared resource, shared schedule, or guild decision. Mark that boundary clearly. It prevents an informal conversation from becoming an assumed commitment without the right people agreeing to it.

For shared decisions, record the goal, the expected benefit, and the people affected. The record does not have to be long; it just needs to survive after the conversation moves on.

Common criteria include event role, readiness for a scheduled objective, prior contribution, agreed rotation, and the ability to use the resource immediately. Choose the criteria before naming the recipient whenever possible.

A transparent rule can still produce a disappointing answer. Its value is that members can understand the decision and know how a future decision will be made, rather than guessing at private preferences.

After assigning a resource, preserve the reason, recipient, related event, and any follow-up obligation. This makes later reconciliation much easier than rebuilding context from messages.

Review the rule at a predictable point, such as the end of a season or after a major event. A rule that was fair for a small roster may need adjustment as a guild’s goals and capacity change.