Zandronum Chat @
Get the latest version: 3.0
Source Code

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0003193Doomseeker[All Projects] Bugpublic2017-07-21 23:532017-10-05 00:36
Assigned To 
PlatformMicrosoftOSWindowsOS VersionXP/Vista/7
Product Version1.1 
Target VersionFixed in Version 
Summary0003193: Server owner does not show up in buddies list
DescriptionThe owner of a server, when plaing on his own server, does not show up in buddies list. All other buddies on same server do. I had the owner change his name, added the new name in the buddies list, and he still didn't show up. I found another server with presumably a local player (ping 1) but after adding him he does show up, so I don't know what's going on.
Steps To ReproduceAdd "Johnny Blaze" to your buddies list, when he's playing in one of the "MOP + Chillax" servers (usually fri/sat around midnight GMT, sometimes other times too)
Attached Files

- Relationships

-  Notes
User avatar (0018075)
Zalewa (developer)
2017-07-22 16:38

Doomseeker doesn't know if player is local or not (in fact, all players in Zandronum are technically remote, because the servers can only be run in a dedicated mode).

Maybe "Johnny Blaze" is using a hidden character in their nickname? Something that is there but isn't printed on screen.

Try adding this player in "Basic" mode as "*Johnny*Blaze*".
User avatar (0018117)
Zom-B (reporter)
2017-07-29 20:01

He shows up as "b1]Johnny Blaze". It's not stripping this extended color code quite right for some reason.
User avatar (0018435)
WubTheCaptain (developer)
2017-10-04 20:13

I'm unable to reproduce. I tried names with colors, spaces, basic wildcard matching, they all show up in the buddy list as intended.

Only thing I noticed was at some point Doomseeker's buddy list for names I had added just reset. This happens sometimes when a server started from Doomseeker is open and Doomseeker is restarted.
User avatar (0018437)
WubTheCaptain (developer)
2017-10-04 20:59
edited on: 2017-10-04 21:31

Okay, I think I understand what's going on in here. It's an escape sequence/third-party issue. This affects extended colors from third-party "NewTextColors_260.pk3", but not regular color sequences.

Ingame, I had my name set to "b1]Wub". Just those characters, no colors. "name b1]Wub" in console. Attempting to match "b1]*" in Doomseeker finds no results. Attempting to match "*Wub" finds it. An escaped sequence "b1\]*" also finds it.

With standard colors: "name \cfWub" in console. This is displayed as "Wub" with a color in the "server details" dialog in Doomseeker, but as "Wub" in the buddies dialog. It uses a standard color ingame. "Wub" matches this in buddy list.

With extended colors from NewTextColors_260.pk3: "name \c[b1]Wub" in console. This is displayed as "Wub" with no colors in the "server details" dialog in Doomseeker, but as "b1]Wub" in buddies dialog. It uses an extended color ingame. "Wub" does not match this in buddy list, but "*Wub" does. "b1]Wub" or "b1\]Wub" does not match. "\[b1\]Wub" matches.

I also tried using a non-breaking space (" ") as a "hidden character". To my awareness, it's treated the same as a regular space character (like case-insensitive).

In other words: Because "\c[" is not a "valid" standard color sequence ("[" is not a recognized color), it will be discarded and you get this result. Special characters must also be escaped with a backwards slash ("\") or matched with a wildcard asterisk ("*").

Tested with Zandronum 3.0 and Doomseeker 1.1.

User avatar (0018438)
WubTheCaptain (developer)
2017-10-04 21:58

Personally, I also think Doomseeker to be working as intended. If game data (WAD) authors want to break existing conventions, that's their fault. I admit I'd like to have a color sequence standardized for custom colors, but until then I wouldn't make a hacked up patch to this issue. The correct way to handle those broken convention cases is to match "*Wub".

I've set this to acknowledged, but not confirmed. I'll leave it up to the developers (Zalewa and/or Blzut3) to decide what to do with this.
User avatar (0018442)
Blzut3 (administrator)
2017-10-05 00:36

The "\c[*]" is a valid color sequence for a long time now, so if that's what's tripping things up then this is a bug.

Issue Community Support
Only registered users can voice their support. Click here to register, or here to log in.
Supporters: No one explicitly supports this issue yet.
Opponents: WubTheCaptain

- Issue History
Date Modified Username Field Change
2017-07-21 23:53 Zom-B New Issue
2017-07-22 16:38 Zalewa Note Added: 0018075
2017-07-29 20:01 Zom-B Note Added: 0018117
2017-10-04 20:13 WubTheCaptain Note Added: 0018435
2017-10-04 20:26 WubTheCaptain Note Added: 0018436
2017-10-04 20:26 WubTheCaptain Note Edited: 0018436 View Revisions
2017-10-04 20:33 WubTheCaptain Note Edited: 0018436 View Revisions
2017-10-04 20:52 WubTheCaptain Note Deleted: 0018436
2017-10-04 20:59 WubTheCaptain Note Added: 0018437
2017-10-04 21:00 WubTheCaptain Note Edited: 0018437 View Revisions
2017-10-04 21:01 WubTheCaptain Note Edited: 0018437 View Revisions
2017-10-04 21:08 WubTheCaptain Status new => acknowledged
2017-10-04 21:09 WubTheCaptain Note Edited: 0018437 View Revisions
2017-10-04 21:10 WubTheCaptain Note Edited: 0018437 View Revisions
2017-10-04 21:10 WubTheCaptain Product Version => 1.1
2017-10-04 21:31 WubTheCaptain Note Edited: 0018437 View Revisions
2017-10-04 21:58 WubTheCaptain Note Added: 0018438
2017-10-05 00:36 Blzut3 Note Added: 0018442

Questions or other issues? Contact Us.


Copyright © 2000 - 2018 MantisBT Team
Powered by Mantis Bugtracker