MantisBT - Zandronum |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0002234 | Zandronum | [All Projects] Bug | public | 2015-05-17 08:41 | 2018-09-30 22:20 |
|
Reporter | DrinkyBird | |
Assigned To | Torr Samaho | |
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | |
Platform | Microsoft | OS | Windows | OS Version | 7 SP1 x64 |
Product Version | 3.0-beta | |
Target Version | 3.0 | Fixed in Version | 3.0 | |
|
Summary | 0002234: nextmap and nextsecret commands are sort of broken |
Description | When testing one of my mods in 3.0, I found an issue with the nextmap command that sends you to a non-existent random map.
Tested on WaTaKiD's build of abdac7b. |
Steps To Reproduce | 1. Go to a map that has no next map. (Try the attached map called BLANK I made to test this ticket)
2. Type `nextmap` in console.
3. Instead of printing "No next map" and doing nothing, it tries to go to a map "ENDSEQ07CE" (the last 4 characters seem to vary).
|
Additional Information | Does not happen in GZDoom 1.8.00 - it simply says "No next map" and does nothing else.
Tested with various maps that lack a map after them.
Also tested with fresh INIs and not-so-fresh INIs.
On 2.0, it pretty much just restarts the map. |
Tags | No tags attached. |
Relationships | |
Attached Files | blank.wad (1,256) 2015-05-17 08:41 /tracker/file_download.php?file_id=1493&type=bug |
|
Issue History |
Date Modified | Username | Field | Change |
2015-05-17 08:41 | DrinkyBird | New Issue | |
2015-05-17 08:41 | DrinkyBird | File Added: blank.wad | |
2015-05-17 16:41 | Torr Samaho | Assigned To | => Torr Samaho |
2015-05-17 16:41 | Torr Samaho | Status | new => assigned |
2015-05-17 16:57 | Torr Samaho | Note Added: 0012314 | |
2015-05-17 17:34 | Torr Samaho | Status | assigned => needs testing |
2015-05-17 17:38 | DrinkyBird | Note Added: 0012323 | |
2015-05-17 23:05 | Edward-san | Note Added: 0012328 | |
2015-05-17 23:15 | Arco | Severity | major => minor |
2015-05-17 23:15 | Arco | Status | needs testing => assigned |
2015-05-17 23:15 | Arco | Summary | [Merge Experiments] nextmap command is sort of broken => [Merge Experiments] nextmap and nextsecret command are sort of broken |
2015-05-17 23:15 | Arco | Summary | [Merge Experiments] nextmap and nextsecret command are sort of broken => [Merge Experiments] nextmap and nextsecret commands are sort of broken |
2015-05-24 18:55 | Dusk | Product Version | => 3.0 |
2015-05-24 18:55 | Dusk | Target Version | => 3.0 |
2015-05-24 18:55 | Dusk | Summary | [Merge Experiments] nextmap and nextsecret commands are sort of broken => nextmap and nextsecret commands are sort of broken |
2015-05-24 19:31 | Dusk | Product Version | 3.0 => 3.0-beta |
2015-08-08 15:48 | Torr Samaho | Note Added: 0013098 | |
2015-08-08 15:48 | Torr Samaho | Status | assigned => needs testing |
2015-08-08 15:48 | cobalt | Note Added: 0013100 | |
2015-08-09 23:05 | WaTaKiD | Note Added: 0013182 | |
2015-08-09 23:05 | WaTaKiD | Note Edited: 0013182 | bug_revision_view_page.php?bugnote_id=13182#r7863 |
2015-09-10 20:13 | Dusk | Status | needs testing => resolved |
2015-09-10 20:13 | Dusk | Fixed in Version | => 3.0 |
2015-09-10 20:13 | Dusk | Resolution | open => fixed |
2018-09-30 22:20 | Blzut3 | Status | resolved => closed |
Notes |
|
|
|
|
|
|
|
|
I can reproduce the issue with 'nextsecret', too. It needs the same fix as 'nextmap'. |
|
|
|
I also applied the fix to nextsecret. |
|
|
(0013100)
|
cobalt
|
2015-08-08 15:48
|
|
|
|
|
|