greenoaks wrote:HardAttack wrote:betiko wrote:spiesr wrote:The obvious bridge between that idea and the current setup is to simply make it so that you can receive additional diamond medals. So for the rating medal for example, you would get another diamond ratings medal every 1500 ratings beyond the first.
sounds better, mostly because keeping the medals exponential after diamond is ridiculous, we're talking about unique kills here and the more you have the more you will struggle. not to mention that a lot of players foe people when they medal hunt, foe lists for medal hunting could just turn out to be ridiculously high and games really hard to join.
foe is an option for medal hunters to use,
i am not fan of doing it that way but there is no other way to get there...
maybe, something can be done at creation on games, say there is a field once checked/activated, then these games can not be joined by players i already have unique defeats on. This means definition of a new foe list, to be used on medal hunting purposes only. And with this option, you will click/choose games while creating games, this way player is not blocking other players to join in all games but only games he means to medal hunt only.
how will the button know what you are medal hunting for?
say i have defeated you in fog but not trench. how will the button know if i want you to join so i can get trench or not join because i am going for fog?
that button is not neccesaily need to know what medals i am hunting,
i will decide it though, will make some portion of my games clicked/checked to be medal hunting games with the button, so my foes will not be able to join in these games. At this point, foe option should have two levels, medal foe, and full foe. Full foe can not join in any of your games, while medal foes can join unchecked games but can not in checked games. Since it is you creating games, you can pick which games are medal hunting games u r creating.