Zandronum Chat on our Discord Server Get the latest version: 3.1
Source Code

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0002648Zandronum[All Projects] Bugpublic2016-02-22 16:272018-09-30 21:40
ReporterXsnake 
Assigned ToDusk 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformMicrosoftOSWindowsOS VersionXP/Vista/7
Product Version2.1 
Target Version2.2Fixed in Version2.2 
Summary0002648: Newly connected clients aren't informed about other players TID
DescriptionWhen a TID change is performed on a player (serverside), all the clients connected to the server are informed about it. However, if a client joins after the TID change has been performed, they are not informed about it.
Steps To ReproduceThe issue happens online only.
-set up a server with a bot (MAP01, SyncTIDCheck.wad)
-join the server
-the clientside reading of the monster's HP works, but not of the player 1's HP
-remove the bot
-add another bot while you're in the server
-now the clientside reading of the player 1's HP works
Additional InformationClients seem to be properly informed about TIDs affected to monsters, even when they join late. The issue is about players TIDs only.
Tested on 3.0-160131-2023 and 2.1.2
Attached Files? file icon SyncTIDCheck.wad [^] (2,350 bytes) 2016-02-22 16:27

- Relationships

-  Notes
User avatar (0014476)
Dusk (developer)
2016-02-22 19:06

Fixed
User avatar (0014512)
cobalt (updater)
2016-02-28 13:01

Issue addressed by commit e7f7d7dedb4f: Fixed: newly connecting clients were not informed of player TIDs, fixes 2648
Committed by Teemu Piippo [Dusk] on Wednesday 31 December 1969 23:59:57

Changes in files:

 docs/zandronum-history.txt | 1 +
 src/sv_main.cpp | 4 ++++
 2 files changed, 5 insertions(+), 0 deletions(-)

User avatar (0014529)
Ru5tK1ng (updater)
2016-03-01 22:12

I tested this online with the latest build and the hp showed up properly on map load and after adding and kicking bots.

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
2016-02-22 16:27 Xsnake New Issue
2016-02-22 16:27 Xsnake File Added: SyncTIDCheck.wad
2016-02-22 17:13 Dusk Product Version 3.0-beta => 2.1
2016-02-22 17:15 Dusk Priority low => normal
2016-02-22 17:18 Dusk Assigned To => Dusk
2016-02-22 17:18 Dusk Status new => assigned
2016-02-22 19:06 Dusk Note Added: 0014476
2016-02-22 19:06 Dusk Status assigned => needs review
2016-02-28 13:01 cobalt Status needs review => needs testing
2016-02-28 13:01 cobalt Target Version => 2.2
2016-02-28 13:01 cobalt Steps to Reproduce Updated View Revisions
2016-02-28 13:01 cobalt Additional Information Updated View Revisions
2016-02-28 13:01 cobalt Note Added: 0014512
2016-03-01 22:12 Ru5tK1ng Note Added: 0014529
2016-03-01 22:13 Ru5tK1ng Status needs testing => resolved
2016-03-01 22:13 Ru5tK1ng Resolution open => fixed
2016-03-01 22:13 Ru5tK1ng Fixed in Version => 2.2
2016-03-01 22:13 Ru5tK1ng Steps to Reproduce Updated View Revisions
2016-03-01 22:13 Ru5tK1ng Additional Information Updated View Revisions
2018-09-30 21:40 Blzut3 Status resolved => closed






Questions or other issues? Contact Us.

Links


Copyright © 2000 - 2024 MantisBT Team
Powered by Mantis Bugtracker