forked from HardLight/HardLight
update #3
Loading…
Reference in a new issue
No description provided.
Delete branch "HardLight/HardLight:master"
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?
About the PR
Why / Balance
Technical details
How to test
Media
Breaking changes
Changelog
I replaced all outside Cargo Request Terminals with Ash so that it is no longer needed to AHELP to get them removed at round start Ahelps take up valuable admin time. Also the QM can still make a console outside if they choose to with the board in their locker. Files changed: Resources\Maps\convex.yml Resources\Maps\fland.yml Resources\Maps\box.yml Resources\Maps\amber.yml Open any of these maps and go to cargo to see an ash pile Pictures attached None **Changelog** 🆑 - remove: Removed cargo request consoles that were just outside the front desk of cargo on Convex, Amber, Box and FlandAdded a guidebook entry for [form] Makes Bureaucracy more newbie friendly. And I love bureaucracy. Changed the guidebook entry `Resources\ServerInfo\Guidebook\Writing.xml` to have a hardlight section and put the [form] help there. Open the guidebook, navigate to Writing.  **Changelog** 🆑 - add: Added a guidebook entry for the [form] tag.bug->Bug(#4613) b9d9a92fc3## About the PR Changes the Machine Incompatible trait to grant 0 points. ## Why / Balance If you (as an admin, on the live server) compare `entities with JobTracker visualize` and `entities with JobTracker with Unborgable visualize`, the result is typically that **40-50%** of players take this trait. I fully acknowledge that there are people who feel highly uncomfortable with their characters being borged or otherwise have lore reasons, but I do not believe that this figure is concurrent with this. It is a generally accepted belief that the average player with this trait simply takes it because it is worth 4 extra points, with an incredibly niche downside, and it is taken purely as an afterthought to maximize the perks on many characters. This results in a disproportionately large number of players simply not being able to be put in an MMI if they are gibbed in a round, to the point where borging a brain is sometimes not even considered when someone gibs. Furthermore, it completely screws with Xenoborg gameplay in their current state, as every precarious victory only has a 50-60% chance of being _useful_ to them. I have discussed back and forth at great lengths with the playerbase and admin team how to approach this issue, and put simply this is the most conservative approach. I want to see if this change will improve things. The exact number of zero has been chosen to generously reflect those with consent preferences against being bored, allowing this trait to act as a consent toggle of sorts. Many people will simply take it even if it is worth a _single_ free point (see: snoring, stinky) due to how niche the downsides are. I wish to recategorize this trait, along with the others listed, as a **roleplay** trait, rather than a **mechanically advantageous / disadvantageous** trait. In line with this particular change, I have also chosen to nerf snoring, stinky and uncloneable to zero points. Players who wish to take these traits should be doing so for roleplay reasons, and not for free points. In my data below, I have also shown the unrevivable trait. Given the larger game impact this trait has, it is unsurprising that far less people take it. As such, I have left its point cost alone. ## Technical details Edited the `cost` values for the listed traits: - **Machine Incompatble:** 0pts - **Uncloneable:** +1pts - **Stinky:** 0pts - **Snoring:** 0pts ## How to test - Launch game - Look at trait options ## Media Below is a typical highpop example of the following: #### Machine Incompatble: `entities with JobTracker visualize` vs `entities with JobTracker with Unborgable visualize`  #### Uncloneable: `entities with JobTracker visualize` vs `entities with JobTracker with Uncloneable visualize`  #### Snoring: `entities with JobTracker visualize` vs `entities with JobTracker with Snoring visualize`  #### Unrevivable: `entities with JobTracker visualize` vs `entities with JobTracker with Unrevivable visualize` - Note the difference, as unrevivable has a much higher game impact  **Changelog** 🆑 Slatebreaker - tweak: Removed trait points given by niche/roleplay related traits0f543b89c0to2c519a77d0EnergyDomeNullspaceto ship save blacklist and fix parsing inFixedPoint2(#4646) 657ebab55bf59013e9a8to1e56fa167bSetOwnerparameter 00ec58c991View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.