|
Notes |
|
|
(0007211)
|
|
ZzZombo
|
2013-09-18 04:11
(edited on: 2013-09-18 04:15) |
|
I think either the client should just show ?/? for HP/AP or SpawnHealth value/MaxArmor (zero?) value.
Q: Why such system do exist in first place? Many (all known competitive TBH) games such as CS/L4D don't hide opponents' health/armor if they are observed in deathcam or by spectators.
|
|
|
|
(0007223)
|
|
Qent
|
2013-09-18 17:38
(edited on: 2013-09-18 17:39) |
|
A couple questions were raised while testing the patch last night:
- When a player dies, should other clients be notified of their remaining armor?
- If not, should the health be shown at maximum or zero for other clients?
My view is that health should drop instantly to zero when spying on a player dying. Armor should remain at whatever the default for that player class was (usually zero, something else in some mods like ZDoomWars).
|
|
|
|
|
|
BTW: the test went well, with the help of Qent and 75. Apparently there are no regressions, hence this patch can be appliable imo. |
|
|
|
|
|
Oh, so this explains why spectators observe thick red pain screen after someone gets Soulsphere and immediately receives small damage in competitive modes. Client thinks that player's HP lowers from 200 (local prediction) to 100. This is also a bug btw |
|
|
|
|
|
I just remembered I forgot to set the correct status. |
|
|
|
|
|
But don't you find "?/?" being much better solution if we still don't want to stop hiding this information? And I still insist hiding HP and armor shouldn't be so strict (and TBH I never understood why we do it), and at least spectators could see the real state of the game. |
|
|
|
(0007942)
|
|
Konar6
|
|
2014-01-10 15:25
|
|
|
I'm wondering as well why spectators are not allowed to see players' health. I can't see how it could be efficiently abused for cheating. |
|
|
|
(0007945)
|
|
Edward-san
|
2014-01-10 22:56
(edited on: 2014-01-10 22:57) |
|
It seems there's a misunderstanding on the bug and the fix:
in every gamemode which prohibits the knowledge of the other players informations, if spawnhealth is set differently from default and one player is damaged for the first time, independently on the value of the damage, the spying clients will:
1)see the damage palette as if the player had spawnhealth-default damage
2)if custom SBarInfo HUD is used, health bar drops to 100.
This happens because the server sends some bytes to all the clients with the instruction: change the damaged player health/armor to 100/100. If the gamemode doesn't allow players to see each other's status, then the server should respect this and should not send lies at all. The fix is simple: just don't send useless info at all. Nothing changes regarding the general behavior and it's intended because that's the topic of this bug ticket.
Imho, if you want something about the rest, just create a new suggestion ticket with your considerations.
|
|
|
|
|
|
With your patch damaged players are not put into the pain state anymore. |
|
|
|
|
|
Does this happen also in coop? Because in deathmatch or in other games where the enemy players info is hidden, the pain state hiding is intentional. |
|
|
|
|
client_DamagePlayer always calls
players[ulPlayer].mo->SetState( pPainState );
no matter which game mode. So you intentionally want to hide the pain state in DM? Can you elaborate why? |
|
|
|
|
|
Ah, sorry, I thought you were speaking of the pain red screen ... I'll take a look at it. |
|
|
|
|
|
|
|
|
|
Updated a new patch which changes some comments. Tested it locally with 2 clients. Pain is heard, can be visible with chasecam, no sudden changes with health and armor. |
|
|
|
(0008907)
|
|
Torr Samaho
|
2014-06-08 10:12
(edited on: 2014-06-08 10:23) |
|
Looks good. Added!
EDIT: This needs to be tested in 1.3 and 2.0 separately since I had to adapt this change to the recent server commands rewrite in 2.0 when merging this change into 2.0.
|
|
|
|
(0009836)
|
|
Arco
|
|
2014-07-04 17:36
|
|
|
Works correctly in both v1.3 r140703-1806 and v2.0 r140609-0928. |
|
inconsistent_hp_armor.txt (2,545) 2013-09-17 21:15