Community software for the people running the servers
A WordPress plugin for running a gaming community. Discord sign in, members, applications, feedback, activity, documents, support, a staff panel. Per game integrations are next. The site around it is still designed and built by hand, per community.
Software, site, community
GuildWorks is three things. The plugin does two of them. The site is built by hand, per community.
Software
Discord sign in, member records, applications, feedback, activity. Runs inside WordPress. No second platform, no second login.
Site design
This part is not the plugin. Each community gets a site built for its own brand. The plugin goes in behind it once the site is standing.
Community
Who is active, who is new, who needs a nudge. Plus a private way for members to flag a problem.
Current features
Running means built and in use on the beta install today. Planned means designed and scheduled, not started.
Runs inside WordPress
The plugin installs on the community’s existing WordPress site. The hub sits on the same domain, under the same login, in the same backup. One thing to keep patched.
Discord sign in
Members sign in with Discord. No password is ever set. Roles come across on sign in, so someone with Staff in Discord lands on the staff panel without being granted it twice.
Member hub
One page per member: their number, their documents, their time away, their tickets, and anything waiting on them. It is the first screen after sign in.
Applications
An applicant fills in the form, staff read the answers side by side and accept or decline. Accepted applicants can be held in a wave and admitted together on a launch date.
Anonymous feedback and forms
Polls and feedback forms where staff see the answers and not the name. Who was eligible and what was answered sit in two tables with nothing joining them, so there is no record to look up later.
Activity from in game
A resource on the game server posts play sessions back to the site. Hours show on the member’s profile, and the roster flags anyone not seen for two weeks.
Privacy controls
Member counts, rosters and activity are off the public site by default. Each community turns on what it wants shown, figure by figure.
Support tickets
A member opens a ticket and staff answer in a thread. The queue shows which side it is waiting on. Staff can leave notes on a ticket that the member never sees.
Documents and sign off
Rules and policies are versioned. Publishing version 3 asks every member to read and sign again, with a grace period before anyone counts as out of date.
Time away
A member requests leave with a return date. Staff approve it, the roster shows an On leave pill, and the activity report skips them until they are back.
Notices and Discord DMs
Decisions, reminders and document changes land in the member’s hub, and as a Discord DM if they allowed one. Staff can see which notices were never opened.
Staff panel
Overview, roster, applications, waves, feedback, documents, tickets and reports, all on the front of the site. Staff never need a wp-admin login.
Member numbers
Members request the number they are known by in game. The request is checked against every number already taken and held until staff release it, so two people never end up as 42.
Creator pages in a community
The Creator edition already builds pages for characters, servers and the people a channel plays with. The same pages inside a community install, so a community can push its own creators.
Per game integrations
ARK: Survival Ascended first. Discord roles drive the server whitelist, and a player links their game identity once. A module per game after that.
Two editions
Community edition
For a server with members. Applications, member hub, feedback, activity, documents, tickets and a staff panel in one plugin. The first community on it is a FiveM roleplay server, in beta. The game side is the part still being written.
Creator edition
For a channel rather than a server. It runs today on a GTA roleplay and ARK channel. The video library pulls itself in from YouTube and sorts by format, and characters, servers, creators and story arcs each get a page with the right videos attached.
Now, next, later
Running the beta with a real community and fixing what that turns up. The hub, the staff panel and the daily screens are all in use now.
A second community on the plugin, the in game resource that posts sessions back, and the first creator pages inside a community site.
ARK whitelist sync driven by Discord roles, then a module per game.
Hub and staff screens
Two installs are up. A FiveM roleplay community is on the Community edition, in beta. A GTA roleplay and ARK channel runs the Creator edition.
The hub and staff shots below are the real screens on the beta install, filled with invented members.
Home. Hero, positioning and the application call to action.
Server page. What the community runs and when it is busy.
Guidelines. Long form content pages on the same system.
Home. An access checklist, documents to sign off, notifications and a member number.
Feedback. Anonymous by design, with nothing stored that links an answer back to a member.
Support. A private thread with staff, kept out of Discord DMs.
Overview. What is waiting, who cannot get on the server, and the countdown to the next wave.
Roster. Every member with their number, status, Discord roles and time away.
Applications. The review queue by track and wave, with how long each one has been waiting.
Reviewing one. The applicant’s answers beside the reviews other staff have already left.
Tickets. Support threads by category, and whether it is the member or staff holding things up.
Reports. Who has not acknowledged the current version of a document, and who has gone quiet.
Video library. Pulled in from YouTube, sorted by format, tagged by game.
Characters. Status, the servers they play on, and their videos.
Creator pages. Who the channel plays with, and what they play.
We are looking to partner with current communities
If you run a community or create for one, get in touch. We would rather build this with a few real servers than guess at what they need.
Early partners get their setup migrated, their integrations built, and what they ask for goes on the roadmap first.
Software, site design and community tools for gaming communities and creators.
© 2026 GuildWorks