0002582: Skirmish menu doesn't save settings

Notes
(0014103) Dusk (developer) 2016-01-17 14:04	'https://bitbucket.org/Torr_Samaho/zandronum/pull-requests/55 [^]'

(0014105) cobalt (updater) 2016-01-17 16:11	Issue addressed by commit c8512ac6a3ee: Fixed: the skirmish menu didn't save limits or skill settings (fixes 2582) Committed by Teemu Piippo [Dusk] on Wednesday 31 December 1969 23:59:57 Changes in files: src/menu/multiplayermenu.cpp \| 21 +++++++++++++++++++-- wadsrc/static/menudef.za \| 12 ++++++------ 2 files changed, 25 insertions(+), 8 deletions(-)

(0014171) StrikerMan780 (reporter) 2016-01-24 12:42 edited on: 2016-01-24 13:31	Tried this build, still doesn't save the settings. 'https://www.dropbox.com/sh/nnc1tgooo1pbo0z/AABnmVdzdEArYA8eXrZz1KLca/zandronum-3.0-r160117-2053-4255969-windows.zip?dl=0 [^]' EDIT: Never mind, it works, but I had to delete my INI first. It doesn't seem to add the entries to the INI if they aren't already there at generation.

(0014434) Ru5tK1ng (updater) 2016-02-13 22:13	I had a clean install and the settings saved for me. I'm not sure if having to delete an INI as striker indicated warrants for a rework of the fix.

(0014449) StrikerMan780 (reporter) 2016-02-16 07:09	Most people will be using their old inis, replacing their existing Zandronum installs when the time comes. I think it's worth investigating.

(0016354) Torr Samaho (administrator) 2016-11-27 16:15	I can't reproduce the problem if I use my 2.1.2 ini with the latest 3.0 build. Can somebody reproduce the problem? If so, please post a copy of the problematic ini. Otherwise, I'll consider this issue as fixed.

(0016486) Catastrophe (reporter) 2016-12-13 00:20	From the various testing sessions I've done with various revisions of 3.0, I haven't encountered this problem.

(0016725) Ru5tK1ng (updater) 2017-01-30 03:04	Based on Catastrophe's results and no ini for several months, this is closed.

**Issue Community Support**
This issue is already marked as resolved. If you feel that is not the case, please reopen it and explain why.
Supporters:	No one explicitly supports this issue yet.
Opponents:	No one explicitly opposes this issue yet.

Issue Community Support

This issue is already marked as resolved.
If you feel that is not the case, please reopen it and explain why.

Supporters:

No one explicitly supports this issue yet.

Opponents:

No one explicitly opposes this issue yet.

Issue History
Date Modified	Username	Field	Change
2016-01-17 10:15	StrikerMan780	New Issue
2016-01-17 13:33	Dusk	Assigned To	=> Dusk
2016-01-17 13:33	Dusk	Status	new => assigned
2016-01-17 14:04	Dusk	Note Added: 0014103
2016-01-17 14:04	Dusk	Status	assigned => needs review
2016-01-17 16:11	cobalt	Status	needs review => needs testing
2016-01-17 16:11	cobalt	Target Version	=> 3.0
2016-01-17 16:11	cobalt	Note Added: 0014105
2016-01-24 12:42	StrikerMan780	Note Added: 0014171
2016-01-24 13:31	StrikerMan780	Note Edited: 0014171	View Revisions
2016-02-13 22:13	Ru5tK1ng	Note Added: 0014434
2016-02-16 07:09	StrikerMan780	Note Added: 0014449
2016-04-10 17:05	Ru5tK1ng	Status	needs testing => feedback
2016-11-27 16:15	Torr Samaho	Note Added: 0016354
2016-12-13 00:20	Catastrophe	Note Added: 0016486
2017-01-30 03:04	Ru5tK1ng	Note Added: 0016725
2017-01-30 03:04	Ru5tK1ng	Status	feedback => resolved
2017-01-30 03:04	Ru5tK1ng	Resolution	open => fixed
2017-01-30 03:04	Ru5tK1ng	Fixed in Version	=> 3.0
2018-09-30 21:50	Blzut3	Status	resolved => closed

Relationships