Closed GoogleCodeExporter closed 9 years ago
I like the idea (especially if it's implemented alongside the 'Comm Room'
issue). I
also had some other ideas about essentially phasing out the whole channel
system and
switching to a named frequency / subscription based multicast system (so that
we have
several named channels that a radio can subscribe to, like a set
general/command/security/engineering channels, most people get 2 subscriptions
(their
occupational specialty, and the current general/partyline channel) but certain
roles
get enhanced headsets with more channels (like say the captain, who would get
3-4
channels, general/security/command/???). However this would complicate some of
the
mechanics for the traitor radio (no more freq to dial in).
what do you propose for the mechanic/say syntax to specify an intercom to send
to?
Original comment by maddi...@lightbound.net
on 14 Aug 2008 at 11:40
Let's stay realistic... there are lots of more important things that need more
work
right now.
Also, the idea of a switchboard seems very old-fashioned. How about giving the
OPTION
for an intercom to speak to another, but by default have intercoms broadcast to
the
general frequency, because not everyone will have a headset on them.
Speaking of which.... interesting idea... remove headsets on many crewmembers?
Issue
will be posted.
Original comment by pgol...@gmail.com
on 15 Aug 2008 at 3:30
I concur with pgoldin - doing "intercom patching" to simulate a phone call
could be
cool, but the default behavior is how most people would intend to use it
(broadcasting to everyone). I don't think adding all these additional channels
(in a
<30 person server) is worthwhile - though allowing radio-to-radio connections
(as
above) may be an idea.
Original comment by KelsonG...@gmail.com
on 15 Aug 2008 at 10:06
Original comment by KelsonG...@gmail.com
on 29 Aug 2008 at 2:26
Relevant Changes:
- lots of formatting changes
- patching occurs at the transmit stage
- all radios can establish "patch links"
- only intercoms take advantage of patches
- patching automatically sets the source freq
- changing frequency automatically drops patches
Original comment by KelsonG...@gmail.com
on 31 Aug 2008 at 3:15
Attachments:
Committed in rev 574
Original comment by KelsonG...@gmail.com
on 26 Oct 2008 at 5:22
Original issue reported on code.google.com by
Persh...@gmail.com
on 14 Aug 2008 at 10:21