OpenXcom Forum

Modding => OpenXcom Extended => OXCE Suggestions DONE => Topic started by: Finnik on December 30, 2021, 12:57:04 am

Title: [DONE][SUGGESTION] More precise define enemy count in alienDeployments.data
Post by: Finnik on December 30, 2021, 12:57:04 am

We currently can specify `lowQty`for 0 difficulty and `highQty`for 5th, that assumes linear approximation of enemy count for other difficulties. I would like to suggest a new optional property 'medQty` that would specify Veteran difficulty enemy count, thus we could make nonlinear difficulty rise, with, for example, small grow on beginner-veteran and more rapid on experienced-superhuman. If not specified ('medQty` <= 0) we use vanilla logic.
To me, it looks like a tool to design a more precise balance for missions.

Title: Re: [SUGGESTION] More precise define enemy count in alienDeployments.data
Post by: Meridian on December 30, 2021, 10:20:17 am

Sounds OK.

Current formulas are:

beginner = lowQty
experienced = lowQty
veteran = lowQty + (highQty-lowQty)/2
genius = lowQty + (highQty-lowQty)/2
superhuman = highQty

What would the formulas look like after adding medQty?

Title: Re: [SUGGESTION] More precise define enemy count in alienDeployments.data
Post by: Finnik on December 30, 2021, 02:05:35 pm

Hm, there are multiple options... The first one is obvious:

Code: [Select]

beginner = lowQty
experienced = lowQty
veteran = medQty
genius = medQty
superhuman = highQty

Thus, `highQty` could be set to some really high value that represent challenge, but without effect on veteran or genius.

I guess, if we choose to keep vanilla formula on 'medQty` <= 0 we can also alter vanilla results with

Code: [Select]

beginner = lowQty
experienced = lowQty + (medQty-lowQty)/2
veteran = medQty
genius = medQty+ (highQty-medQty)/2
superhuman = highQty

Not sure if I like the second option... Tho it shows more smooth transition over difficulty levels, it changes the way things work and also leads to less clear logic in code. Anyway, I would be with both options.

Title: Re: [SUGGESTION] More precise define enemy count in alienDeployments.data
Post by: Meridian on December 31, 2021, 07:36:20 pm

Option #2 was implemented.

Title: Re: [DONE][SUGGESTION] More precise define enemy count in alienDeployments.data
Post by: Finnik on December 31, 2021, 07:51:48 pm

Nice, thanks! I already grabbed those  ;) Looking forward to getting it in ruleset reference too!  :)

Title: Re: [SUGGESTION] More precise define enemy count in alienDeployments.data
Post by: Ethereal on January 20, 2022, 03:16:54 pm

Quote from: Meridian on December 31, 2021, 07:36:20 pm

Option #2 was implemented.

It is possible to specify?

Code: [Select]

      - alienRank: 5
        lowQty: 10
        medQty: 12
        highQty: 14
        dQty: ??? (0? 2? 4?)

Title: Re: [DONE][SUGGESTION] More precise define enemy count in alienDeployments.data
Post by: Meridian on January 20, 2022, 03:23:10 pm

I don't understand the question

`dQty` didn't change at all, it works the same as before

Title: Re: [DONE][SUGGESTION] More precise define enemy count in alienDeployments.data
Post by: Ethereal on January 20, 2022, 03:31:14 pm

That there is such a combination does not cause problems and will work?

Code: [Select]

      - alienRank: 5
        lowQty: 10
        medQty: 12
        highQty: 14
        dQty: 0

Title: Re: [DONE][SUGGESTION] More precise define enemy count in alienDeployments.data
Post by: Meridian on January 20, 2022, 03:36:31 pm

All combinations will work.

The only case where it will fail is when you use a negative value for `dQty`.