Jump to content
Sign in to follow this  
smacker909

setSkill / profile question

Recommended Posts

Can someone explain how the skill settings in your Profile interact with the setskill command? I believe since 1.60 the precisionFriendly and precisionEnemy settings in the profile have no effect, so If I set my profile for skillFriendly and skillEnemy to '1' does that set all parts of the skills array to 1' and then I can modify in a script.. say; _unit setskill ["aimingAccuracy", 0.8] leaving the rest at '1' ?

Share this post


Link to post
Share on other sites

Ondrej Spanel explained it to me like this once:

If you set the skill in your profile to 0.5 and the skill in the mission to 1.0 the result will be something in between the two, e.g. 0.7

How exactly it is calculated he hasn't said, or I forgot it.

Share this post


Link to post
Share on other sites

hmm... so for instance "skillEnemy 1" in profile.. and "_unit setskill ["aimingAccuracy", 0.5]" in a script.. then only "aimaingAccuracy" would be ~ .7 and the remaining elements in the skill array would be 1? I'm assuming you can't set "aimingAccuracy" in the profile. Maybe that's a bad assumption?

Share this post


Link to post
Share on other sites

You can set the enemy precision in the profile actually. Which then goes the same I presume: precisionEnemy=1 in the profile and "_unit setskill ["aimingAccuracy", 0.5]" results in an average value between the two parameters set.

It would be somewhat easy to find out with a script which returns the true value from a unit you are looking at in the editor I guess.

Share this post


Link to post
Share on other sites

okay, thanks, I had thought precisionEnemy in profile no longer had effect since 1.60 based on this

Share this post


Link to post
Share on other sites

Hmm I still have the values in my config which was made before 1.60. But the sliders are indeed gone in 1.62.

Question is now if the values are still read when added manually to the config.

Share this post


Link to post
Share on other sites

I think the bug was that the precision value was never read or read incorrectly, so it was removed altogether.

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×