Skip to content

Conversation

b-b-blueberry
Copy link
Contributor

@b-b-blueberry b-b-blueberry commented Aug 22, 2025

Summary

Rewrites some methods on SpaceCore to better allow for arbitrary draw calls from other mods (read: love of cooking), and fixes some minor presentation issues relating to custom buff effects since SDV1.6.

Changes

  • Separate various SkillBuff behaviours into their individual steps, made accessible to other programs.
  • Replace ParseCustomFields method with new TryGetAdditionalBuffEffects method, return success and all parsed buff custom skill buff effects and attributes from parsed CustomFields dictionaries.
  • Replace Transpile_IClickableMenu_DrawHoverText method contents with CodeMatcher solution for added precision since SDV1.6 changes to hover text draw behaviours.

Fixes

  • Fix irregular spacing between basic and custom skill buff effect entries and their icons.
  • Fix custom skill buff effects placed above divider between health/stamina and buff attributes.

- Fold all parsing behaviours into `SkillBuff.TryGetAdditionalBuffEffects` method with `out` params for parsed values, returning false on null input or no output.
- Run all buff string formatting through `SkillBuff.FormattedBuffEffect` method for consistency.
- Move all buff draw behaviours to `SkillBuff.DrawBuffEffect` method, with `DrawHealthRegenBuffEffect` and `DrawStaminaRegenBuffEffect` methods allowing arbitrary draw behaviours for SpaceCore specific buff effects.
…HoverText transpiler:

- Replace yield-by-index transpiler with CodeMatcher solution.
- Draw additional buff effects (health and stamina regen) below health, above divider.
- Draw custom skill buff effects above basic skill effects, below divider.
- Custom skill buff effects use the same spacing as basic skill effects.
@b-b-blueberry
Copy link
Contributor Author

the dramatic comparison

Before

spacecore-skillbuff-before

After

spacecore-skillbuff-after

@b-b-blueberry
Copy link
Contributor Author

Commit 271c327 in this PR also relates to #504 , so you might want to compare both and see which you prefer

@spacechase0
Copy link
Owner

So apparently my reorganizing the repository created conflicts for every single PR. I figured the PR system would be smart enough to handle files being moved around fine, but I guess not.

I plan on manually merging this soon with some rebase shenanigans, so no need to worry about fixing this. I'll leave the PR open until it's taken care.

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