Skip to content

Add DimensionSync - #11522

Open
sparr wants to merge 1 commit into
KSP-CKAN:masterfrom
sparr:add-dimensionsync
Open

Add DimensionSync#11522
sparr wants to merge 1 commit into
KSP-CKAN:masterfrom
sparr:add-dimensionsync

Conversation

@sparr

@sparr sparr commented Sep 7, 2026

Copy link
Copy Markdown

First-time submission, of my own mod.

DimensionSync is an editor plugin that keeps the dimensions of connected parts in step: resizing a procedural part carries the change along the stack, and a wing segment's tip dimensions carry to the root of the segment outboard of it. It knows about ProceduralParts, ROLib, Procedural Fairings, SSTU, and B9 Procedural Wings out of the box, and its field catalogue is ModuleManager-patchable so other mods can be added without a code change.

Inflated locally against the v0.2.0 release with kspckan/metadata before opening this: exit 0, no warnings, installs and uninstalls cleanly in a dummy instance.

Two notes in case they save a review round-trip:

  • release_status: development is deliberate rather than a leftover. The mod is tested and works, but it is young and I would rather set expectations low since I am confident there are use cases I haven't tried and edge misbehaviors I haven't triggered. Happy to drop the field if you would prefer it left to default.
  • The suggests are the mods it has explicit support for, plus Harmony2, which it uses optionally to see other mods' writes.

The content and description of this PR were approximately 90% authored by Claude Opus 5.

An editor plugin that keeps the dimensions of connected parts in step: resizing
a procedural part carries the change along the stack, and a wing segment's tip
dimensions carry to the root of the segment outboard of it.

https://github.com/sparr/ksp-mod-DimensionSync
$kref: '#/ckan/github/sparr/ksp-mod-DimensionSync'
$vref: '#/ckan/ksp-avc'
license: MIT
release_status: development

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Leaving this in will just mean that the mod doesn't get indexed by CKAN.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

At all? Or just not shown by default?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

It won't be shown to anyone unless they have their stability tolerance set to development. In any case we don't want you explicitly setting release_status in netkans. If you want the mod to be marked as a prerelease then you can make your github releases prereleases (or just document it in the readme).

- name: ProceduralFairings
- name: B9-PWings-Fork
- name: ROLib
- name: Harmony2

@Phantomical Phantomical Sep 7, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Harmony2 should just be a depends. Basically nobody installing your mod will know what Harmony2 does, and it does not change any game behaviour.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

Having it or not here does produce a behavior change. This mod is more aware of other mods' changes to parts with Harmony than without.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants