Member Identity

Membership in CoGM has two layers. This page covers how those layers work, the five ways someone becomes a member, what gets tracked where, and what happens on archive or kick.

Two layers

A community member is your account inside a community. It carries your display name, Discord identity, level, XP, message and voice activity, characters, and community-wide roles.

A guild member is your membership in a specific guild inside that community. It carries DKP, activity points, sub-guild label, archive status, and per-guild roles. One community member can hold guild member rows in several guilds at once.

One Discord account can hold community member rows in multiple communities. Each community is isolated from the others.

Five ways to become a member

  1. Apply on the web. Open the community's public page, sign in with Discord, fill out the application. An officer approves, and both records are created.
  2. Officer add. An officer adds you to a guild from the dashboard. Works only if you already have a community member record.
  3. Discord member role. If the guild has a member role configured, anyone holding that role on Discord gets records auto-created the first time they run a bot command.
  4. Run /upload. Uploading gear creates a placeholder member if one does not exist. The placeholder gets merged into your real account when you first sign into the dashboard.
  5. First sign-in. Signing in with Discord claims any placeholder records keyed to your Discord ID and merges them into your account.

The /join command opens a link to the community page. It does not create records on its own.

What gets tracked at each scope

Per community

  • Display name, Discord identity
  • Level, XP, message and voice activity
  • Characters
  • Community roles
  • Strikes, applications, tickets

Per guild

  • DKP, activity points
  • Archive status, archived date
  • Sub-guild label
  • Guild roles
  • Treasury contributions, storage actions

PvP participation rows live on the event but link back to your community member record. They stay around even if you leave the guild, which is what powers My PvP in lifetime mode.

Archive vs kick

Archive is a guild-level flag. The member is hidden from the active roster but every record stays put. DKP, activity points, characters, strikes, and PvP history carry over. Returning is automatic. Running /upload or being re-added by an officer flips the flag and the member returns with everything intact.

Kick is community-wide. The member loses access to the community on the web. Their records still exist for audit purposes, but they cannot view, sign up, or interact until an officer un-kicks them.

Region and family names

In Black Desert Online, family names are unique within a region (NA, EU, SA), not globally. CoGM tracks family names per region, so two people sharing a name across regions stay separate in roster sync, whois lookups, and PvP analytics.

Multi-guild and multi-community

Inside one community, a single account can hold guild member rows in more than one guild at a time. The /upload command picks the right guild from your sub-guild Discord role.

Across communities, no data crosses over by default. The one path that spans communities is your own PvP history. On the My PvP page, switch to All time to see your participations across every guild you've played for, in any community. Only your own rows show up. Other players' data from those guilds stays private to them.

Picking up a stale guild member

If a former member returns and runs /upload, their guild member row is unarchived and their old DKP, characters, and history pick up where they left off. No officer action required.