Zandronum Chat on our Discord Server Get the latest version: 3.1
Source Code
My View | View Issues | Change Log | Roadmap | Zandronum Issue Support Ranking | Rules | My Account
  

View Issue Details [ Jump to Notes ] [ Issue History ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0003231Zandronum[All Projects] Bugpublic2017-08-31 21:122022-10-14 01:53
ReporterDecay 
Assigned ToKaminsky 
PrioritynormalSeveritymajorReproducibilityalways
StatusresolvedResolutionfixed 
PlatformOSOS Version
Product Version3.0-beta 
Target Version3.1Fixed in Version3.1 
Summary0003231: BFG tracer obituary has regressed
DescriptionBFG tracer frags now read "x was killed by y" instead of "x couldn't hide from y's bfg"

This happened several 3.0 betas back i'm surprised nobody posted a ticket about it, unless this is intended behaviour? This regression breaks alexmax's duel40 obituary for bfg tracers and eon weapons at least as well, i don't know of anymore

Steps To Reproducefrag someone with the bfg
Attached Files

- Relationships

-  Notes
User avatar (0018241)
Dusk (developer)
2017-09-07 21:59

 This happens because DoomPlayer now has the line

  Obituary "$OB_MPDEFAULT"

in the actor definition. This is overriding the hard-coded logic of the BFG splash obituary.
User avatar (0018247)
Dusk (developer)
2017-09-08 13:54
edited on: 2017-09-08 13:54

 The obituary was added in commit 11b92d086309
User avatar (0019499)
unknownna (updater)
2018-09-10 12:37

 I've noticed this issue very often while testing some duel with bots in 3.1. The duel players are going to notice this bug all the time.
User avatar (0020024)
Ivan (reporter)
2018-10-08 20:43

 Happens with the current 3.1 build released here:'https://zandronum.com/forum/viewtopic.php?f=55&t=9340 [^]'
User avatar (0021632)
Kaminsky (developer)
2021-07-23 21:01

 3.1 should now be using the correct obituary for the BFG's tracers.
User avatar (0022447)
WaTaKiD (updater)
2022-10-14 01:53

 'https://hg.osdn.net/view/zandronum/zandronum-stable/rev/8076c8f33db8 [^]' was added and quick tests on windows and tspg linux servers show that its fixed

marking as resolved

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
2017-08-31 21:12 Decay New Issue
2017-09-07 21:59 Dusk Note Added: 0018241
2017-09-07 21:59 Dusk Status new => confirmed
2017-09-07 22:01 Dusk Target Version => 3.1
2017-09-08 13:54 Dusk Note Added: 0018247
2017-09-08 13:54 Dusk Note Edited: 0018247 View Revisions
2018-09-10 12:37 unknownna Note Added: 0019499
2018-10-08 20:43 Ivan Note Added: 0020024
2021-07-23 21:01 Kaminsky Note Added: 0021632
2021-07-23 21:01 Kaminsky Assigned To => Kaminsky
2021-07-23 21:01 Kaminsky Status confirmed => needs testing
2022-10-14 01:53 WaTaKiD Note Added: 0022447
2022-10-14 01:53 WaTaKiD Status needs testing => resolved
2022-10-14 01:53 WaTaKiD Resolution open => fixed
2022-10-14 01:53 WaTaKiD Fixed in Version => 3.1




Questions or other issues? Contact Us.

Links

Copyright © 2000 - 2024 MantisBT Team
Powered by Mantis Bugtracker