0001645: "Player located none" shared keys message

Notes
(0007896) someoneelse (reporter) 2014-01-06 16:11	I made Doom II server, same happened.

(0007897) Dusk (developer) 2014-01-06 16:19	Quote Dusk has connected. (from: LAN) Dusk joined the game. Dusk has located the RedCard! client Dusk disconnected. Works fine for me with a server with the svdoom.wad from best-ever:'http://static.best-ever.org/wads/svdoom.wad [^]' Exactly what wads are you using?

(0007901) someoneelse (reporter) 2014-01-06 18:49 edited on: 2014-01-06 18:51	doom.wad and svdoom.wad... But then I made Doom II server, without any wads, and it happened again. So I guess it's not WADs fault. (I started the server via IDE, btw., which messes up flags, but I can't see how it would affect this string). I played with other people who also noticed that. I can include a demo, I guess? Oh, and my server is up, called "I have located the None!", if you are available you can see it.

(0007902) Dusk (developer) 2014-01-06 18:51	A demo could help here. Also please check whether it happens with a clean INI.

(0007903) someoneelse (reporter) 2014-01-06 19:08	Deleting inis didn't help. I also booted the server from the commandline, with a very minimal config that I am sending. (Demo was already sent, I edited my previous post BTW)

(0007904) Dusk (developer) 2014-01-06 19:32	blargh, my build was outdated, I can confirm this now and I already see what's wrong...

(0007905) Dusk (developer) 2014-01-06 20:15	'https://bitbucket.org/Torr_Samaho/zandronum/pull-request/28/changes-to-sv_sharekeys [^]' when I tested the fix for 0001625, I forgot to check the scenario when the actor has no tag set..

(0007950) Torr Samaho (administrator) 2014-01-11 12:05	'https://bitbucket.org/slatenails/zandronum/commits/39782610856c1aeda2016ef1cbc607c59b57486d [^]' looks good. I'll pull and rebase it.

(0007968) Torr Samaho (administrator) 2014-01-12 08:00	I transplanted your fix. I think this is better than "pull + rebase" since this keeps a proper reference to the hash of your original changeset and still keeps the history linear.

(0008182) Qent (updater) 2014-02-09 19:31	This fix works.

**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
2014-01-06 14:56	someoneelse	New Issue
2014-01-06 16:11	someoneelse	Note Added: 0007896
2014-01-06 16:19	Dusk	Note Added: 0007897
2014-01-06 16:19	Dusk	Assigned To	=> Dusk
2014-01-06 16:19	Dusk	Status	new => feedback
2014-01-06 18:00	Dusk	Target Version	=> 2.0
2014-01-06 18:49	someoneelse	Note Added: 0007901
2014-01-06 18:49	someoneelse	Status	feedback => assigned
2014-01-06 18:49	someoneelse	File Added: 2014.01.06_19.44.48_doom2.cld
2014-01-06 18:51	someoneelse	Note Edited: 0007901	View Revisions
2014-01-06 18:51	Dusk	Note Added: 0007902
2014-01-06 18:51	Dusk	Status	assigned => feedback
2014-01-06 19:08	someoneelse	Note Added: 0007903
2014-01-06 19:08	someoneelse	Status	feedback => assigned
2014-01-06 19:09	someoneelse	File Added: server.cfg
2014-01-06 19:32	Dusk	Note Added: 0007904
2014-01-06 20:15	Dusk	Note Added: 0007905
2014-01-06 20:15	Dusk	Status	assigned => needs review
2014-01-11 12:05	Torr Samaho	Note Added: 0007950
2014-01-12 08:00	Torr Samaho	Note Added: 0007968
2014-01-12 08:00	Torr Samaho	Status	needs review => needs testing
2014-02-09 19:31	Qent	Note Added: 0008182
2014-02-09 19:31	Qent	Status	needs testing => resolved
2014-02-09 19:31	Qent	Fixed in Version	=> 2.0-beta
2014-02-09 19:31	Qent	Resolution	open => fixed
2015-01-23 04:56	Blzut3	Fixed in Version	2.0-beta => 2.0
2018-09-30 23:06	Blzut3	Status	resolved => closed

Relationships