Project

General

Profile

Feature #2671

Turn off experience/attribute/... caps

Added by Who Knows over 2 years ago. Updated 2 months ago.

Status:
Rejected
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
Start date:
06/12/2015
% Done:

0%

Severity:
Normal

Description

Best would be if it could be set on a game level (when you choose a name for the PC).
I'll be happy as well if it's "just" in the global setup.

History

#1 Updated by Jeffrey Haines over 2 years ago

  • Status changed from New to Feedback needed
  • Priority changed from Normal to Low

This is something we can do before 1.0.

But we need to ask some questions... Concerns I have are, does the ability to go over the cap break anything?
What calculations would be affected by values over 100?

Does this include major and minor skills? Level up dialogue attributes? Max level?

We do need to figure out all of these variables and where they exist in the code.. we wouldn't want to create any project bloat.

#2 Updated by Who Knows over 2 years ago

Jeffrey Haines wrote:

This is something we can do before 1.0.

great! :)

But we need to ask some questions... Concerns I have are, does the ability to go over the cap break anything?
What calculations would be affected by values over 100?

If it's possibe, drop skill-/level-/attribute caps completely. Most important would be the PC level since having level 200 will influence health, magicka and fatigue which may be interesting in the first place.
Yes, short values will most probably become a problem. Making those int or long would have to be done. Except - and I am quite sure of that - you've already been counting on requests like this right from the start. ;)

Does this include major and minor skills? Level up dialogue attributes? Max level?

I guess the easiest and most logic would be to keep every calculation and remove upper caps. So
IF ( i_base_potion_strength >= <value_needed_for_exclusive_potion> ) THEN i_potion_quality = "exclusive"
would give the same results because there is no "uber exclusive" potion in the game. Whatever i_base_potion_strength gets, there is a logical cap for the outcome that depends on the possible potions qualities. If mods create "blow-you-out-of-your-shoes" potions they could make more distinctions. Potion duration could still be calculated as it is done by the original formula because the base_calc_value is mot capped - effect: potions last longer.
The same would apply to speechcraft, 300% friendship/trust would not change anything. There could be a mod that makes getting from 0% trust to 100% faster if speechcraft is x-times bigger than the (uncapped) maximum.
The outcome of level 1000 armorer might be limited in the same way, except a mod makes use of the calculated value and e.g. makes durability of steel-* from default_max to default_max+100 on repair etc. This might help when making crafting mods - for those who desire such.

Fighting skills, willower and all primary primary attributes like speed would be especially interesting to level up without upper outcome boundaries. They have an instant influence on gameplay (running) and the main attributes (AKA "secondary attributes") as well - independent from the "environment" like what objects exist in the game.

To sum it up: please remove boundaries and let's have calculations in a reasonable way. What does not fit can be done with (levelling related) mods like it's been done before. What seems odd to some can still be restricted. The other way around is much more cumbersome.

Do you think it's helpful to make a forum thread regarding these questions?

#3 Updated by Jeffrey Haines over 2 years ago

  • Related to Feature #2758: OpenMW: Use Variables To Control Skill/Attribute Maximum Levels added

#4 Updated by Alexei Dobrohotov 10 months ago

  • Target version set to openmw-future

#5 Updated by scrawl . 2 months ago

  • Subject changed from OpenMW: turn off expericence/attribute/... caps to Turn off experience/attribute/... caps

#6 Updated by scrawl . 2 months ago

  • Related to deleted (Feature #2758: OpenMW: Use Variables To Control Skill/Attribute Maximum Levels)

#7 Updated by scrawl . 2 months ago

  • Status changed from Feedback needed to Rejected
  • Target version deleted (openmw-future)

Also available in: Atom PDF