Repository navigation
fix: The Debug-switch warning says the setting goes back to the startup preference, not that it reverts - #3237
Merged
hatayama merged 3 commits intoOct 7, 2026
Conversation
Unity restores the Code Optimization On Startup preference on restart, a per-user setting that may itself be Debug, so saying the setting reverts misleads readers into expecting Release.
The session value set through CompilationPipeline is replaced at startup by the per-user Code Optimization On Startup preference, which defaults to Release but may be Debug, so the warning now names that preference instead of saying the setting reverts.
…erence The skill reference, the soak-testing doc, and a code comment said the setting reverts, is lost, or returns to the project's setting. Unity restores the per-user Code Optimization On Startup preference instead, which can itself be Debug.
Contributor
|
Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configuration
📒 Files selected for processing (5)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
hatayama
merged commit Oct 7, 2026
ea9d692
into
feature/hot-reload-large-project-feedback-3
4 of 5 checks passed
This was referenced Oct 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
CompilationPipeline.codeOptimizationchanges only the native value for the current session. It writes neither EditorPrefs nor the project.ScriptDebugInfoEnabled, shown in Preferences as 'Code Optimization On Startup'. It is a per-user setting, not a project setting, and it defaults to false (Release).uloop set-code-optimization debug --startupwrites that same key.uloop launch -r, which matches a startup preference of Debug. "Reverts" read as "goes back to Release".Changes
docs/soak-testing.md: a restarted Editor comes back on the per-user startup preference, not "the project's own setting".Verification
go -C cli/project-runner test ./internal/projectrunner -run 'TestPausePointAutoDebugSwitchWarningRecommendsApprovedStartupCommand' -count=1failed on the mismatch. With the constant changed, it passed.gofmt -l cli/project-runner: no output.go -C cli/project-runner vet ./...: exit 0.golangci-lint run ./...incli/project-runner: 0 issues.git grep -n "reverts on every Editor restart\|project's own setting\|lost on every Editor restart" -- cli Packages docs: no matches.This pull request targets an integration branch, so the pull request CI does not run on it; the checks above were run locally.
Not changed
set-code-optimizationwording "for this Editor session" and its command description.