Loading...
  OR  Zero-K Name:    Password:   

Post edit history

Pitch Some new Maps for Autohost Lobpot Rotation

To display differences between versions, select one or more edits in the list using checkboxes and click "diff selected"
Post edit history
Date Editor Before After
11/28/2022 11:00:11 AMPLrankrookstoo before revert after revert
11/28/2022 10:59:30 AMPLrankrookstoo before revert after revert
11/28/2022 10:58:02 AMPLrankrookstoo before revert after revert
11/28/2022 10:57:06 AMPLrankrookstoo before revert after revert
11/28/2022 10:55:07 AMPLrankrookstoo before revert after revert
11/28/2022 7:38:25 AMPLrankrookstoo before revert after revert
11/28/2022 7:37:54 AMPLrankrookstoo before revert after revert
11/28/2022 7:35:46 AMPLrankrookstoo before revert after revert
11/28/2022 7:33:55 AMPLrankrookstoo before revert after revert
11/28/2022 7:29:48 AMPLrankrookstoo before revert after revert
Before After
1 make following algo: 1 make following algo:
2 \n 2 \n
3 each map has couple of weights to it: 3 each map has couple of weights to it:
4 {{{map_weights[][admin, popular, last]}}} 4 {{{map_weights[][admin, popular, last]}}}
5 admin - weight set over by admin for lobpot pick 5 admin - weight set over by admin for lobpot pick
6 popular - weight using number played count from 0 to 1, counted from game stats each night at midnight over like 30-60 days back. 6 popular - weight using number played count from 0 to 1, counted from game stats each night at midnight over like 30-60 days back.
7 last - last time it was played in days_ago also counted at midnight and normalised to 0-1 range. the language used is rubyish, since it will get into sql, (which i dont do) anyway. 7 last - last time it was played in days_ago also counted at midnight and normalised to 0-1 range. the language used is rubyish, since it will get into sql, (which i dont do) anyway.
8 \n 8 \n
9 and then setup weights for map slots in map clicky thingy, so first one is lobster pot, next are chances of high lobster pot but also popular, 3rd slot is from most played with some chances of popular or lobster pot, and last slot is LEAST played, setting weights for each slot: 9 and then setup weights for map slots in map clicky thingy, so first one is lobster pot, next are chances of high lobster pot but also popular, 3rd slot is from most played with some chances of popular or lobster pot, and last slot is LEAST played, setting weights for each slot:
10 {{{ 10 {{{
11 weights[admin, popular, last] = { 11 weights[admin, popular, last] = {
12 { 9, 0, 0 } 12 { 9, 0, 0 }
13 { 4, 9, 2 } 13 { 4, 9, 2 }
14 { 2, 2, 9 } 14 { 2, 2, 9 }
15 { 0, 0, -9 } 15 { 0, 0, -9 }
16 } 16 }
17 }}} 17 }}}
18 and map is selected using weighted random, by combining(adding) all weights of map multipled by slot weight selection, with some further tweaks : 18 and map is selected using weighted random, by combining(adding) all weights of map multipled by slot weight selection, with some further tweaks :
19 {{{slot(n) { 19 {{{slot(n) {
20 x[] = map_weights[] * weights[n] * random(from 0.9 to 1.0); 20 x[] = map_weights[] * weights[n] * random(from 0.9 to 1.0);
21 for each map: weight[map] = x.admin*scale_admin 21 for each map: weight[map] = x.admin*scale_admin
22 + x.popular^power_popular*scale_popularity 22 + x.popular^power_popular*scale_popularity
23 + x. last>0 ? absolute( x. last) ^power_last*scale_last : 23 + x. last>0 ? x. last^power_last*scale_last :
24 (1-absolute(x.last))^power_last*scale_last ; 24 (1-absolute(x.last))^power_last*scale_last ;
25 return random(weight) 25 return random(weight)
26 } 26 }
27 }}} 27 }}}
28 maybe on some days do reverse order of scale to do retro maps more favoured on fridays or something... toy around with it. figure it out... :) the minus in setting the weight of the x.last fragment is determinging if the map should be weighted using last or first played order of weights. i guess you could plug it to x.popular as well. 28 maybe on some days do reverse order of scale to do retro maps more favoured on fridays or something... toy around with it. figure it out... :) the minus in setting the weight of the x.last fragment is determinging if the map should be weighted using last or first played order of weights. i guess you could plug it to x.popular as well.
29 \n 29 \n
30 On top of that you might add 30 On top of that you might add
31 {{{!mapw 9 1 1}}} 31 {{{!mapw 9 1 1}}}
32 command to do map random, using own weights instead of those in that 3x4 matrix, so all slots are using same weights for random 32 command to do map random, using own weights instead of those in that 3x4 matrix, so all slots are using same weights for random
33 \n 33 \n