I have been hosting alot of races lately, and having a great time with
up to 30 guys in a race. But, occasionally, there will be some IDIOT
that joins in that will ruin the race for most all. Starting with
language, Disrespecting everyone, then becoming an intentional "hack on
the track". Or, I have had several people qualify for the race, then
probably leave the computer to go do something else. So, their car sits
there at the start and gets run over. Not only once, but then again when
the leaders come by.
I'm sure you see where I'm going with this one. I want a button that
will allow the host to remove a driver from his server. And then block
him (or her) from joining that host again. Charlie, maybe you could
help us out here?
I don't think that it would get misused. If a host misuses it, he'll get
a bad reputation, then it wouldn't matter anyway.
Hitch-Hiker
Request for a way to eject disruptive NASCAR 3 drivers
Hitch-Hiker asked Papyrus for a way for hosts to remove abusive or deliberately wrecking drivers from N3 online races. Others pointed to the eject command in the GPL 1.1 patch, which N3 lacked, and debated blacklists and IP bans. One poster said Papyrus was working on unattended dedicated servers with remote control.
Automated summary.
Sometimes the cars that get disconnected are left on the track. So
possibly you could be blacklisting legit drivers.
dave henrie
Quoted text (18 lines)
> I have been hosting alot of races lately, and having a great time with > up to 30 guys in a race. But, occasionally, there will be some IDIOT > that joins in that will ruin the race for most all. Starting with > language, Disrespecting everyone, then becoming an intentional "hack on > the track". Or, I have had several people qualify for the race, then > probably leave the computer to go do something else. So, their car sits > there at the start and gets run over. Not only once, but then again when > the leaders come by. > I'm sure you see where I'm going with this one. I want a button that > will allow the host to remove a driver from his server. And then block > him (or her) from joining that host again. Charlie, maybe you could > help us out here? > I don't think that it would get misused. If a host misuses it, he'll get > a bad reputation, then it wouldn't matter anyway. > Hitch-HikerOn Sun, 03 Oct 1999 22:54:49 -0500, Hitch-Hiker
We've certainly experienced similar problems with on-line races in
Grand Prix Legends, so I can appreciate how annoying it can be.
Did either Grand Prix Legends patch solve the problem, by allowing the
host to remove a specific driver?
I'm surprised that Papyrus didn't include a 'remove' or 'ban' option
from the start, before releasing Nascar 3.
Perhaps they should have taken a look at rec.autos.simulators to see
some of the many complaints by Grand Prix Legends fans?
Best regards,
Brian Whitaker
Quoted text (16 lines)
>I have been hosting alot of races lately, and having a great time with >up to 30 guys in a race. But, occasionally, there will be some IDIOT >that joins in that will ruin the race for most all. Starting with >language, Disrespecting everyone, then becoming an intentional "hack on >the track". Or, I have had several people qualify for the race, then >probably leave the computer to go do something else. So, their car sits >there at the start and gets run over. Not only once, but then again when >the leaders come by. >I'm sure you see where I'm going with this one. I want a button that >will allow the host to remove a driver from his server. And then block >him (or her) from joining that host again. Charlie, maybe you could >help us out here? >I don't think that it would get misused. If a host misuses it, he'll get >a bad reputation, then it wouldn't matter anyway.I certainly agree 100%. Seems some guys only goal in entering a race is to
ruin it for everyone else. This happens very often. Just today I was
hosting a race at Martinsville, and I someone who could not keep up, got
frustrated and started chattering, constantly. Then he would just take guys
out. Absolutely, we need a kill button. Be great if we could actually get
the IP of the menace he could not join under an new driver and name. They
would actually have to get a new IP.
Quoted text (18 lines)
> I have been hosting alot of races lately, and having a great time with > up to 30 guys in a race. But, occasionally, there will be some IDIOT > that joins in that will ruin the race for most all. Starting with > language, Disrespecting everyone, then becoming an intentional "hack on > the track". Or, I have had several people qualify for the race, then > probably leave the computer to go do something else. So, their car sits > there at the start and gets run over. Not only once, but then again when > the leaders come by. > I'm sure you see where I'm going with this one. I want a button that > will allow the host to remove a driver from his server. And then block > him (or her) from joining that host again. Charlie, maybe you could > help us out here? > I don't think that it would get misused. If a host misuses it, he'll get > a bad reputation, then it wouldn't matter anyway. > Hitch-Hikersnipped lotsa true words
Rick, that won't work as many ppl (like me) get a new IP everytime they log
on to the Internet..............only solution again, same as in GPL:
passworded races with assorted drivers (http://www3.bc.sympatico.ca/GPLRC/)
and league-races. You will mostly get one or two idiots on board doing open
pickup-races......sadly, although things have vastly improved in GPL by now,
I have never seen a host use the "!eject"-command lately. Maybe there's a
slightly more mature audience in GPL?
cya
Maaki "still remembering some great battles at Spa with you" Stiepel
That would be far too harsh.
Best regards,
Brian Whitaker - ICQ, 51274367
Didn't the patch readme (the 1.1 patch, that is) mention that this was now
an option?
Here's a quote:
There was no way to eject a player from a server. Any boss may now remove a
player using the "!eject" command. The command should be entered as a chat
message. The format of the command is "!eject player", where player can
either be the "#" symbol along with the player's car number, or the players
name. For example,
"!eject #12"
"!eject smith"
"!eject f.smith"
"!eject fred.smith"
[end quote]
Perhaps you knew this, but it does answer half of your request. But there
doesn't seem to be a way to blacklist.
david
Quoted text (9 lines)
> >I certainly agree 100%. Seems some guys only goal in entering a race is to > >ruin it for everyone else. This happens very often. Just today I was > >hosting a race at Martinsville, and I someone who could not keep up, got > >frustrated and started chattering, constantly. Then he would just take guys > >out. Absolutely, we need a kill button. Be great if we could actually get > >the IP of the menace he could not join under an new driver and name. They > >would actually have to get a new IP. > That would be far too harsh.Quoted text (19 lines)
> Didn't the patch readme (the 1.1 patch, that is) mention that this was now > an option? > Here's a quote: > There was no way to eject a player from a server. Any boss may now remove a > player using the "!eject" command. The command should be entered as a chat > message. The format of the command is "!eject player", where player can > either be the "#" symbol along with the player's car number, or the players > name. For example, > "!eject #12" > "!eject smith" > "!eject f.smith" > "!eject fred.smith" > [end quote] > Perhaps you knew this, but it does answer half of your request. But there > doesn't seem to be a way to blacklist.Quoted text (9 lines)
>>I certainly agree 100%. Seems some guys only goal in entering a race is to >>ruin it for everyone else. This happens very often. Just today I was >>hosting a race at Martinsville, and I someone who could not keep up, got >>frustrated and started chattering, constantly. Then he would just take guys >>out. Absolutely, we need a kill button. Be great if we could actually get >>the IP of the menace he could not join under an new driver and name. They >>would actually have to get a new IP. >That would be far too harsh.Quoted text (12 lines)
> >>I certainly agree 100%. Seems some guys only goal in entering a race is to > >>ruin it for everyone else. This happens very often. Just today I was > >>hosting a race at Martinsville, and I someone who could not keep up, got > >>frustrated and started chattering, constantly. Then he would just take guys > >>out. Absolutely, we need a kill button. Be great if we could actually get > >>the IP of the menace he could not join under an new driver and name. They > >>would actually have to get a new IP. > >That would be far too harsh. > How would that be too harsh? If someone's DELIBERATELY taking people out, I > certainly wouldn't want him in MY race...I think DK made a mistake as to what sim you were talking about. What he is
describing is the 1.1 patch readme for GPL. N3 could definitly be enhanced
by something similar. Who knows, maybe in N3 V1.1 :)
David
> > Didn't the patch readme (the 1.1 patch, that is) mention that this was now
> > an option?
> > Here's a quote:
> > There was no way to eject a player from a server. Any boss may now remove a
> > player using the "!eject" command. The command should be entered as a chat
> > message. The format of the command is "!eject player", where player can
> > either be the "#" symbol along with the player's car number, or the players
there
> > doesn't seem to be a way to blacklist.
> Is this for N3? Does it work? Patch 1.1?
> Anyone know?
> H-H
Quoted text (9 lines)
> > name. For example, > > "!eject #12" > > "!eject smith" > > "!eject f.smith" > > "!eject fred.smith" > > [end quote] > > Perhaps you knew this, but it does answer half of your request. ButYou are thinking of the GPL 1.1 patch.
Regards
Rick
Quoted text (43 lines)
> Didn't the patch readme (the 1.1 patch, that is) mention that this was now > an option? > Here's a quote: > There was no way to eject a player from a server. Any boss may now remove a > player using the "!eject" command. The command should be entered as a chat > message. The format of the command is "!eject player", where player can > either be the "#" symbol along with the player's car number, or the players > name. For example, > "!eject #12" > "!eject smith" > "!eject f.smith" > "!eject fred.smith" > [end quote] > Perhaps you knew this, but it does answer half of your request. But there > doesn't seem to be a way to blacklist. > david > > I have been hosting alot of races lately, and having a great time with > > up to 30 guys in a race. But, occasionally, there will be some IDIOT > > that joins in that will ruin the race for most all. Starting with > > language, Disrespecting everyone, then becoming an intentional "hack on > > the track". Or, I have had several people qualify for the race, then > > probably leave the computer to go do something else. So, their car sits > > there at the start and gets run over. Not only once, but then again when > > the leaders come by. > > I'm sure you see where I'm going with this one. I want a button that > > will allow the host to remove a driver from his server. And then block > > him (or her) from joining that host again. Charlie, maybe you could > > help us out here? > > I don't think that it would get misused. If a host misuses it, he'll get > > a bad reputation, then it wouldn't matter anyway. > > Hitch-Hikerthat sounds like a great idea. On TEN they had a Muzzle button on the
server that allowed just that. I hate to say this but I long for those
ten days when you could actually talk to someone between races
Quoted text (18 lines)
> I have been hosting alot of races lately, and having a great time with > up to 30 guys in a race. But, occasionally, there will be some IDIOT > that joins in that will ruin the race for most all. Starting with > language, Disrespecting everyone, then becoming an intentional "hack on > the track". Or, I have had several people qualify for the race, then > probably leave the computer to go do something else. So, their car sits > there at the start and gets run over. Not only once, but then again when > the leaders come by. > I'm sure you see where I'm going with this one. I want a button that > will allow the host to remove a driver from his server. And then block > him (or her) from joining that host again. Charlie, maybe you could > help us out here? > I don't think that it would get misused. If a host misuses it, he'll get > a bad reputation, then it wouldn't matter anyway. > Hitch-HikerAGREED
in their living rooms watching on the tube :-)
I don't think I'd permanently KO someone for a few mistakes, he'd have to develop a
reputation before I'd put him on the shit list. It's usually not too hard to
separate the dedicated ***s from the beginners who are still just struggling
with car control and the rules in general, but have good intentions.
I too wonder if the same filtering process that took place with GPL on VROC will
happen with N3. I sort of doubt it. GPL is difficult to drive. Unless you put in
a lot of practice, it can be hard to keep the car on the track for a lap, let alone
an entire race. I doubt if it's much fun to try and***up a race for others
when you're spending 90% of it in the ditch without another car in sight. With N3,
especially at Talladega, pretty much anyone can drive an entire race, however
poorly, and there are always cars coming by. I've seen one guy idle along until
the guy he wanted to take out caught up and began to lap him, then swing over and
take them both out. Sometimes I really can't believe this shit. I also suspect
the sales volume for N3 will be much higher than GPL, consequently the ***
factor will be up there too.
All this aside, it's incredibly exciting when you DO get that one good race, with
clean drivers, and you battle right up to the checkers. This game has a lot of
potential.
Zog
Quoted text (25 lines)
> > >>I certainly agree 100%. Seems some guys only goal in entering a race is to > > >>ruin it for everyone else. This happens very often. Just today I was > > >>hosting a race at Martinsville, and I someone who could not keep up, got > > >>frustrated and started chattering, constantly. Then he would just take guys > > >>out. Absolutely, we need a kill button. Be great if we could actually get > > >>the IP of the menace he could not join under an new driver and name. They > > >>would actually have to get a new IP. > > >That would be far too harsh. > > How would that be too harsh? If someone's DELIBERATELY taking people out, I > > certainly wouldn't want him in MY race... > True, but what if you accidently make this huge brainfade mistake once and > because of that wont be able to race anymore. I guess it would turn ***. > There should at least be a "give the poor lad a second try button". > Look at GPL when it was released and VROC was launched. There was some problems > in the beginning with people ***ing up, but after time only the good racers > are left. If this will happen with N3 only time will tell, but I can see the > problem with N3 having so great many more users. > -- > Olav K. Malmin > remove spam when replyingWell, I posted this on the N3 newsgroup server but here it is again :)
At the moment Papyrus is working on what we call "unattended dedicated
servers". That is essentially what we know in the GPL community as remote
server control. That means you can control from an external PC the settings
of a dedicated server. At the moment we can assume (since it's was from the
last source I got) in alpha stage with NASCAR Legends, but it will include
many things that will probably be ported to N3.
Most of the code is based on the NROS server scripts, they were very
versatile and you had some great tools to use.
Here is some examples :
#82/eject ; eject driver #82
#82/lapremove ; remove a lap for driver #82
/drp_yellow ; force a yellow flag to be thrown on the track
#82/clr_black ; clear a black flag for #82 (you can also issue a BF)
Those are mostly remote command lines that "administrators" can do. You can
add or remove a lap to a driver. The server sets a password and that is the
pw needed to administrators to be able to get those command lines. FYI
there is a lot more stuff, mostly related to dedicated servers. You can
specify about everything like with GPL ; race length, temperature,
force_smoke for all clients, fixed setups, max latency, race password,
administration password, max client, yellow/pace/damage, etc.. Hopefully
even more things will be added to the list. This somehow gives us one of
the necessary item the N3 community requested, now the only thing(s) left is
a centralized chat and as a bonus some sort of ranking/GUi functions like
muzzle, profile, statistics, etc..
FYI, those are from almost-official sources and I can back-up them if you
want.
--
-- Fran?ois Mnard <ymenard>
-- May the Downforce be with you...
"People think it must be fun to be a super genius, but they don't realise
how hard it is to put up with all the idiots in the world."
<snip good server stuff> >
For, E<cough>d's benifit, no doubt ;-)
R
No, I don't mean an 'oops' in a fast corner. I'm talking about someone who
deliberately swerves into someone(even on a straight), or who drives backwards.
Is booting someone like that too strong? I don't think so...
Eldred
___
Tiger Stadium R.I.P. 1912-1999
Own Grand Prix Legends? Goto http://gpl.gamestats.com/vroc
If all the world's a stage, where is the audience sitting?
Remove SPAM-OFF to reply.
On Mon, 04 Oct 1999 12:21:11 -0400, Hitch-Hiker
I apologise. I didn't make myself clear.
Removing a player from a race would seem like a must for all on-line
simulators. I have commented on this in a previous post in this
thread.
What I believed to be too harsh was the proposal for on-line racers to
be able to view the IP address of the other on-line racers.
Best regards,
Brian Whitaker - ICQ, 51274367
Quoted text (12 lines)
>> >I certainly agree 100%. Seems some guys only goal in entering a race is to >> >ruin it for everyone else. This happens very often. Just today I was >> >hosting a race at Martinsville, and I someone who could not keep up, got >> >frustrated and started chattering, constantly. Then he would just take guys >> >out. Absolutely, we need a kill button. Be great if we could actually get >> >the IP of the menace he could not join under an new driver and name. They >> >would actually have to get a new IP. >> That would be far too harsh. >I would believe that just the fact of knowing the host could remove you from the >race would deter 90% of the problems before they start!Quoted text (8 lines)
>True, but what if you accidently make this huge brainfade mistake once and >because of that wont be able to race anymore. I guess it would turn ***. >There should at least be a "give the poor lad a second try button". >Look at GPL when it was released and VROC was launched. There was some problems >in the beginning with people ***ing up, but after time only the good racers >are left. If this will happen with N3 only time will tell, but I can see the >problem with N3 having so great many more users.hmm, I never did care for the TEN rankings system. Just about
everything there was good information to know but (imo) it was put
together and sorted wrong.
LPI.. LPI was good, but it was structured to continuously add laps. If I
remember right, you could theoretically have a LPI of 10,000/1(?) I
like the concept that's used with GPL... Novice, Int-Short, Int-Long,
Pro-short, Pro-Long, GP, length races. The math then would show how the
drivers got to that LPI. By way of never doing anything more then
Novice races, or by way of doing all of the lengths. There fore the LPI
wouldn't be misleading. Total number of laps was good as a separate
indicator for experience.
The over all ranking of Novice, Intermediate, Advanced, Pro, was good
but also a bit miss leading with the "Pro" selection. True that since
those drivers had all the numbers to show that they could race cleanly,
If I remember right, the number of total laps was added to the LPI and
their average finish positions and a few other odd numbers to get to the
Pro level. Using the formula they did it showed that these driver could
play a game rather well instead of showing that they could race rather
well. Basically, it was more biased towards those that finished very
high at the end of the races. All that was needed to be done was to
make sure only you finished the race and your numbers would then start
to sky rocket towards that "pro" level. It should have first been
restructured/settings renamed to Novice, Intermediate, Advanced, and
Experienced. The calculations should have included race settings
(novice, int-short, ect..), LPI for those settings, and ect.. showing
that driver A was a very good driver in the Novice length races.. Driver
A was a very good driver for the Int-short length races, and ect.. I
could go on but I haven't had my first cup of coffee yet...
I just hope that the possible new rankings system is set to show a
drivers true abilities rather then showing that he has been on the
system longest. And I hope it doesn't rank drivers as top dog, second
top dog, third top dog, ect.. I'd rather know that I'm racing against
good solid drivers then racing for a better over all position. The only
time the rankings of #1, #2...... are any good is when we are racing for
points in a league. The new rankings system should be biased towards
experience. (rankings of novice, intermediate, experienced, Advanced).
Just my opinions
Mike
--
=========================================
Mike Barlow of Barlow Racing?
=========================================
http://members.xoom.com/BarlowRacing/
Racing online with the help of......
Race Communications Association
Holodyne Engineering
Mystic Music
(have Your !!Name/Address!! placed here)
This absolutely killed us in a race I joined on Sunday. At the green 5 cars
sat there and stayed there. Then the ones still able to started intentionally
wrecking others. We need a patch for this big time!!!!!!!
--
Rich Koehler
rgkoehler(at)lucent(dot)com
killerk(at)home(dot)com
Quoted text (8 lines)
> I have been hosting alot of races lately, and having a great time with > up to 30 guys in a race. But, occasionally, there will be some IDIOT > that joins in that will ruin the race for most all. Starting with > language, Disrespecting everyone, then becoming an intentional "hack on > the track". Or, I have had several people qualify for the race, then > probably leave the computer to go do something else. So, their car sits > there at the start and gets run over. Not only once, but then again when > the leaders come by.How 'bouts putting Nascar3 (or whatever) in your message header so we know
what sim you're referring to?


































