latendresse76, MSfD was initial base of my knowledge about GMST, but it turned out that comments there are mostly assumtions. Testing shows that MSfD is frequently wrong. There are also lack of details and formulae. Still, I'm fully taking it into account, of course, thank you.

Oh, and I almost forgot, Hrnchamd, could you also provide information on creature skills (combat, magic, stealth)? Does the game just checks them instead of corresponding skills (e. g. Combat instead of Longblade, Magic instead of Destruction) or instead of skills of a corresponding specialization with a possibility to alter this with mods, or is there something more complicated?

There was a short thread a few years back discussing the enchantment (chance of success) formula, with the actual formula and musings on how it could be improved. I have it saved on my old computer, so I'll try digging it out later.

Hrnchamd, would you be able to work out the mechanics for lock picking? It would help very much in completing the Oblivion-style lock picking mod. Thank you.

Thank you, Nandorianen.

[Updated and moved down. This post can be ignored.]

skaeps.mp3, if you are looking for formula, then here it is:
Picklock chance = ((Security Skill + INT * 0.2 + LUC * 0.1) * Lockpick Quality Multiplier - (Lock Difficulty * fPickLockMult)).

Sorry, this formula is incorrect. Tested it just now. Results:
Picklock chance = ((Security Skill * 1.25 + INT * 0.25 + LUC * 0.1) * Lockpick Quality Multiplier - (Lock Difficulty * fPickLockMult)).

Please don't post unconfirmed information in this thread. It's supposed to be accurate and not confusing. It looks like you are missing the fatigue multiplier in your formulas. Please clean up inaccurate posts.

I'm still researching things you asked for. Organic containers respawn via a global variable, MonthsToRespawn. It is decremented at the end of each month, and when it reaches zero, it is reset to iMonthsToRespawn and all organic containers are refilled. Therefore, changing the GMST has no immediate effect.

My apologies for the first post. Fatigue multiplier, however, is another story. I think, since it is included in every formula for any action, it should be separated. One instance in the first post should be enough.


Thank you. I started to doubt if you are willing to do it.


So there is only one variable for all containers? Interesting. Thank you again.

Excuse me, Hrnchamd, are you still working on this?

I've been working on MGE XE for weeks. There are still notes from before, they are about 25% complete. I will get back to it when I have time.

Thank you. Then I will try not to bother you anymore.

Seems like the OpenMW devs have been looking for this info as well, so great job!

Could you find out what the formula used to determine Armor Rating is?

I don't know the exact name for it, but the number underneath the paperdoll in the inventory (Armor: #). Do NPCs use the same formula?

Hrnchamd seems to be busy. I'll try.

Added item recharge notes; yet another bug.

Hrnchamd, any chance for a MCP patch that allows us to disable the pickpocketing process altogether? I hate how the pickpocketing doesn't work. I hope to have a completely overhauled thief experience. To me, the idea of a thief character is kinda silly since most of the skills that thieves rely on are all but useless

I know you are busy and I don't mean to bug you with this. I've been working 2 jobs and going to school fulltime so I haven't done anything past initial testing on the last project you did for me (traps overhaul). I hope to get that done spring break (soon)

ST

Soon, we shall be able to steal some purse without suffering from a broken mechanic.

thanx, this is good news!!!

ST

The pickpocket rewrite is already in testing. You should go download it in the MCP thread if you haven't already and give it a try. There haven't been any complaints or problems with it, so I think Hrnchmd might decide to take it out of beta soon.

Regarding how much damage is absorbed by armor, this previous post is a little misleading:



Actually, there is a minimum damage taken based on the GMST fCombatArmorMult which by default equals 0.2500. So at a minimum you will always take 1/4 of the original damage dealt, no matter what your AR is. So in the above example of a blow landing 25 points, you will actually take (25 * 0.2500) = 6 points of damage.

I've tried a test by setting fCombatArmorMult to 0.5, had a char with full Daedric Armor @ 100 Heavy Armor (so AR of 265), getting hit by a custom Dremora (50 strength, 100 combat) wielding a custom weapon that did 40-40 min/max damage, and I always got hit for 20 points. When I changed fCombatArmorMult back to 0.2500, I got hit for 10 points everytime.

Here are are some observations regarding Auto Calculate Stats NPCs and what spells are available to them:


Obviously the spell has to have Auto Calculate Cost checked in the CS.

An Auto-Calc NPC will always try to own the most powerful spells, going from most powerful to least powerful. This is based on casting cost, not on a spell's effects/duration, etc, which is why a lot of NPC seem to have rather useless spells, e.g. casting Absorb Personality [Ranged] against a Daedric Battle-Axe wielding PC is rather silly.


Here are some of the GMSTs that help determine spell ownership:

fAutoSpellChance:
This is the minimum % casting chance an NPC needs for a particular spell in order to own it. This is based on his Auto-Calc stats. So, if it is set to 80.0000 (default value), an NPC will need at least an 80% chance of casting this spell. You can see the NPC's cast chance in the CS. This is why most non-caster NPCs (smugglers, acrobats, etc) never cast anything. Their Spell skills are so low (in the Class definitions) that all auto-calc spells never reach this setting's minimum.

iAutoSpellTimesCanCast:
Even though an NPC might have a high enough casting chance to own a spell, he/she will not own it if the NPC cannot cast it iAutoSpellTimesCanCast number of times based on the NPC's max magicka. By default iAutoSpellTimesCanCast = 3. So, if an NPC has 200 magicka, he/she will never own a spell which costs 70 magicka points, since 70 x 3 = 210 (greater than NPC's 200 max magicka), even if it passes the fAutoSpellChance requirement. Set it to 2 and suddenly that 70 point spell is available to the NPC.

iAutoSpellAlterationMax, iAutoSpellConjurationMax, iAutoSpellRestorationMax, iAutoSpellIllusionMax, iAutoSpellDestructionMax, iAutoSpellMysticismMax:
These are just the maximum amount of spells that an NPC might have from each School. So if you set iAutoSpellDestructionMax = 0, no auto-calc NPC will ever own a Destruction spell. If you set it to 3, the NPC will try to own the top 3 costliest Destruction spells that pass the fAutoSpellChance and iAutoSpellTimesCanCast requirements. However, there are rare cases, which I haven't been able to fully understand, in which this is not exactly true. For example, you might set the max spells for Destruction to 2, Mysticism to 2, and everything else 0. The NPC will still own a total of 4 spells, and they will never be from any spell school set to 0, but 3 might be Destruction spells and 1 Mysticism. Or you might get 4 Destruction and 0 Mysticism. Why? No exactly sure, but it is rare.

iAutoSpellAttSkillMin:
This one's a little hard to figure out, but basically it seems to work like this: if one of the spells selected (passes the above requirements) affects attributes or skills (absorb, drain, damage, fortify, etc), but not health, magicka, or fatigue, this GMST will help in selecting which particular skill or attribute spell to choose, since a lot of them have the same casting cost. It seems to chose the one that corresponds to your next highest attribute or skill which is equal to or less than this setting. So, if your Mysticism = 64, Long Blade skill = 97, and iAutoSpellAttSkillMin = 64 or less, the skill affecting spell will drain, absorb, etc, Mysticism . If you set iAutoSpellAttSkillMin = 65-97, that spell will now affect Long Blade. There are some bizarre discrepancies in exactly which skill/attribute spells are chosen, but this seems to be the general form.

Do we know anything about how the game determines which piece of armour takes a hit? Also, how is damage done to a piece of armour calculated?

That would be sweet.

Also, if you're still working on this Hrnchamd, could you determine how far and fast a projectile goes? If you can do that I can add my own projectiles to shadow the arrows, bolts and thrown weapons in-game so we can finally attach scripts to marksman ammo.