[addons_zz]

Released a new version:

2017-05-23 | v5.7.0-878

1. Added a new option to the cvar `gal_general_options`, change the command `gal_startvote` command default behavior.
2. Added a new argument to the command `gal_startvote`. The argument `-now` to allow the map to change immediately at the voting end.
3. Added a new argument to the command `gal_startvote`. The argument `-roundend` to allow the round to finish after the voting end.
4. Added a new cvar `gal_endonround_max` to indicates the maximum time to wait before forcing to change the map.
5. Fixed the cvars `gal_extendmap_max_*` option 0 always blocking the vote, instead of allowing it.
6. Fixed the command `say rockthevote` not working when cvar `gal_rtv_commands` enables it.
7. Fixed a ghost extension option showing up on `runoff` voting.
8. Fixed the possibility of the voting being messed up by its own automatic trigger.
9. Renamed the command `gal_command_maintenance` to `gal_maintenance_mode`.
10. Renamed the command `gal_looking_for_crashes` to `gal_look_for_crashes`.
11. Set the MAX_SERVER_RESTART_ACCEPTABLE value to 1, implying on 3 crashes required before ignoring the map.

[feruchio]

Thank your feature (about the night dm cvar) works fine, but sometimes start a vote while 10 minutes of the map have been passed and change the map after another 10 minutes, as it should be, but quite strange the vote show up 10 minutes before it have to. I should mention that in half of the times works normally and vote start when it supposed to start.

P.S I use version prior this 2017-05-23 | v5.7.0-878

[addons_zz]

Originally Posted by feruchio but quite strange the vote show up 10 minutes before it have to. I should mention that in half of the times works normally and vote start when it supposed to start.

It seems you are using the cvar `gal_endofmapvote_start` which not proper for round based
deathmatch server. So, just set it to 0 on your `galileo.cfg`:

// A heuristic which counts every end round, how much time the round
// took and how much time remains to the end of map. In base with it,
// calculate the correct round to start the voting.
//
// Notes:
// 1. It requires the game to have at least 8 rounds played, otherwise
//    it cannot try to guess on which round it should to start the voting.
//
// 2. If the prediction fail and the voting is not finish when the round
//    ended or the round total time is too short, i.e., the round total
//    time is bigger than the total voting time (including a possible
//    runoff, if enabled), a extra round will be played.
//
// 0 - Disable this feature.
// 1 - To start the voting on the Ultima     game round (the last round to be played).
// 2 - To start the voting on the Penult     game round (the round before the last).
// 3 - To start the voting on the Antepenult game round (the round before the last of the last).
//
// Default: 0
gal_endofmapvote_start 0

[BeNq!]

The last map played isn't locked. Why? Galileo.cfg:

////////////////////////////////////////////////////////////////////////
// Banning recently played maps means that the last several maps that //
// have been played can not be nominated or otherwise placed in the   //
// map vote. This ensures that a map can not be played over and over  //
// again at the expense of playing a variety of other maps.           //
////////////////////////////////////////////////////////////////////////

// Specifies how many of the most recent maps are disallowed from a map
// vote.
//
// If you specify a value greater than the number of maps in your server,
// it will automatically ban only the maximum allowed.
//
// A value of 0 will disable this feature.
//
// Default: 0
gal_banrecent 8

// When banning recently played maps, the last several maps that have
// been played can not be nominated.
//
// A value of 0 will keep banning the recently played from nomination.
//
// 1 - the banned maps will be banned from the being added to the
//     voting list automatically, but they are still able to be nominated
//     and added to the voting list.
//
// 2 - if the admin has the flag `f`(ADMIN_MAP) he can nominate recent banned maps.
//
// Default: 0
gal_recent_nom_maps 0

// Only mark as recent played maps, those maps which are included on
// the mapcycle specified by the cvar 'mapcyclefile'.
//
// 0 - Mark as recent maps, every recently played map.
//
// 1 - Only mark as recent maps, the maps included in the mapcycle list
//     specified by the cvar 'mapcyclefile'.
//
// Default: 0
gal_banrecent_mapcycle 1

// Indicates the style in which the recent maps are displayed when a
// player uses the "recentmaps" say command.
//
// 0 - do not show the banned maps, when using the `recentmaps` command
// 1 - all maps on one line
// 2 - each map on a separate line
// 3 - display a menu.
//
// Default: 3
gal_banrecentstyle 3

[addons_zz]

Setting the cvar `gal_banrecent_mapcycle` as 1 will only ban maps which are on your map cycle file. You should record a log reproducing the bug.

[BeNq!]

Looking:



Where is recentMaps.dat?

[addons_zz]

The answer is on the galileo log.

Update:

2017-05-24 | v5.7.1-879

1. Fixed the `ban recent` maps feature not working.

[wlmraziel]

im using the previous version, ¿i need modify de galileo.cfg?

[addons_zz]

No. You just need to see what is on the change log:

1. I when I modify the `galileo.cfg` (settings file) is when are added new cvars or options.
2. I when modify the `galileo.txt` (lang file) is when are added new LANG constants.

On this version I fixed a word misspelled, on the `galileo.cfg` but should have no impact.
You can see exactly all the changes I do on the files accessing this address bellow and clicking on the commits descriptions:

1. https://github.com/addonszz/Galileo/commits/master

This is what was changed on the last commit for this version:

1. https://github.com/addonszz/Galileo/commit/1db60f2f41cf3a8d544671968ca742656b89179f

[gabuch2]

The plugin's messages are being output to the console, not the chat, I'm not able to pinpoint the cause.