New features in v1.30
"use winter balls only when it is snowing" (introduced in v1.20) cannot be selected on overlay anymore - it has instead become a new default rule to serve winter balls for all competitions!
new default rule to serve winter balls for all competitions, TL/DR version: it has to actually snow (snowy weather) for the Ball Server to offer winter balls
it does not have to be a winter season at all :) - as long as it snows, the ball server will provide winter ball for the competition (if one exists in GDB) - so if it starts snowing mid-May, you'll still get the winter ball
for leagues that have fixed weeks when winter balls have to be used, there is new map file: map_winter_weeks.txt
only if a league is listed in this new map file, it will always use winter balls (which are assigned in map_competitions.txt) - it does not matter is it is snowing or not, winter ball will be used as long as the match falls in-between defined start/end weeks
if really needed, it can be restricted further to use winter balls within given weeks only if it is snowing too
this new map file only specifies week ranges/intervals when winter balls must be used - the ball itself is still assigned in the map_competitions.txt file
the term "week" is synonymous with the league match day - e.g. "Week 1" is actually Day 1 in a league (from the possible range of e.g. Day 1 to Day 38 for the league with 20 teams/2-rounds-each; or range Day 1 to Day 46 range for a league with 24 teams/2-rounds-each; etc.)
important: the "Week" is read from the sider property ctx.match_info - if match_info is 0, that means we have "Week 1" or Day 1 in the league; if match_info value is 37, the week is 38 (always +1), etc.
important: since "week" detection relies upon sider's ctx.match_info property, this new map file (map_winter_weeks.txt) CANNOT BE USED for cup competitions or in exhibition mode!
The concept of a "week" makes no sense in a cup format, and even more important - sider cannot provide such info for cups
Exhibition mode - the same
all cups and exhibitions follow the new default rule - only if it snows, use winter ball
"use winter balls only when it is snowing" (introduced in v1.20) cannot be selected on overlay anymore - it has instead become a new default rule to serve winter balls for all competitions!
new default rule to serve winter balls for all competitions, TL/DR version: it has to actually snow (snowy weather) for the Ball Server to offer winter balls
it does not have to be a winter season at all :) - as long as it snows, the ball server will provide winter ball for the competition (if one exists in GDB) - so if it starts snowing mid-May, you'll still get the winter ball
for leagues that have fixed weeks when winter balls have to be used, there is new map file: map_winter_weeks.txt
only if a league is listed in this new map file, it will always use winter balls (which are assigned in map_competitions.txt) - it does not matter is it is snowing or not, winter ball will be used as long as the match falls in-between defined start/end weeks
if really needed, it can be restricted further to use winter balls within given weeks only if it is snowing too
this new map file only specifies week ranges/intervals when winter balls must be used - the ball itself is still assigned in the map_competitions.txt file
the term "week" is synonymous with the league match day - e.g. "Week 1" is actually Day 1 in a league (from the possible range of e.g. Day 1 to Day 38 for the league with 20 teams/2-rounds-each; or range Day 1 to Day 46 range for a league with 24 teams/2-rounds-each; etc.)
important: the "Week" is read from the sider property ctx.match_info - if match_info is 0, that means we have "Week 1" or Day 1 in the league; if match_info value is 37, the week is 38 (always +1), etc.
important: since "week" detection relies upon sider's ctx.match_info property, this new map file (map_winter_weeks.txt) CANNOT BE USED for cup competitions or in exhibition mode!
The concept of a "week" makes no sense in a cup format, and even more important - sider cannot provide such info for cups
Exhibition mode - the same
all cups and exhibitions follow the new default rule - only if it snows, use winter ball
examples: here
and yet another completely new map file map_HiVis_winter_balls.txt, used to define only the special super-hi-vis winter balls - e.g. if a league has a regular yellowish winter ball which is always used during winter weeks (that yellowish ball would still be assigned in map_competitions.txt file), that same league may have different orange/red winter ball only for the low-visibility, heavy-snowfall situations
entries in this file are fully optional - if a competition is not listed here, it will still use its' standard winter ball assigned in your old map_competitions.txt file
makes no sense to use for leagues that have only one universal winter ball good enough for super-bad winter weather too (such as Ligue 1, which tends to use orange/reddish winter balls as the standard winter balls) - in that case, having only the old entry in map_competitions.txt is enough - define that universal winter ball there
Danish league for example does have two different winter balls prescribed
the yellowish one (for fine weather winter matches) goes into map_competitions.txt file
and the special snowfall ball which goes into new map_HiVis_winter_balls.txt file
if both types of winter balls are assigned to a competition (in map_competition and in map_hivis), then the ball from map_HiVis_winter_balls.txt file always has priority
unlike new weekly map file (which is usable only for leagues), this file can have effect on all types of competitions!
example: here
Summary
The biggest unavoidable change in v1.30 is the new default rule for switching to a winter ball ("only if it snows"), nothing is changed in map_teams.txt and in map_competitions.txt
new map file map_winter_weeks.txt enables you to keep the old seasonal way of using winter balls for the leagues that need it - BUT with more precision now, since it supports start/end week style, instead of serving winter balls throughout entire winter season
new map file map_HiVis_winter_balls.txt for the fully optional super hi-vis snow balls for snowy weather, which will override ordinary winter balls
How to use:
a) Installing Ball Server for the first time: Unpack the v1.1 7z archive and copy unpacked folders content and modules inside your sider folder (folder where you have sider.exe file) - overwrite, if asked
b) Upgrading to version 1.1 and/or using various ballpacks already: Unpack the v1.1 7z archive, delete map_teams.txt and map_competitions.txt files from unpacked v1.1's content folder first and then copy folders content and modules inside your sider folder (folder where you have sider.exe file) - overwrite, if asked
(If not done already) Download and install CommonLib.lua v1
(If not done already) Add lua.module = "BallServer.lua" under CommonLib.lua in sider.ini
[Optional] Customize map_teams.txt and map_competitions.txt files and add more ball folders in the content\ball-server folder (more instructions can be found inside .txt files)
[NEW v1.20] After ensuring you have a fully functional Ball Server v1.1, download and unpack v1.2 zip archive and copy unpacked folder modules inside your sider folder (folder where you have sider.exe file) - overwrite, if asked. Map files are not provided with version 1.2, only the replacement .lua script
[NEW v1.30] After ensuring you have a fully functional Ball Server v1.2, download and unpack v1.3 zip archive and copy unpacked folder modules inside your sider folder (folder where you have sider.exe file) - overwrite, if asked. Only the .lua script and sample versions of the two new map files are provided in v1.3 download
Download:
1. Link v1.1 (base pack with .lua script, no balls included) - LATEST version, with search by-name support - read THIS POST to learn more about searching
2. Link v1.2 (only replacement .lua script included - requires already working version v1.1 to be installed) - more info on v1.20 features in THIS POST
3. Link v1.3 (only replacement .lua script and sample versions of the two new v1.3 specific map files - requires already working version v1.2 to be installed)
Post a Comment