-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Rubik has random debt depth #64226
Comments
I don't see any reason for why there should be any relation between CBM installation costs and the maximum dept Rubik is willing to be in. It would be horrible to go on an exploration trip and have your reasonably conveniently located Exodii base teleport away. |
Because exodii are supposed to be the only source for cbms. So I'm assuming autodocs will not be able to install cbms in future. And problems with globally_unique will be fixed somewhen in future, no doubt, so you won't be able to reroll max debt.
|
Unless things have changed since I last played, you pay for CBM installation at the time of installation. If, however, the implementation has changed such that installation cost has to be drawn from an account into which you have to deposit before a CBM installation can be performed, yes, the account should be able to contain enough funds to cover every installation your current trust level allows. I obviously don't understand what your "despawn" comment is supposed to mean, so just repeating it louder doesn't provide any additional understanding. Despawn just before detection of another one seems like teleporting it to me (although I guess despawn might mean reset of any progress as well as a move to a worse location. |
By "despawn" They're asking for the Exodii base to be made a globally unique location through the specific mechanism of removing old locations when you discover a new one. This is not possible for a variety of reasons, and while many people are interested in globally unique NPC locations, removing already discovered locations is not a solution we're considering. If you'd like to learn more please search for the various existing issues on the subject. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Please do not bump or comment on this issue unless you are actively working on it. Stale issues, and stale issues that are closed are still considered. |
This probably should be solved, rubik shouldn't really accept any debt at all. EDIT: If this is the amount of money they're willing to owe to the player, that's another story... it's not a big problem if they owe the player money nor for that to be variable. It would be nice to have a little more consistency though. |
This is definitely the amount Rubik is willing to owe you. So you can trade them... IDK, 10 thingies and they'll owe you $100. But if you trade them 1000 thingies, they're still only willing to owe you $100. Rubik's is variable because it depends at least partly on their altruism! And remember: altruism is randomized! The calculation is in npc::max_credit_extended. Lines 2074 to 2093 in 3c95a24
It would be pretty simple to short-circuit this logic with a flag if desired.
|
We can just define Rubik's altruism as a flat value, there's an option for that already |
Oh, so there is. Well it's VERY easy when it already exists. So rubik's definition, here:
Needs a defined personality, like this: (Not these values exactly! Probably!)
The NPCs.md documentation for reference: https://github.com/CleverRaven/Cataclysm-DDA/blob/master/doc/NPCs.md#npc-instance-definition |
Describe the bug
Each vendor in multiple exodii bases has a separate and random value for how much they can owe player, ranging in my testing from $100 to $700.
Having low values forces player to find another exodii base or an autodoc to install high value cbm.
Attach save file
Baseline-trimmed.tar.gz
Steps to reproduce
Expected behavior
first exodii base should despawn right before you find another oneScreenshots
No response
Versions and configuration
Dark Days Ahead [dda]
]
Additional context
No response
The text was updated successfully, but these errors were encountered: