Skip to content
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

MPA Session Calculation #1651

Merged
merged 4 commits into from
Mar 4, 2024
Merged

MPA Session Calculation #1651

merged 4 commits into from
Mar 4, 2024

Conversation

pstalcup
Copy link
Contributor

No description provided.

Copy link
Contributor

@spaghetti-squash spaghetti-squash left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay I think I see what's going on here; you're letting the extraValue be a marginal familiar mpa thing, and you're trickling it down through barfFamiliar and barfOutfit, and then extracting it in session calcs.

Neat!

@@ -160,5 +164,5 @@ export function barfOutfit(spec: OutfitSpec = {}, sim = false): Outfit {
parka: "kachungasaur",
});

return outfit;
return { outfit, extraValue };
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't love doing this for barf and nothing else, seems counterintuitive & inconsistent. But I get it

Might be worth exporting two functions, like the freeFightFamiliarData and freeFightFamiliar thing?


return {
familiar: best.familiar,
extraValue: extraValue(best, meatFamiliarEntry, jellyfish),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I need some documentation about what extraValue means here. extra compared to what?

Copy link
Contributor

@spaghetti-squash spaghetti-squash left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't love the way we're passing this information around but I can't think of a nicer way; fix the merge conflicts and make it so

@spaghetti-squash spaghetti-squash merged commit d06c19e into loathers:main Mar 4, 2024
4 checks passed
github-actions bot pushed a commit that referenced this pull request Mar 4, 2024
* MPA Session Calculation

* Attempt to readd marginal familiar extra value tracking

* Formatting & Fixes

---------

Co-authored-by: neil <[email protected]>
Co-authored-by: horrible little slime <[email protected]>
spaghetti-squash added a commit that referenced this pull request Mar 5, 2024
spaghetti-squash added a commit that referenced this pull request Mar 5, 2024
github-actions bot pushed a commit that referenced this pull request Mar 5, 2024
@spaghetti-squash
Copy link
Contributor

Had to revert, this is a breaking change because of a circular bit of logic between barfFamiliar and barfOutfit. I don't think we can capture the excess familiar value with that level of precision.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants