On Sat, 14 Nov 2009, Erik Hofman wrote:
You could compare it to an IRC channel where users can get ignored,
kicked and even banned. Not that I'm propagating a kicking or banning
facility but making them invisible for others (may be even upon request
of the user) may provide a nice way for
On 14 Nov 2009, at 11:08, Anders Gidenstam wrote:
Access to these properties could e.g. be via the pilot list as for MP-chat
ignore.
I'm not entirely sure it is a good idea to add this, though. OTOH if I
really do not want to see or hear pilot X, then why not give me the option
to
Perhaps by adding a
/ai/models/multiplayer/controls/show-model
property (or similar) to each multiplayer entry that defaults to true
(show) but can be set to false to hide the model of that pilot.
Access to these properties could e.g. be via the pilot list as for MP-chat
ignore.
I'm not
On Sat, 2009-11-14 at 13:02 +0100, Torsten Dreyer wrote:
Yes, I also thought it sounded like groups, but I was thinking that
the client would send
a list of group-name strings that a user wanted to be part of when
it sends the pilot call-sign and aircraft type information.
This would
Hi Torsten
That's an interesting concept, I was thinking about groups as well.
But instead of writing extra code on top of the current client and server,
could we use different ports on the server?
Let me explain: if I understand correctly, the server already allows
connection to port 5002 for
5 matches
Mail list logo
