Zandronum Chat on our Discord Server Get the latest version: 3.2.1
Source Code
My View | View Issues | Change Log | Roadmap | Zandronum Issue Support Ranking | Rules | My Account
  

View Issue Details [ Jump to Notes ] [ Issue History ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0001276Zandronum[All Projects] Suggestionpublic2013-02-09 16:532018-09-30 20:19
ReporterMonsterovich 
Assigned ToTorr Samaho 
PriorityhighSeverityfeatureReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version1.0 
Target Version1.1Fixed in Version1.1 
Summary0001276: Do not disconnect immediately after selecting "New game" in the main menu
DescriptionBut instead disconnect only after choosing the difficulty.
Steps To Reproduce1. Connect to a multiplayer game
2. Open main menu
3. Select "New Game"
4. You are instantly disconnected from the server.
Attached Files

- Relationships

-  Notes
User avatar (0005973)
Watermelon (developer)
2013-02-09 18:32

 This was always a pain when I'd open the menu and hit enter by accident thinking I was on options and get kicked out of my LMS game, thus losing a lot.

The next question is why was this added to New Game? What bug did it fix when it was not in there?
User avatar (0005975)
Dusk (developer)
2013-02-09 19:23

 In AOW I countered this by adding a confirmation screen to the only skill level. Perhaps something similar could be put together here.
User avatar (0006139)
Torr Samaho (administrator)
2013-03-17 19:35

 I just tested this briefly and I'm not disconnected immediately after selecting new game, but only after selecting the skill.
User avatar (0006142)
Ijon Tichy (reporter)
2013-03-18 01:08

 It happens only when there's multiple classes to select, apparently.
User avatar (0006164)
Torr Samaho (administrator)
2013-03-24 08:42
edited on: 2013-03-24 08:43

 I see. I changed it so that the player is now told to disconnect first instead of being automatically disconnected immediately. Please test in the next beta build.
User avatar (0006206)
Arco (updater)
2013-04-04 01:28
edited on: 2013-05-25 23:49

 I tested the latest build with and without class-oriented wads (i.e. Samsara,) and the bug still happens.

EDIT: This is now fixed in V1.1 Alpha-130512-1932.

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
2013-02-09 16:53 Monsterovich New Issue
2013-02-09 18:32 Watermelon Note Added: 0005973
2013-02-09 19:23 Dusk Note Added: 0005975
2013-03-17 19:35 Torr Samaho Note Added: 0006139
2013-03-18 01:08 Ijon Tichy Note Added: 0006142
2013-03-24 08:42 Torr Samaho Note Added: 0006164
2013-03-24 08:43 Torr Samaho Status new => needs testing
2013-03-24 08:43 Torr Samaho Product Version => 1.0
2013-03-24 08:43 Torr Samaho Target Version => 1.1
2013-03-24 08:43 Torr Samaho Note Edited: 0006164 View Revisions
2013-03-24 08:44 Torr Samaho Note Revision Dropped: 6164: 0003391
2013-03-24 13:28 Torr Samaho Assigned To => Torr Samaho
2013-03-24 13:28 Torr Samaho Status needs testing => assigned
2013-04-04 01:28 Arco Note Added: 0006206
2013-05-25 23:49 Arco Note Edited: 0006206 View Revisions
2013-06-11 03:35 Blzut3 Status assigned => resolved
2013-06-11 03:35 Blzut3 Fixed in Version => 1.1
2013-06-11 03:35 Blzut3 Resolution open => fixed
2018-09-30 20:19 Blzut3 Status resolved => closed




Questions or other issues? Contact Us.

Links

Copyright © 2000 - 2025 MantisBT Team
Powered by Mantis Bugtracker