satisfactorymodding / satisfactorymodding/SatisfactoryModLoader

User Config Reset messes up on Array of Sections

Open
#415 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
344
Forks
225
PR merge metrics
No merged PRs in 30d

Description

From @ryan-skabelund on Discord

It’s when you have an array of sections. The values under the sections will think default is the data type default rather than the config default
My use case was using it to rebuild a graph, where each section under the array had two values: an X and a Y
The array itself was fine, I can’t recall the sections (I think they were fine? idk), but the individual values of X and Y was where it went wrong for sure
For each float (or any other type) under the section, the reset to default button was on
Wish I had a picture, I can get one to you late tonight if it helps. Otherwise if you download the “Configurable Explorer” commit from Slooped Up Explorer and compile it you can see for yourself, though it’s a lot of steps

https://github.com/satisfactory-mods-by-ryan/SloopedUpExplorer/commit/4b6168cbb3e81c67a20335e3f98d1d9f23d3553c

In the mean time, mod devs can disable "Allow User Reset" on arrays of sections to avoid confusing data problems

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

Start by reproducing the report using the Configurable Explorer commit linked in the issue, creating an array of sections with X and Y values and resetting an individual value. Compare the reset result with the configured default; done means values inside array sections restore their config defaults rather than the type defaults.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
game-dev, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.