How do players start or join a guild?
Use the current guild interface for creation or invitation; the documented keybind and NPC location belong to a dated 2.0 announcement and must be verified in the live client.
- Creation and invitation belong to the current guild interface, while an old keybind or NPC location can drift.
- Find the live guild control first, then confirm whether the intended action is creating a guild or accepting membership rather than mixing both flows.
- The live interface reveals whether creation and invitation are still presented through the same controls described historically.
Choose the intended branch first: a creator looks for the creation action, while an invited player looks for membership acceptance. An outdated key or NPC reference should not override the current UI. Costs, unlock requirements, and locations remain unknown here and should not be guessed to complete the flow.
What should be checked when guild access is missing?
Confirm membership and account-link state before treating the guild interface or stash as broken.
- Missing access can come from membership state or account-link state before it indicates a broken stash or interface.
- Confirm those two conditions separately so a pending invitation is not diagnosed as a storage failure.
- Membership should be visible before stash permissions or perks can be evaluated.
Account-link state is another prerequisite worth separating from the guild screen itself. If either condition is incomplete, the missing interface has a plausible upstream explanation. If both appear correct and access is still absent, the page has reached its limit; current support is more appropriate than inventing a hidden permission or cooldown.
What are guild stash and perks for?
First-party documents establish shared stash and perk concepts, while current values and permissions remain live-client checks.
- Shared stash and perk concepts explain why guild membership can matter, but their present values and permissions remain live-client questions.
- Inspect the guild interface before planning around a cost, unlock, location, or bonus that this guide does not establish.
- A shared stash supports group storage, while perks describe guild-level benefits.
Their existence does not establish who can withdraw, what bonuses are active, or how they are unlocked now. Inspect the current guild panel for permissions and values before moving items or planning a build around a bonus. The Blood Pact page concerns a private league and should not be used to fill gaps in guild mechanics.
Guild decisions become clearer when the desired outcome is stated first. Someone trying to join should verify invitation and membership state; someone trying to store items should verify membership before examining stash permissions; someone evaluating benefits should read the live perk display rather than assume old values. Creation is a fourth action even when it shares the same interface. This ordering prevents a player from diagnosing a perk as missing when the account is not yet a member, or from treating a dated NPC reference as the current way to create. The page can establish the concepts of shared storage and perks while leaving their exact present rules to the client.
The dated 2.0 material is most useful as proof that guild creation and invitations were designed concepts, not as a permanent navigation map. If the old keybind or NPC location is absent, search the current guild interface before concluding the feature is unavailable. Joining has its own dependency chain: invitation, accepted membership, and account-link state precede stash or perk access. Once membership is confirmed, separate the shared-stash question from the perk question because each can have different live permissions or values. The dated material establishes neither who may withdraw nor which bonus is active, so a missing action should be compared with the current panel rather than filled with an assumed rank, cost, unlock, or cooldown. This sequence produces a useful support report: state whether the problem is creation, invitation, membership, account link, stash permission, or perk display. Combining those symptoms under “guild broken” would discard the useful distinctions in the available information.
Before you rely on this guidefirst-party material establishes guild creation, invitations, shared stash, and perk concepts, but an older 2.0 announcement is not proof that its keybind or NPC location remains current. Verify the interface, membership state, account link, permissions, costs, unlocks, locations, and perk values in the live client before diagnosing access or spending resources.