chore(wetness-effects): set default MaxPuddleWetness to 1.5

[SkrubbySkrubInAShrub]

May not fix potential underlying issues with wetness effects, but does set a more reasonable default value that doesn't cause overly wet surfaces.

Summary by CodeRabbit

Release Notes

• Adjustments
  • Reduced maximum puddle wetness effect intensity to provide more balanced visual effects.

[coderabbitai]

📝 Walkthrough

Walkthrough

A configuration constant in WetnessEffects is reduced from 2.5f to 1.5f, lowering the maximum puddle wetness setting. This is a single-value parameter adjustment with no other functional changes.

Changes

Cohort / File(s)	Summary
WetnessEffects Configuration src/Features/WetnessEffects.h	Reduced MaxPuddleWetness constant from 2.5f to 1.5f.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

• jiayev
• doodlum

Poem

🐰 A puddle's dance, now tamed with care,
From two-point-five to one-point-five in the air,
Less wetness blooms where water gleams,
A gentle tweak to nature's schemes! ✨💧

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main change: adjusting the MaxPuddleWetness default value from 2.5f to 1.5f in the wetness effects configuration.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

📝 Coding Plan

• Generate coding plan for human review comments

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

No actionable suggestions for changed features.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

src/Features/WetnessEffects.h (1)

35-35: PR metadata polish: shorten title and add issue keyword if applicable

Suggested title: chore(wetness): lower max puddle wetness default
If this is tied to a tracked issue, add Addresses #<id> (or Fixes #<id> if fully resolved).

As per coding guidelines: **/*: provide suggestions for Conventional Commit Titles (50-char limit, lowercase description) and Issue References.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/Features/WetnessEffects.h` at line 35, Update the PR title to a concise
conventional commit style and add an issue reference if applicable: use a short
lowercase subject like "chore(wetness): lower max puddle wetness default" (<=50
chars) and append "Addresses #<id>" or "Fixes #<id>" when this change to
MaxPuddleWetness is tied to a tracked issue; ensure the commit/PR title follows
the repository's Conventional Commits guidelines.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/Features/WetnessEffects.h`:
- Line 35: The default for MaxPuddleWetness was lowered but runtime paths still
allow values > 1.5f; update the deserialization and preset/application paths to
enforce the cap by clamping settings.MaxPuddleWetness to the [0.0f, 1.5f] range
after loading or applying presets—specifically add a clamp of
settings.MaxPuddleWetness in the LoadSettings(...) routine and likewise after
any preset or climate-multiplier application in WetnessEffects.cpp so the
effective value used by MaxPuddleWetness can never exceed 1.5f.

---

Nitpick comments:
In `@src/Features/WetnessEffects.h`:
- Line 35: Update the PR title to a concise conventional commit style and add an
issue reference if applicable: use a short lowercase subject like
"chore(wetness): lower max puddle wetness default" (<=50 chars) and append
"Addresses #<id>" or "Fixes #<id>" when this change to MaxPuddleWetness is tied
to a tracked issue; ensure the commit/PR title follows the repository's
Conventional Commits guidelines.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 9072f367-e392-41d1-b7e4-fd95dae67640

📥 Commits

Reviewing files that changed from the base of the PR and between e0877a5 and e41e745.

📒 Files selected for processing (1)

• src/Features/WetnessEffects.h

[github-actions]

✅ A pre-release build is available for this PR:
Download

[alandtse]

Ok, this is also likely to end up with a revert war. Please provide screenshots showing the difference and identify what is the setup/weather. Absent a standard, it should be a vanilla install with just CS.

[SkrubbySkrubInAShrub]

Tbh, I don't care enough about this issue to make a new skyrim install to make comparisons, people complained about the high glossiness, doodlum told me to PR a change to the default values. If this isn't merged, then that's completely fine by me too.

[alandtse]

Well fuck it. We can have revert wars on this setting.