NuggoDEV / NuggoDEV/CountersPlus

Per-Environment Base Offsets for 'Parent to Base Game UI' (Plus others.)

Open
#133 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
152
Forks
35
PR merge metrics
No merged PRs in 30d

Description

Is it because of an issue?
The base game UI is not in the same orientation for every environment. For example, EDM makes the UI elements smaller and by extension, lower. Counters+ UI elements do not account for this even with 'parent to base game UI' and the setting that attaches the Z position both on.

Describe your solution
Per-environment size/position offsets that are built into the code. (New environments would of course just use the default environment value prior to updating the mod for them.) As long as the UI follows the differences in base UI positions properly, there shouldn't need to be any change to the in-game customization settings. Disabling the 'parent' option should be sufficient to disable this automatic adjustment as well.

A programmer yourself?
I've only worked extensively with the code base in Second Life, almost a decade ago, which used 'LSL' and 'Mono'. I've heard they're a mix of Java and C# however, and I do intend to learn how to code mods eventually, so I may in fact eventually come help with this, as there are other 'enhancements' that I have in mind for this mod.

Other enhancements in mind;

  • A 'display example values instead of labels' toggle.
  • 'Display combo (with/without FC bars) and multiplier elements in customization environment' toggle,
  • Select preview environment (should tie in with the original enhancement's base UI offsets.)
  • Additive offsets for base game UI which apply to the Parent function.
  • Make the Z position slider become an additional offset when 'use base Z value' is ticked.
  • Finer per-counter height adjustments than just -1 to 4.
  • Per-counter text size adjustment.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named in the issue. Start by locating the parent-to-base-game-UI implementation and its environment handling, then determine how the requested offsets should be represented; done means the UI follows each supported environment's base position while the existing customization behavior remains usable.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
game-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.