WIP: Seafluff Guidebook changes. #1043
No reviewers
Labels
No labels
Area/Accessibility
Area/Admin Tooling
Area/Art
Area/Atmospherics
Area/Cargo
Area/Character / Species
Area/Chat
Area/Combat
Area/Command
Area/Database
Area/Engineering
Area/Graphics
Area/Guidebook
Area/Mapping
Area/Medical
Area/Preferences / Options
Area/Roleplay / Lore
Area/Roundflow / Antag
Area/Rules
Area/Salvage
Area/Science
Area/Security
Area/Service
Area/Silicons
bug
Changes: Audio
Changes: Map
Changes: No C#
Changes: Sprites
Changes: UI
documentation
DON'T MERGE
duplicate
good first issue
help wanted
holding to vote
Note/Port
Note/Upstream
Priority
Critical
Priority
High
Priority
Low
Priority
Normal
size/L
size/M
size/S
size/XL
size/XS
State/Approved
State/invalid
State/Merge Conflict
State/Needs Changes
State/Needs Discussion
State/Untriaged
Type/Balance Change
Type/Bugfix
Type/Documentation
Type/Enhancement
Type/Feature
Type/Question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Byrd-Station/Byrd!1043
Loading…
Reference in a new issue
No description provided.
Delete branch "Allycat/ByrdAllycat:GuidebookAllycat"
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?
Short description
Adding Byrd section, with SOP and space law and other updates.
Why we need to add this
Seafluff's Guidebook changes, I just did coding and fixed some errors. Seafluff can answer queries about need.
Checklist
Breaking changes
None
The SOP is not accessible in-game.

You have to place xml and yaml files under the
Resourcesdirectory/folder.In this case, yaml files in
Resources/Prototypes/_Byrd/Guidebookand xml files inResources/ServerInfo/Guidebook/_Byrd(Additional folder can be made to make it look nicer, more organized)I also recommend hiding the old sop to avoid confusion
@EchoOfNothing wrote in #1043 (comment):
Scroll down. It's in a different section labeled Byrd.
However I cannot say why, as I was organizing it based on Seafluff's direction. If changes need to be made, they should be involved in it.
@Allycat wrote in #1043 (comment):
There is no where left to scroll that's the screenshot of the entire guidebook.
Byrdcategory doesn't exist because the files were not place where they belong. And also Seafluff told me that theByrdcategory is supposed to replace the old sop category (if you don't know how to do this tell me, I will explain how to achieve this in more detail).@ -0,0 +69,4 @@name: guide-entry-byrdknowledgepriority: 6text: "/ServerInfo/Guidebook/_Byrd/ByrdKnowledge.xml"#ByrdStation SOP Entries begin hereI recommend replacing
#ByrdStation SOP Entries begin herewith#region SOPor#region ByrdStation SOP(but I think addingByrdStationhere is quite redundant since it's already in the file calledByrd.yml) and#Byrdstation SOP entries endwith#endregion. This way most IDEs will let you collapse those regions nicely, making reading and navigating the file easier.I am aware of how to do it, it seems there just was A. a miscommunication with Seafluff and myself, and B. an error when the PR was made. I'm newer to the forgejo/codeberg setup and so likely mixed up a couple things when manually making the PR (I manually uploaded the files and likely swapped guidebook and _byrd in location).
But it was all well organized, for the purposes I was aware of.
If you'd like to discuss more, I'd rather we just talk on discord if that works
Seafluff Guidebook changes.to WIP: Seafluff Guidebook changes.View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.