refactor: Cleanup ComplexSet code layout and skeletonize its JSDoc's.

[carys-the-weed-cloud]

I added barebones JSDoc styling where i could in ComplexSet and tangentally scr_population_influence as well. I did slip in a few code changes here and there as they caught my eye but nothing that should cause a regression.

In ComplexSet I also rearranged things so all variable definitions are at the top of the file instead of interspersed throughout.

---

Summary by cubic

Reorganized ComplexSet into a clean top‑to‑bottom layout and expanded lightweight JSDoc across its API and scr_population_influence. Improves readability, type hints, and maintainability without changing expected behavior.

• Refactors

  • Hoisted fields, statics, and shader handles; grouped helpers; normalized parameter names and early returns.
  • Added @param, @return, and @self JSDoc across ComplexSet methods; typed helpers like scr_has_style, valid_sprite_transform_data, and sprite_get_uvs_transformed.
  • Centralized default draw order and deduplicated purity‑seal positioning across armour types.
  • Created global.base_component_surface up front; call base_armour() before Techmarine overlays.
  • assign_modulars: use position = "" to opt‑in override; simplified style checks and array early‑exit.

• Bug Fixes

  • merge_influences: pass id into adjust_influence and updated @self to Asset.GMObject.obj_star.
  • Added sprite‑existence guards when computing shadow UV transforms.
  • assign_modulars: respect provided position for non‑weapon items so they render in the right area.

^{Written for commit f880d0f. Summary will update on new commits.}

[cubic-dev-ai]

1 issue found across 2 files

Confidence score: 2/5

• In scripts/scr_ComplexSet/scr_ComplexSet.gml, the default assign_modulars() behavior appears to clear each modular item's position, so global.modular_drawing_items are no longer added to the ComplexSet and modular visuals may silently disappear at runtime; only override position when a caller explicitly provides one (such as weapon visual overrides) before merging.

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

No issues found across 2 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Re-trigger cubic}

[cubic-dev-ai]

No issues found across 2 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Re-trigger cubic}

[cubic-dev-ai]

0 issues found across 2 files (changes from recent commits).

_{Re-trigger cubic}