Genjiro
Lead Game Master
- Joined
- Aug 8, 2022
- Messages
- 249
- Reaction score
- 139
- Server
- Aeria
- Main Pilotname
- Genjiro
Hello all,
First of all congratulations @Kiloker on winning the OTB despite the odds!!, however what you have described is not an issue at all in my opinion. The winning team did win less cryonite overall in this scenario which looks bad on paper but let me try to convince you that this is fine.
We know the cryonite bonus depends on the number of active pilots which increases with each player increment.
Here's a graph showcasing the cryonite winnings for a hypothetical score of 100% to 0%. (Link to source)
Now this curve is obviously not the same for your score in question but it should give a general idea on the cryonite rewards scaling for each additional active player.
A major reward from conquests that we are ignoring is the gravitons won by the winning team which is certainly a solid amount per pilot for 45min of PvP. I am not going to count the added benefit of progressing conquest planet win achievement but it is undeniably a benefit regardless.
I have gone through the OTB Stats page of @KillerSoldier_ (Very informative page that I encourage others to check out), And the last OTB on Askone where 2 players were counted inactive on the same side was on 1st of August 2023, which does show this scenario is quite a rare case and not something that needs urgent attention.
This type of situation would not arise in a clan vs clan conquest since most clans choose their best players who will more or less stay active, clan leaders can opt to not select players who go inactive to better their winning chances.
Since the same system is used in OTB's but without the controlling factor I can see why there is a general dissatisfaction in lieu of randomized teams and the seeming unluckiness of being paired with inactive teammates.
The statement that players incur a 7 day ban when they don't land, but aren't penalized while inactive on the surface is correct. This I agree needs to be changed and I will certainly bring the topic forward to the devs. It should also mitigate the actual problem which is throwing/purposeful inactivity.
Greetings,
Genjiro.
First of all congratulations @Kiloker on winning the OTB despite the odds!!, however what you have described is not an issue at all in my opinion. The winning team did win less cryonite overall in this scenario which looks bad on paper but let me try to convince you that this is fine.
We know the cryonite bonus depends on the number of active pilots which increases with each player increment.
Here's a graph showcasing the cryonite winnings for a hypothetical score of 100% to 0%. (Link to source)
Now this curve is obviously not the same for your score in question but it should give a general idea on the cryonite rewards scaling for each additional active player.
A major reward from conquests that we are ignoring is the gravitons won by the winning team which is certainly a solid amount per pilot for 45min of PvP. I am not going to count the added benefit of progressing conquest planet win achievement but it is undeniably a benefit regardless.
I have gone through the OTB Stats page of @KillerSoldier_ (Very informative page that I encourage others to check out), And the last OTB on Askone where 2 players were counted inactive on the same side was on 1st of August 2023, which does show this scenario is quite a rare case and not something that needs urgent attention.
This type of situation would not arise in a clan vs clan conquest since most clans choose their best players who will more or less stay active, clan leaders can opt to not select players who go inactive to better their winning chances.
Since the same system is used in OTB's but without the controlling factor I can see why there is a general dissatisfaction in lieu of randomized teams and the seeming unluckiness of being paired with inactive teammates.
The statement that players incur a 7 day ban when they don't land, but aren't penalized while inactive on the surface is correct. This I agree needs to be changed and I will certainly bring the topic forward to the devs. It should also mitigate the actual problem which is throwing/purposeful inactivity.
Greetings,
Genjiro.
Last edited: