-
Notifications
You must be signed in to change notification settings - Fork 400
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixed Cargo Bounties #1010
Fixed Cargo Bounties #1010
Conversation
Should probably add markers to note what is being changed, and that those are deltav changes. |
To the first thing, yeah, I didnt said much as this is a draft and alot can change so I would wait till its functional. |
this still would be nice for upstream so it would support multi station sharing a trade station but using each stations bounties |
You are not wrong. |
Co-authored-by: Adrian16199 <[email protected]> Signed-off-by: blueDev2 <[email protected]>
I'm not sure what markers you are talking about. |
Do you think I really should make this an upstream PR? |
The markers are pretty much just notes that indicate that an upstream file was touched that usually goes like: # DELTA V-Fixes Cargo Bountys |
It would be a good attempt as deltanedas suggested, it would fix it and less upstream file touched that are different from wizden. |
Where am I supposed to mark that down? |
So basicly { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here's just a few I had time for right now
@@ -17,4 +19,10 @@ public sealed partial class CargoBountyLabelComponent : Component | |||
/// Used to prevent recursion in calculating the price. | |||
/// </summary> | |||
public bool Calculating; | |||
|
|||
/// <summary> | |||
/// The Station System to check and remove bounties from |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/// The Station System to check and remove bounties from | |
/// DeltaV - The Station System to check and remove bounties from |
@@ -65,16 +67,17 @@ private void OnPrintLabelMessage(EntityUid uid, CargoBountyConsoleComponent comp | |||
|
|||
var label = Spawn(component.BountyLabelId, Transform(uid).Coordinates); | |||
component.NextPrintTime = _timing.CurTime + component.PrintDelay; | |||
SetupBountyLabel(label, bounty.Value); | |||
SetupBountyLabel(label, station, bounty.Value); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SetupBountyLabel(label, station, bounty.Value); | |
SetupBountyLabel(label, station, bounty.Value); // DeltaV - Track owning station |
I'm gonna wait until a final decision is made on the upstream PR before adding code markers. |
Yes, this is a flaw with the bounty system that would also affect wizden, and their downstreams, if they put the station on a different map. If they don't accept it for whatever reason, which I doubt, can just reopen this pr. |
Upstream PR merged: space-wizards/space-station-14#26469 |
# Description This PR adds a CVar that allows server hosts (such as N14 who need it) to optionally disable the Crit Threshold modification part of the MoodSystem. This is useful if a server has some other system that frequently messes with Thresholds, and that a server host wishes their system to not have to fight with Mood for it. # Changelog No changelog because this isn't playerfacing.
About the PR
Fixed Cargo Bounties
Why / Balance
Players tend to want the bounties to work so that they don't have to depend on mail for funds.
Technical details
Made bounty label components also hold the station where it was printed, so that the main station's bounty DB is used instead of the automated trade station's bounty DB
Media
TODO
Breaking changes
Changelog
Fixes #955
🆑 blueDev2