| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0004584 | Doomseeker | [All Projects] Bug | public | 2026-01-18 06:10 | 2026-01-24 16:39 |
|
| Reporter | Bill Buchanan | |
| Assigned To | | |
| Priority | high | Severity | major | Reproducibility | always |
| Status | acknowledged | Resolution | open | |
| Platform | PC | OS | Windows | OS Version | 10 x64 |
| Product Version | 1.5.3 | |
| Target Version | | Fixed in Version | | |
|
| Summary | 0004584: Odamex Deathmatch servers with sv_timelimit set to 0 (infinite) display as <ERROR>. |
| Description | Odamex Deathmatch servers with no timelimit, i.e. sv_timelimit set to 0, don't resolve properly in DoomSeeker. Instead, these servers are displayed as <ERROR> in the server list. Deathmatch servers with sv_timelimit set to anything higher than 0 will properly display. |
| Steps To Reproduce | 1. Start an Odamex Deathmatch server.
2. Set sv_timelimit to 0
3. The server will display in DoomSeeker as <ERROR> |
| Additional Information | DoomExplorer and OdaLaunch don't seem to be affected. This appears to be a DoomSeeker-exclusive issue.
It doesn't matter if the server is started from DoomSeeker or just with a bare batch file/command.
Using rcon or other means to give a sv_timelimt of anything higher than 0 will allow the server to display in DoomSeeker again. Likewise, setting it to 0 while it's up will make it display <ERROR> again. |
|
| Attached Files | |
|
Chat on our Discord Server
Get the latest version: 3.2.1
Relationships 
Relationships 
ZDoom
Doom Wiki
id Software
Doomworld
Odamex
Doomseeker
Internet Doom Explorer
The Sentinel's Playground Servers