WIP: Tabletop-Esque Exclusive Campaign Infrastructure #561
No reviewers
Byrd-Station/Owners
Labels
No labels
bug
Changes: Audio
Changes: Map
Changes: No C#
Changes: Sprites
Changes: UI
documentation
DON'T MERGE
duplicate
enhancement
good first issue
help wanted
holding to vote
invalid
question
size/L
size/M
size/S
size/XL
size/XS
S: Merge Conflict
S: Untriaged
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Byrd-Station/Byrd!561
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "campaign-whitelist"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
PR Changes
Adds Campaign-specific player whitelist.
Reasons Behind Changes
There are people interested in a D&D-esque mini campaign, and it is about high time I add some infrastructure that has proven to be effective elsewhere.
Code & Technical details
The database model was changed to accommodate this new list. A lot of refactors were made to the Model.cs and ServerDb classes; purely syntactical.
Images; Sprites; Media
none
Checklist
Note to self: Consider adding a timer. If a campaign session goes on too long, forcibly reopen the server and end their session. They can continue another time. Consider a timer for 24 hours to prevent instantly turning it back on? Also consider scheduling command to automate the process for close and reopen, and schedule close command to cancel it?
Consider a ForceCampaignRound command, where it starts a fresh round in Sandbox which will last for time provided?
Consider allowing non-campaigngoers to join and spectate, perhaps even ghost role. This partially solves the isolative effect.
Breaking changes
Ingame Changelog
🆑
WIP: Tabletop-Esque Exclusive Campaignto WIP: Tabletop-Esque Exclusive Campaign InfrastructurePull request closed