[MOD] for IL2 stats system - more options for disconnection situations

[CountZero]

In original Vaal and Isay IL2 stats system any disconnection in game is considered as disco sortie, no mather if someone is at that moment shooting at you or its random disconnect. And attacker who damaged disconnecting player will not get airplane kill for him.

In this mod i make this changes:

1)

If player disconnected and someone damaged his airplane, player who damaged him will get that kill (like its now in game).

2a)

When player disconnected, and his airplane is damaged short time before disconnection, hes sortie is considered captured sortie. Server host can set what that time can be in its "conf.ini" , with "sortie_damage_disco_time = 120" ( by default i set it to 120s, if you wont to not use this option just set it to 1). 

I belive this addition is neccesary because this situation has high probability of intentional disco, to avoid geting killed/captured. Now with this option player will not be able to avoid getting his virtual life to end, K/D lowered, ranks points lowered and so on... Aditionaly if for any reason you as server host need also to set at what amount of damage to airplane this option activates, you can do so in "report.py" file in "def event_player_disconnected" change "dmg_pct=0" to what ever percentage you think is fair (default is 0, so any damage abow 0% activates it).

 

2b)

When player disconnected, and his airplane is damaged, but damaged occured long time before disconnect ( more then time server host set by "sortie_damage_disco_time" ), his sortie will just count as normal disconnection. 

So players who recived damage to airplane, long time ago before disconnection happend in that sortie, dont get aditionaly punished like intentional disconnecters. As probability that he did this intentionaly is not that high.

 

3a)

If players airplane is not damaged, and disconnection happend short time after take off, disco sortie is turned into bailout sortie. This one is good if you have that any disco sortie ends players virtual life (like on WoL for example). There is big probability that player didnt disconnect intentionaly short time after take of while his not damaged and over his front, so why punish him with end of his virtual life if it can be avoided by this setting.

Server host can define time for this option in servers "conf.ini" file, with "sortie_disco_min_time = 0" (by default is 0 seconds, so its not active). As doing it like in option 4 is not posible, this option 3 is best compromise.

 

3b)

If players airplane is damaged but damage is done to it outside of time set by sortie_damaged_disco_time, and disconnection sortie lenght was inside time set by sortie_disco_min_time, then that disco sortie is turned into bailout sortie also.

4) *Not able to do from what i know, POS on disconnect is (0,0,0,0 - post if you know way to do it):

Make that when player disconnected, and no damage is done to his airplane and his airplane position at time of disconnect was over frendly side, his sortie will be considered like he bailout, and if it happend over enemy side its considered as normal disco.

I think this should be more fair system then how its now, and server host have options to use what he wonts how he wonts it on his server.

 

Link for mod version 1.7.3 (its important that you dont just copy/paste whole "conf.ini" file, just make same edit to your server conf.ini file, works with original IL2 stats 1.2.71 version): https://www.mediafire.com/file/hiaeh0fznfzp1ml/discomodv1.7.3.zip/file

 

previous version:

Spoiler

https://www.mediafire.com/file/0memhd7826gjqc9/discomodv1.6.1.zip/file

https://www.mediafire.com/file/t4gyfbfrjbqhgaq/discomodv1.7.zip/file

 

Edited files:

-in src folder: conf.ini, config.py 

-in stats folder: models.py, sortie_log.py, stats_whore.py

-mission_report folder: report.py

 

For TANKS stats version:

This mod works with tank stats mod, aditionaly to airplane disco changes it also changes tank sortie where player got damaged just before he exit sortie (by default is damage in 120s before player exit or disconects) or he disconected, to capture sortie, Vlife ends and attacker get kill, tank lost.

If he bails out after damage, then its normal bailout sortie, attacker get kill, tank lost, Vlife dont end. So players should bail out insted just finish flight.

Also damage from colisions with objects dont activate this switch. And mission crash or end also dont activate change.

If damage is done outside of this 120s, sorties will just be considered as in service/normal , and no kill to player who damaged tank, no tank lost.

Link for mod version 1.0 (its important that you dont just copy/paste whole "conf.ini" file, just make same edit to your server conf.ini file, works with original IL2 stats 1.2.71 version):   https://www.mediafire.com/file/37qr8w36jkd4rwq/tankdiscomodv1.0.1.zip/file

 

 

In original stats it looks like this:
Pic1:

Spoiler

 

Pic2:

Spoiler

 

With mod i used; sortie_damage_disco_time = 60 , sortie_disco_min_time = 100 , and this is how then same sorties look:
Pic 3:

Spoiler

Pic 4:

Spoiler

 

On pic 1 two bailout sorties (Bf-109K4 and Fw190D9) were disco in original, but as their time betwen take off and disconnection is less then 100s, they are now bailout sorties like shown on pic 3.
Same happends with Yak-1b and La5 sorties on pic 2, time is shorter then 100s , so they are considered bailout , pic 4. 

On pic 4 you can also see that disco sorties from pic 2 are turned now in capture sorties in cases where airplane was damaged in time under 60s (2xJu87 and 1xBf110 sortie).  And disco sortie on pic 2 an pic 4 for Bf109G14 counts as normal disco as last damage to airplane is done 174s before disco.

 

Example of two sorties where damaged to airplane is done before disco, i changed sortie_damage_disco_time = 5:
This sortie is normal disco as damage is done 6s before disco:

Spoiler

And this one is considered capture as damage is done in 5s before disco:

Spoiler

You can also see on both cases event "WAS SHOTDOWN" now shows up at time of disconection, and kill goes to who damaged disconnect player and is also added to killboard win/lost.

 

From mod version 1.4, event "DISCONNECTED" also shows up in sortie log of player who disconnected, at time of disconnection.

Spoiler

 

 

 

 

Post here if you see any problems or get any errors with it or if you see better way to do it, i tested it as mutch as i could and im not coder so i did best i could as for long time nothing was done regarding this problem.

Edited April 18, 2023 by CountZero
new version 1.7.3 and new version for tanks disco/exit v1.0.1

[FTC_Riksen]

@77.CountZero

 

Great addition! I hope all servers use your mod for the stats system.

 

Cheers

[CountZero]

Atleast there is more options now with it if they decide to use it, and with added sortie_damage_disco_time and sortie_disco_min_time they can set it how they wont.

 

They should just not say what times they use, if they use thouse options. Because if players know exactly up to what second he can disco and be counted as bailout insted, he can quickly strike targets and just disco over enemy side if time is long enought to avoid capture and get points also. 

Or if damage time is to short, he can know that he needs for example glide in damaged airplane over enemy front for certen amount of seconds, and then disco to avoid capture and be disco or bailout ( what ever server set). If players know what times servers use for thouse options they will probably abuse it.

 

Or you can not even use any of that stuff , and have it like its in original, but atleast with mod files player who damaged disconecter will get kill for him when disco happends, like its in game.

Edited December 6, 2019 by 77.CountZero

[CountZero]

version 1.2 of mod is in first post, 

 

I noticed with more tests, that change i did for disco player to get shotdown when damaged and to give kill for that, was making also situation when you rtb and was damaged in that sortie to also give a kill when it should not give kill. 

So i fix that with this changes to report.py file in version 1.2. Now disco and damaged give kill to attacker, and rtb works as in original ( not give kill when you land at home base).

I tested also if situation when your damaged and in air at mission end, or server crashes and your in air, is same like in original and not effected by changes neccesary for disco kill, and it works like in original, your in flight and dont give kill for just being damaged. 

Edited December 9, 2019 by 77.CountZero

[Alonzo]

Thanks for this, CountZero. I have been needing something like this for a while. I will look at implementing it on Combat Box.

 

Here is a "patch" version of your mod. It is in "unified diff" format and will be a bit more portable. I generated it by diffing the original IL2 stats 1.2.38 against a copy with your changes applied. Combat Box already modifies some of these files, so for me the patch file works better, as I can apply it to incorporate your changes into my modified IL2 stats.

 

 

discomod-1.2.zip

[CountZero]

4 hours ago, Alonzo said:

Thanks for this, CountZero. I have been needing something like this for a while. I will look at implementing it on Combat Box.

 

Here is a "patch" version of your mod. It is in "unified diff" format and will be a bit more portable. I generated it by diffing the original IL2 stats 1.2.38 against a copy with your changes applied. Combat Box already modifies some of these files, so for me the patch file works better, as I can apply it to incorporate your changes into my modified IL2 stats.

 

 

discomod-1.2.zip 2.51 kB · 0 downloads

 

Thanks for sharing it, its probably faster to implement changes from edits in mod that way

[Alonzo]

Just to add, we’ve implemented this on Combat Box and it seems to be working. Players are appreciative! Thanks!

[CountZero]

10 hours ago, Alonzo said:

Just to add, we’ve implemented this on Combat Box and it seems to be working. Players are appreciative! Thanks!

 

Thanks for testing it, i think i se problem:

http://combatbox.net/en/sortie/log/288468/?tour=17

http://combatbox.net/en/sortie/288468/?tour=17

 

I belive this should be player in flight at end of mission. Would be in flight sortie in original, and here i see its shotdown as he got damaged before mission end. His sortie end time is same as that mission end time.

http://combatbox.net/en/mission/3598/

 

I belive this mission is after you started to use this mod, if yes, then he got shotdown status because of changes i did to get kill to attacker when player disconected in report.py in def killed_by_damage.

 

Can you send me mission reports from that mission, so i can use it to test and see how to eliminate this and still keep that when disco player is damaged guy who attack him gets kill for disco player.

 

To prevent this from happening again (untill i fined differant way to get kill to attacker for disco guy), in report.py just remove this 2 lines or place # infront of them:

            if not self.is_rtb:
                self.got_killed(force_by_dmg=True)

 

I tested that situation before, and it was not giving shotdown status when player was damaged and in flight at end of mission, so i tought this situation is not changed with my edits, but from that sortie it looks like it did change if you started using mod edits before that mission.

Edited January 5, 2020 by CountZero

[CountZero]

I think this change should fix problem that i see in that sortie, 

in report.py for line 677 i add: and not self.is_ended   

, so it looks like this:

 

            if not self.is_rtb and not self.is_ended:
                self.got_killed(force_by_dmg=True)

 

and also i add in report.py in line 491: 

        self.is_ended = False

 

i see it works in giving kill to attacker for disco damage, and dosent effect any of the test missions i have, but to be sure it works i would need your missionReport for that mission http://combatbox.net/en/mission/3598/ to see if this will eliminate shotdown from situation when mission ends and player is in flight but got damaged at any point.

[Alonzo]

1 hour ago, CountZero said:

to be sure it works i would need your missionReport for that mission http://combatbox.net/en/mission/3598/ to see if this will eliminate shotdown from situation when mission ends and player is in flight but got damaged at any point.

 

Hi there. I think it's one of these two. I'm not sure which, sorry!

missionReport(2020-01-03_09-59-26)[0].txt.zipmissionReport(2020-01-02_18-58-18)[0].txt.zip

 

I also got a similar report from one of our players for a later mission. 

 

Sortie on IL2 stats: http://combatbox.net/en/sortie/log/292559/?tour=17

(hopefully) mission log: missionReport(2020-01-04_21-46-01)[0].txt.zip

[CountZero]

40 minutes ago, Alonzo said:

 

Hi there. I think it's one of these two. I'm not sure which, sorry!

missionReport(2020-01-03_09-59-26)[0].txt.zip 226.47 kB · 1 download missionReport(2020-01-02_18-58-18)[0].txt.zip 464.4 kB · 1 download

 

I also got a similar report from one of our players for a later mission. 

 

Sortie on IL2 stats: http://combatbox.net/en/sortie/log/292559/?tour=17

(hopefully) mission log: missionReport(2020-01-04_21-46-01)[0].txt.zip

 

Thanks thats the missions, i try them and i get same resoult, and then i try add what i tought would fix probem, but it didnt work, so ill keep trying other stuff untill i fined what works. For now, you can just remove problematic lines from report.py , so others dont get shotdown resoult when damaged on mission end.

Edited January 5, 2020 by CountZero

[CountZero]

still not able to make it work so kill is not given if player is in air and damaged at end of mission.

I was able to make changes so atleast his sortie is not turned in lost airplane and shotdown, but he would still give a kill to guy who damaged him.

Im not able to make is_ended (what i see is differant betwen disco and in flight sorties) to work in class Object section, it works in Sortie class section, and other things like killed_by_damage dont work in other class sections wher i try to use it for damageddisco sorties only, so im still trying to see how to make it so kill is only reword when disco player is damaged, and not also when damaged but in flight at mission end.

Edited January 7, 2020 by CountZero

[CountZero]

On 1/5/2020 at 4:24 PM, Alonzo said:

 

...

 

Was going no where for few days and had to do brake and do something els to get fresh start, try again today few comnbinations and i think i found one that works :

 

if in "report.py" file in "def killed_by_damage(self, dmg_pct=0)" section, insted this 2 lines i added for mod:

            if not self.is_rtb:
                self.got_killed(force_by_dmg=True)

 

i use this:

            if self.sortie and not self.is_rtb:
                if not self.sortie.is_ended:
                    self.got_killed(force_by_dmg=True)

 

i get kills/shotdowns for damaged players when they disconect only, and i dont get kills/shotdown when players are damaged but in air at mission end like it was on thouse problematic missions when you run mod on server. I try my test missionsreports and all the ones you send me from your server and it seams all looks like it should from start now. Its late so ill do more test tomorow and recheck all sorties just to be sure it works ok now, and then update mod with fix.

[CountZero]

I check today missions on original stats and then compared them to stats with mod and it looks like fix works as intended so i updated first post with mod v 1.3

Post if you test it on your server and if there is any problems with it, from what i see it should work as planed from start now.

 

EDIT:

checking your server forum i see player got reported for disco when in df, and i see his sortie is turned into capture insted disco as he was damaged short before disco, and his virtual life ends and ranking points go down also.

http://combatbox.net/en/sortie/log/313359/?tour=17

http://combatbox.net/en/sortie/313359/?tour=17

so it seams that edit in mod works as planed and player gets penalised automaticly

Edited January 18, 2020 by CountZero

[Alonzo]

5 hours ago, CountZero said:

I check today missions on original stats and then compared them to stats with mod and it looks like fix works as intended so i updated first post with mod v 1.3

Post if you test it on your server and if there is any problems with it, from what i see it should work as planed from start now.

 

EDIT:

checking your server forum i see player got reported for disco when in df, and i see his sortie is turned into capture insted disco as he was damaged short before disco, and his virtual life ends and ranking points go down also.

http://combatbox.net/en/sortie/log/313359/?tour=17

http://combatbox.net/en/sortie/313359/?tour=17

so it seams that edit in mod works as planed and player gets penalised automaticly

 

Thanks CountZero! I have applied your latest 1.3 mod to the Combat Box server, as of now. Thank you for checking and doing the work on this. Hopefully this improves pilot experience for that last-minute map end scenario.

@CountZero Can I check my report.py contains the right code? This is what I have now:

 

    def killed_by_damage(self, dmg_pct=0):
        if not self.is_killed and (self.damage > dmg_pct or self.is_captured):
            # если самолет приземлился не в зоне своего филда или пилот выпрыгнул или пилот мертв
            # - записываем его как сбитый
            if (self.on_ground and not self.is_rtb) or self.is_bailout or (self.bot and self.bot.life_status.is_destroyed):
                self.got_killed(force_by_dmg=True)
            # in case of disconection - the player who damaged him gets kill, when damage occurs at any time in flight
            if self.sortie and not self.is_rtb:
                if not self.sortie.is_ended:
                    self.got_killed(force_by_dmg=True)

 

[CountZero]

Yes that should be correct, last 3 lines are change that works to give shotdown only when disconected under fire when i try it on test server and with missionreports, and not when player is damaged and in air at mission ends.

[CountZero]

I check your last mission and it looks like fix works ( i guess v1.3 was applayed before that mission ended)

mission ended at 20:03

http://combatbox.net/en/mission/3750/

 

3 examples of in flight at end of mission and damaged:

http://combatbox.net/en/sortie/log/317742/?tour=17

http://combatbox.net/en/sortie/log/317740/?tour=17

http://combatbox.net/en/sortie/log/317666/?tour=17

http://combatbox.net/en/sortie/log/317770/?tour=17

in all cases their sortie is counting as in flight , and no kill/shotdown is given like it would be  before fix.

 

now ill check if i can fined some disco sortie where player was damaged to see if attacker got kill/shotdown for him.

 

 

edit:

found one:

http://combatbox.net/en/sortie/log/317667/?tour=17

disconection when damaged ( his last damage event happend inside time you set in sortie_damage_disco_time , and then his sortie is turned in captured from normal disco), and his attacker gets the kill like it should with this mod:

http://combatbox.net/en/sortie/log/317687/?tour=17

 

Also i see disco where last damage hapend outside time you set in sortie_damage_disco_time so his sortie stays normal disco, as its probably not intentional one.

http://combatbox.net/en/sortie/log/317668/?tour=17

 

good to see that also works like planed.

 

So it seams all works as it should, post if you get players reporting any strange behaviors in their stats that could be resoult of this mod, and again thanks for trying it out.

 

Edited January 18, 2020 by CountZero

[CountZero]

Small change in mod version 1.4, i added so event disconnected show up in players sortie log at time of disconnection from server. 
So its now easyer to know that disconnection happend in sortie where disconnection is turned in capture or bailout for example.

 

Pictures how it looks:

Spoiler

 

 

 

 

 

 

 

Changed files from 1.3 are: report.py, sortie_log.py and stats_whore.py 

Spoiler

in report.py self.logger_event({'type': 'disco', 'sortie': sortie}) is added on 2 places in event_player_disconnect, it should look like this:

    def event_player_disconnected(self, tik, account_id, profile_id):
        # self.online_uuid.discard(account_id)
        sortie = self.sorties_accounts.get(account_id)
        # TODO работает только в Ил2, в РОФ нет такого события
        if sortie:
			# you can determine the amount of damage that is considered
            dmg_pct=0
			# the departure was completed, there was a jump, no plane was created, the plane on the ground, and the plane was damaged,
			# player disconection can then be changed into captured.
            if not (sortie.is_ended or sortie.is_bailout or (not sortie.aircraft) or sortie.aircraft.on_ground ) and sortie.aircraft.damage > dmg_pct:
                sortie.is_damageddisco = True
                self.logger_event({'type': 'disco', 'sortie': sortie})
            # вылет был завершен, был прыжок, не был создан самолет, самолет на земле
            elif not (sortie.is_ended or sortie.is_bailout or (not sortie.aircraft) or sortie.aircraft.on_ground):
                sortie.is_disco = True 
                self.logger_event({'type': 'disco', 'sortie': sortie})

in sortie_log.py , changes are  'disco': pgettext_lazy('sortie_log', 'DISCONNECTED'), and 'disco': 'grey', is added, it should look like this:

messages_wo_opponent = {
    'act': {
        'respawn': pgettext_lazy('sortie_log', 'respawn'),
        'end': pgettext_lazy('sortie_log', 'end'),
        'disco': pgettext_lazy('sortie_log', 'DISCONNECTED'),
        'takeoff': pgettext_lazy('sortie_log', 'takeoff'),
        'landed': pgettext_lazy('sortie_log', 'landed'),
        'crashed': pgettext_lazy('sortie_log', 'crashed'),
        'ditched': pgettext_lazy('sortie_log', 'ditched'),
        'bailout': pgettext_lazy('sortie_log', 'BAILOUT'),
    },
    'cact': {
        'damaged': pgettext_lazy('sortie_log', 'damage'),
        'wounded': pgettext_lazy('sortie_log', 'wound'),
        'killed': pgettext_lazy('sortie_log', 'DIED'),
        'destroyed': pgettext_lazy('sortie_log', 'DISABLED'),
        'shotdown': pgettext_lazy('sortie_log', 'DISABLED'),
    },
}


@functools.lru_cache(maxsize=64)
def get_message(act_type, event_type, has_opponent=True):
    if has_opponent:
        return messages[act_type][event_type]
    else:
        return messages_wo_opponent[act_type][event_type]


colors = {
    'act': {
        'respawn': 'grey',
        'end': 'grey',
        'disco': 'grey',
        'takeoff': 'grey',
        'landed': 'green',
        'crashed': 'orange',
        'ditched': 'orange',
        'bailout': 'orange',

        'damaged': 'green',
        'wounded': 'green',
        'killed': 'green',
        'destroyed': 'green',
        'shotdown': 'green',
    },
    'cact': {
        'damaged': 'red',
        'wounded': 'red',
        'killed': 'red',
        'destroyed': 'red',
        'shotdown': 'red',
    },
}

 

and in stats_whore.py, in def stats_whore(m_report_file): , in for event in m_report.log_entries , this 4 lines are added in 314, 315, 316 and 317:

        elif event['type'] == 'disco':
            params['type'] = 'disco'
            params['act_object_id'] = event['sortie'].sortie_db.aircraft.id
            params['act_sortie_id'] = event['sortie'].sortie_db.id

 

 

Edited January 19, 2020 by CountZero

[SAS_Storebror]

Hi @CountZero,

I've just recently stumbled upon this mod.

Two questions:

1. Is it possible to get a version compatible with the 1.2.44 update of IL-2 Stats?
2. Maybe it would make sense to create a set of diff files containing all changes necessary to "stock" IL-2 Stats files, so in case an update to IL-2 Stats is being released that touches files of this mod, people could create a patched set of files themselves.

Mike

[CountZero]

Didnt realised there was new update to stats, ill check it out today to see if this mod works with it, i see report.py has updated in 1.2.44 and thats one file i made changes for.

Usealy disconect changes worked without need for updates, only tank mod needed some chnages from time to time as tanks were coming out.

Do you mean something like what Alonzo posted: 

On 1/3/2020 at 4:26 PM, Alonzo said:

Thanks for this, CountZero. I have been needing something like this for a while. I will look at implementing it on Combat Box.

 

Here is a "patch" version of your mod. It is in "unified diff" format and will be a bit more portable. I generated it by diffing the original IL2 stats 1.2.38 against a copy with your changes applied. Combat Box already modifies some of these files, so for me the patch file works better, as I can apply it to incorporate your changes into my modified IL2 stats.

 

 

discomod-1.2.zip 2.51 kB · 5 downloads

I can try to do that, Vall also point me out to some monkey patching for python but still i didnt have will to se how that works for easy moding Il-2 stats.

[SAS_Storebror]

Yes that's exactly what I mean.

Thanks for taking care of this matter 

 

Mike

[CountZero]

I check and only change was tank_id insted parent_id in report.py at event_tank_travel , and not important for function of mod but i updated that file with it so link in first post is now compatible with new IL-2 1.2.44 version of stats. I didnt have time to check how to create diff patch so ill post that when i check how to do it.

Edited August 26, 2020 by CountZero

[CountZero]

Thanks for help with creating diff patch Alonzo and SAS_Storebror, this is patch file i get when i compare clean 1.2.44 IL-2 stats files to discoedits+1.2.44 stats files:

disco-mod-1.4.1.zip

[=FEW=Revolves]

On 12/6/2019 at 3:20 PM, CountZero said:

4) *Not able to do from what i know, POS on disconnect is (0,0,0,0 - post if you know way to do it):

Make that when player disconnected, and no damage is done to his airplane and his airplane position at time of disconnect was over frendly side, his sortie will be considered like he bailout, and if it happend over enemy side its considered as normal disco.

 

 

Hey CountZero - I have an idea here, but I'm not sure if it will work (didn't test):

 

This event might be interesting:

 

def event_pos_changed(self, tik, object_id, pos):
    pass

 

You could add a new field to MissionReport (e.g. self.current_pos), and update self.current_pos with the new pos every time this event is called, as long as the new pos isn't (0,0,0).

 

Assuming the disconnect is one of the last events, then current_pos should have a somewhat accurate position of the player. Passing self.current_pos to is_on_enemy_territory after a event_player_disconnected should then work.

Edited March 10, 2021 by =FEW=Revolves

[CountZero]

Didnt try that, but would there be data on players position in logs at any time ?

i tought log records players position only when player does something (shoot, drop bombs get hit and so on...)

for example: if hes just flying and nothing happends to him for lets say 10min after he drop bombs on some targets in enemy area, and then he gets disconected when hes over frendly area, i was thinking hes last recorded position coordinates (thats not 0,0,0) would be from last time he did something, in this case 10min ago when he attacked targets. 

 

Edited March 11, 2021 by CountZero

[=FEW=Revolves]

I just spent some time looking into it - it won't work I think, the atype of the event is 17:

 

# текущая позиция объекта
# T:58 AType:17 ID:107519 POS(39013.016,45.535,16807.107)
atype_17 = re.compile(r'^T:(?P<tik>\d+) AType:17 ID:(?P<object_id>\d+) POS\((?P<pos>.+)\)$')

 

and I can't find any AType:17 log entry in the test logs I have :<

 

I guess it's something that used to be transmitted, but is not anymore. So you're right, position is only transmitted when the player does somethin.

[CountZero]

Thanks for trying it out.

[=FEW=Revolves]

This message was meant as a DM, please ignore.

 

Edited March 16, 2021 by =FEW=Revolves

[CountZero]

updated first link with small changes to make it compatible with 1.2.54 version of stats

[CountZero]

i updated link to new version 1.6.2, it contains small change to report.py needed for it to be compatable if using latest tank mod version 3.3.

if you dont use tank mod you dont need this version (although it will work on its own also).

Edited August 11, 2021 by CountZero

[CountZero]

=FEW=Revolves found bug in mod where in some situations kill was not rewarded after disco of player, so this new version contains this fix, and also updated report.py file to original 1-2-60 version of stats.

[CountZero]

Updated mod to new stats, only small change is in models.py regarding picture naming of airplanes

[CountZero]

I updated original disco mod to new stats, and i added separate version that is for tanks. This mod works with tank stats mod, aditionaly to airplane disco changes it changes tank sortie where player got damaged just before he exit sortie (by default is damage in 120s before player exit or disconects) or he disconected, to capture sortie.

If he bails out after damage, then its normal bailout sortie. So players should bail out insted just finish flight.

Also damage from colisions with objects dont activate this switch. And mission crash or end also dont activate change. If damage is done outside of this 120s, sorties will just be considered as in service, no kill to player who damaged tank.

 

Link for mod version 1.0 (its important that you dont just copy/paste whole "conf.ini" file, just make same edit to your server conf.ini file, works with original IL2 stats 1.2.71 version):  https://www.mediafire.com/file/p9u0lqq55z0px0y/tankdiscomodv1.0.zip/file

Edited April 14, 2023 by CountZero