Discord bot

[Diablo_]

Found a bug and fixed it.
")" in fijis name (and some other special characters) wasn't handled properly so he could sign whenever he wanted to.
Should work correctly now.

[Diablo_]

Update to compare:

you can now use it with only one name and it will use your own one as second one (thx to jamo for the idea).
e.g.
!compare ba_fail
would compare me and ba fail

protip: compare with yourself to see how many of your last games are tracked.

[smokedope123]

Found a bug and fixed it.
")" in fijis name (and some other special characters) wasn't handled properly so he could sign whenever he wanted to.
Should work correctly now.

@ZTX)Fiji @ZTX)Fiji @ZTX)Fiji @ZTX)Fiji @ZTX)Fiji @ZTX)Fiji

ahahahhaha I knew you were hacking motherfuckre xdddd

[Mind]

this cant go unpunished. dia, do your job!!!!

[Diablo_]

@hazardous
@snowblind
@tom_hardy
@iamyoursenpai

Since the stats aren't recorded currently, games can now be recorded by LIHL mods via the discord bot. There are two commands:
!updatestats <gameid> <winner>
!reverseupdatestats <gameid> <winner>

e.g. for this game: https://entgaming.net/findstats.php?id=10596522

!updatestats 10596522 west:
Gives 15 elo to ilo and me and adds 1 win
Takes 15 elo from n1ll3 and artmas and adds 1 loss

!updatestats 10596522 east:
Gives 15 elo to n1ll3 and artmas and adds 1 win
Takes 15 elo from ilo and me and adds 1 loss

!reverseupdatestats 10596522 west:
Takes 15 elo from ilo and me and removes 1 win
Gives 15 elo to n1ll3 and artmas and removes 1 loss

!reverseupdatestats 10596522 east:
Takes 15 elo from n1ll3 and artmas and removes 1 win
Gives 15 elo to ilo and me and removes 1 loss


Normal usage:
Only use !updatestats <gameid> <winner> exactly once.
!reverseupdatestats is only there to fix wrong usage (e.g. updating stats for the same game twice, updating stats for a game which was drawn etc.)

Normal bot response:
[20:20] BOTSystem: Diablo_ updating stats for game ID: 10596522 with winner: east
[20:20] BOTSystem: Updated Elo/wins/losses for player [artmas]: 15/1/0
[20:20] BOTSystem: Updated Elo/wins/losses for player [diablo_]: -15/0/1
[20:20] BOTSystem: Updated Elo/wins/losses for player [ilocos_norte]: -15/0/1
[20:20] BOTSystem: Updated Elo/wins/losses for player [n1ll3]: 15/1/0


Note that both commands can be used multiple times and have no knowledge of each other, i.e. you can use !reverseupdatestats on a game which wasn't even updated before (of course you shouldn't do that).
Also note that usage of the command is logged so any abuse can be easily detected (we will check for it regularly).

I tried to make it as fool proof as possible and I hope everything is clear, if not just hit me up.

Now you just need to:
1) decide if and if so starting with which time you want to update stats
2) find out which team has won when updating the stats: since stats aren't recorded there's also nowhere visible which team has won and replays are also not available. This means you will need players to tell you who won (e.g. make a thread where people have to post the game id + winner team)

[FadingSuns]

i appreciate that work diablo bit seems like a mess and a lot extra work for mods... Cant we live without elo until stable solution is found?.

Rather than having 1000 topics posted for mods to manual process this... idk

[inQ]

@diablo

Any way to reset !compare function for the new season? Or are going to keep it rolling?

[Diablo_]

@diablo

Any way to reset !compare function for the new season? Or are going to keep it rolling?

It is just fetching all saved game data from the Ent database which (currently) always is a sliding window of ~3 months. I can't really make it to show the current season only, but what would be an option is to allow players to specify how many days should be considered.

i.e.
!compare a b -> compare with all saved games
!compare a b 20 -> compare with saved games of the past 20 days only

Do you think that would be useful?

[inQ]

@diablo

Any way to reset !compare function for the new season? Or are going to keep it rolling?

It is just fetching all saved game data from the Ent database which (currently) always is a sliding window of ~3 months. I can't really make it to show the current season only, but what would be an option is to allow players to specify how many days should be considered.

i.e.
!compare a b -> compare with all saved games
!compare a b 20 -> compare with saved games of the past 20 days only

Do you think that would be useful?

Appreciate it Dia but I don't think that would be necessary unless people want it. I just thought compare function was a fun way to gauge chemistry with certain players during a particular season but no need for you to write new codes for it. Thanks for the hard work as usual.

[smokedope123]

please implement !challenge

[Diablo_]

Added challenge mode.

!challenge x (=4vs4)
!challenge2 x
!challenge3 x
!challenge4 x

!accept

!sign
!sign
!sign
...

!pick a
!pick b
!pick c
...

Pick mode is 1-2-2-2-1, the first picker is random. Game gets canceled after 1 minute of inactivity (i.e. 1 min no accept = cancel, 1 min no sign = cancel, 1 min no pick = cancel). If the challenger or the challengee unsigns the game also gets canceled. Games are hosted as lihlc..., so they are 15/15 Elo games.

If you notice any problems or have suggestions pm me.

[Jamo]

Dude, that's greeeaaattt!!

[Jamo]

How does it work though? Others should have to sign first somehow?

[Diablo_]

Forgot to show the sign part

!challenge x (=4vs4)
!challenge2 x
!challenge3 x
!challenge4 x

!accept

!sign
!sign
!sign
...

!pick a
!pick b
!pick c
...

[smokedope123]

Thanks for the great job and your effort here @Diablo_ !

Just a suggestion on the timers... I agree to 1min accept timer, but shouldn't the other timers be increased to at least 3 min or so?
I'm sure like this the games would be cancelled unintentionally occasionally due to people being slow at deciding who to pick i.e.