w3champions / w3champions-issues Goto Github PK

Currently, each player in a team game plays an artificial solo vs an opponent of rating (sum of opponents' ratings - sum of allies' ratings) - this is equivalent to:
current rating + (arithmetic mean of ratings for oppo team - arithmetic mean of ratings for own team)

It should be changed to:
current rating + (geometric mean of ratings for oppo team - geometric mean of ratings for own team)

this will be consistent with the formula we use for matchmaking and team balancing

If Flo is not working, matchmaking with server option -FLO AND BNET leads to alert about disfunction of FLO. After that Matchmaking Button is freezed and iddle at option CHECKING FLO. This button state persists even after switching server option to BNET ONLY and returning to Main Warcraft3Reforged Menu.

When you leave a game before it's really over and in the meantime you're also able to find a new one, your MMR gets updated only taking into account the second, as if the first never happened.

https://docs.google.com/document/d/1oUSc74F75lISwgYPvSD2wkXbaX1zDH6ykzqkY5DdN-0/

During waiting for teammate there is no cancel
The only way = restart WC3

Even if your ally left group you're still waiting for teammate and can't cancel = should restart

Alike

The latest patch brought an update to CH, we should then update our w3c version accordingly.

Current issues:

1. There's very little variety in terms of unit skin colors:
   a. 1vs1: always red vs blue
   b. 2vs2/FFA: always red/blue (vs) teal/purple
   c. 4vs4: always red/blue/teal/purple vs yellow/orange/green/pink
   d. certain players always tend to have the same color because of MMR sorting
2. Default colors make the game harder to read, because they don't respect any "theme" (e.g. warm/cold) within the same team:
   a. 2vs2: by default, team 1 has one warm color (red) and one cold color (blue)
   b. 4vs4: team 1 has one warm color (red) and three cold colors; team 2 three warm and one cold (green)
   c. team colors (blue self, teal allies, red enemies) help overall readability, but still don't make it easier to distinguish single players within the same team. It's especially a problem in 4vs4 games, where you have to immediately react and coordinate with your allies to deal with enemy pushes

Suggestions for default colors to improve in-game readability:

1. 1vs1/FFA: randomize colors among the following: red, blue, teal, purple, yellow, orange, green, pink
   a. classic BNet feature, these 8 colors are different enough to discern your own units from your opponent's
   b. it's still possible to go for blue/red by enabling the team colors mode (or even other combinations thanks to the W3Champions launcher)
2. Team games. Note that it's not mandatory for team 1 to always have warm colors, it can also be vice versa.
   a. 2vs2:
   i. randomize two colors among the following for one of the two teams (warm colors): red, orange, yellow
   ii. randomize two colors among the following for the other team (cold colors): blue, teal, purple
   b. 4vs4:
   i. colors for players belonging to one of the two teams (random order, warm colors): red, orange, yellow, pink
   ii. colors for players belonging to the other team (random order, cold colors): blue, teal, purple, green

When you're selected as the host and the game ends up having a bad ping issue, normally it helps to restart the game. So it makes sense to label the game host with the "w3c crown" instead of yourself.

You can now vote -ff in 4v4 RT with a 3 min CD
If -ff vote completes on team game ends and voting team gets loss other team gets win
If -ff vote completes you are immune to being reported for leaving
If you leave without using -ff vote it's at your own risk

https://discordapp.com/channels/688377338576109643/765623167808831539/768450988691685377

the package map still V10 V11 , but now is V14...........

The old Battle.Net had the handy feature to maximize the game once an opponent is found. Could this be implemented in W3Champions?

I recently watched a replay where my opponent typed -zoom 2000 and W3C set my actual zoom value to this value. Also this custom zoom level which was not mine got applied automatically for me in every new game. Typing zoom -1650 fixed this.

A better solution would perhaps be to use the local players custom zoom level in both replays and ingame, but to not apply custom zoom levels from replays.

Hi there,

appreciate your work! sorry if this isn't really an issue with any of the software

is there a complete list of tcp/udp ports that required to play on w3champions? Im routing all traffic through a VPN and would like to set up some rules to bypass VPN for w3champions.

thanks

Hello team,

Would like JIRA access to find some issues to play with. Don't want to scope out work that is in progress!

Thanks!

Heys

I've testing the inventory and hotkeys on OSX, and it seems not working

Another issue is when I enable it , esc also does no work

related to #1
(first issue should be closed tho as far as I understand since it's using geomean already there)

https://www.microsoft.com/en-us/research/project/trueskill-ranking-system/?from=http%3A%2F%2Fresearch.microsoft.com%2Fen-us%2Fprojects%2Ftrueskill

Glicko was developed as an extension of ELO and was thus naturally limited to two player matches which end in either win or loss. Glicko cannot update skill levels of players if they compete in multi-player events or even in teams. The logistic model would make it computationally expensive to deal with team and multi-player games. Moreover, chess is usually played in pre-set tournaments and thus matching the right opponents was not considered a relevant problem in Glicko. In contrast, the TrueSkill ranking system offers a way to measure the quality of a match between any set of players.

• code: https://github.com/sublee/trueskill
• old C# realization maybe could be useful too: https://github.com/moserware/Skills

Side note: we could also consider placing FFA maps into a sub-folder for next season or add an FFA label somewhere so that people the map is not meant for team games but just FFA (f.e., W3C/v6/FFA instead of W3C/v6)

Due to the low number of games, it's been suggested we relax the matchmaking requirements on NA for team games.

(In game lounge)
Chat scrolls to the bottom automatically when there are new messages.
But once you scroll a bit, it stops working even though you put the scroll back on the bottom.

It must detect that the user put the scroll back on the bottom so it starts auto-scrolling again.