MantisBT - Zandronum
View Issue Details
0001386Zandronum[All Projects] Bugpublic2013-06-28 03:282018-09-30 23:13
Mr. Repo 
 
normalminoralways
closedfixed 
MicrosoftWindowsXP/Vista/7
2.0-beta 
2.0 
0001386: Monsters with DesignatedTeam infight/attack players of the same team when teamdamage is on
Not sure if this is intentional or not because of teamdamage being required, but either way I feel that this deserves some sort of attention.

When teamdamage is turned on and a teammate harms another teammate, the monster(s) summoned by the player that received the damage start attacking the player that caused the damage and eventually infight if the other teammate has any monsters of their own. Even after the monsters are killed and new ones are spawned, the new monsters being summoned still will automatically hate whomever attacked the player last regardless of when the initial damage was inflicted.
Using the attached wad:

1. Start a team game server.

2. Set 'Teamdamage' to 1.0.

3. Have two players join the red team.

4. Have one player type to console 'summonfriend redteamzombieman'.

5. Have the other player attack the player who summoned the Zombieman.

6. Watch as the Zombieman targets the teammate who inflicted the damage.
I recorded a demo demonstrating this that can be found at'http://www.mediafire.com/download/qghpky3vq6733s6/DesignatedTeamBug.cld [^]'

Also of note: if you summon a monster normally without using 'summonfriend', whatever is summoned is aggressive and acts like a normal monster completely disregarding whatever team it is set to. While it isn't causing any problems on my end I figured that should at least be mentioned here regardless.
No tags attached.
? DesignatedTeamBug.wad (254) 2013-06-28 03:28
/tracker/file_download.php?file_id=989&type=bug
Issue History
2013-06-28 03:28Mr. RepoNew Issue
2013-06-28 03:28Mr. RepoFile Added: DesignatedTeamBug.wad
2014-06-14 17:24WatermelonNote Added: 0009298
2014-06-14 17:24WatermelonStatusnew => feedback
2014-07-24 23:30Mr. RepoNote Added: 0010054
2014-07-24 23:30Mr. RepoStatusfeedback => new
2014-07-25 03:34ArcoStatusnew => resolved
2014-07-25 03:34ArcoResolutionopen => fixed
2014-07-25 03:34ArcoProduct Version1.0 => 2.0-beta
2014-07-25 03:34ArcoFixed in Version => 2.0
2018-09-30 23:13Blzut3Statusresolved => closed

Notes
(0009298)
Watermelon   
2014-06-14 17:24   
Does this still happen in 2.0?
(0010054)
Mr. Repo   
2014-07-24 23:30   
Fixed and working correctly in 2.0.