COMMANDNET LINK

Discord ↔ Forumify

For most MILSIM communities, Discord is where the community lives day to day.

Forumify may hold the structured information.

Discord handles communication.

The problem is keeping the two synchronized.

CommandNet Link is designed to bridge that gap.

More Than One Discord Server

CommandNet Link is being designed around communities that may operate multiple Discord servers.

For example:

Main Community Discord

alongside private servers for:

Infantry

Rangers

Aviation

Special Operations

Staff

Each connection can maintain its own configuration.

That means the same Forumify role can map to completely different Discord roles depending on the server.

Role Synchronization

CommandNet Core can assign roles based on organizational information such as:

• Unit
• Rank
• Specialty
• Other Forumify roles

CommandNet Link can map those roles into Discord.

When organizational information changes, Discord can remain aligned with the community's actual structure.

Discord Commands

CommandNet can also expose information through Discord commands.

Examples include looking up information about:

Personnel

Units

Promotions

Operations

Patrols

That allows members to retrieve useful CommandNet information without always leaving Discord.

Operational Announcements

Other CommandNet modules can use the Link infrastructure to publish information into Discord.

CommandNet S3, for example, can announce when:

A mission briefing becomes ready

or

A new SOP version is published

This allows Forumify to remain the structured source of information while Discord handles immediate community communication.

Built for Connected Communities

The goal isn't to replace Discord.

The goal isn't to make Discord the database either.

Each platform should do what it does best.

Forumify manages structured community information.

Discord handles communication.

CommandNet Link connects the two.

COMMANDNET LINK

Your units.

Your roles.

Your community.

In sync.

Command and Community, Linked.