[odamex-bug-reporter] [Bug 743] New: Announcer (VOX) Standard

From: odamex-bugtracker@xxxxxxxxxx
To: odamex-bug-reporter@xxxxxxxxxxxxx
Date: Tue, 16 Aug 2011 18:34:50 +0000
http://odamex.net/bugs/show_bug.cgi?id=743

             Bug #: 743
           Summary: Announcer (VOX) Standard
    Classification: Unclassified
           Product: Odamex
           Version: 0.5
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Client
        AssignedTo: odamex-bug-reporter@xxxxxxxxxxxxx
        ReportedBy: charles.gunyon@xxxxxxxxx


Some kind of announcer standard would be good I think.  Odamex has a CTF
announcer that uses the following names:

  dsffd (friendly flag dropped)
  dsffg (friendly flag taken)
  dsffm (friendly flag manually returned)
  dsffr (friendly flag returned)
  dsffs (friendly team captured the flag)

Those are "friendly" sound names, dsefd is like the enemy's flag was dropped
(in odamex.wad the sounds are the same whether friendly or enemy).

But there are other "announce-able" events.  ZDaemon primarily uses zvox2.wad,
and the names in there are:

ac_assis.wav  ac_bluet.wav  ac_frag3.wav  ac_holys.wav  ac_leadl.wav 
ac_min5.wav   ac_mult5.wav  ac_reds.wav   ac_spre3.wav  ac_sui1.wav  ac_win.wav
ac_blued.wav  ac_fight.wav  ac_frat1.wav  ac_humil.wav  ac_leadt.wav 
ac_mult2.wav  ac_prep.wav   ac_redt.wav   ac_spre4.wav  ac_sui2.wav
ac_bluer.wav  ac_frag1.wav  ac_frat2.wav  ac_impre.wav  ac_lose.wav  
ac_mult3.wav  ac_redd.wav   ac_spre1.wav  ac_spre5.wav  ac_sui3.wav
ac_blues.wav  ac_frag2.wav  ac_frat3.wav  ac_leadg.wav  ac_min1.wav  
ac_mult4.wav  ac_redr.wav   ac_spre2.wav  ac_spre6.wav  ac_tie.wav

Hopefully those are self-explanatory.

<Ralphis> If Odamex does it, it would probably be based upon some types of
conditions rather than being named strictly after the UT names I imagine
<Ladna> yeah
<Ladna> they should be a lot more generic than they are now

I (clearly) agree with this.

So specifically what I am hoping for is some kind of chart like the one above
that lists sound names and events that trigger them.  I guess it would be less
work if we just used zvox2.wad names - we would get the benefit of all the *vox
WADs out there too - but like Ralphis said they kind of suck, and *vox WADs
aren't hard to convert anyway.

-- 
Configure bugmail: http://odamex.net/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[odamex-bug-reporter] [Bug 743] New: Announcer (VOX) Standard

Other related posts:
