I really wouldn't advise editing police.txt unless you know what you're doing...it has a particular system of storing names, and it has to be stored like that
-
(ReVoX)
DELETED
by the_angry_angel : Cleaning the thread.
-
(BOSCHO)
DELETED
by the_angry_angel : Cleaning the thread.
-
(ReVoX)
DELETED
by the_angry_angel : Cleaning the thread.
-
(BOSCHO)
DELETED
by the_angry_angel : Cleaning the thread.
-
(ReVoX)
DELETED
by the_angry_angel : Cleaning the thread.
-
(BOSCHO)
DELETED
by the_angry_angel : Cleaning the thread.
-
(dougie-lampkin)
DELETED
by the_angry_angel : Cleaning the thread.
-
(BOSCHO)
DELETED
by the_angry_angel : Cleaning the thread.
-
(dougie-lampkin)
DELETED
by the_angry_angel : Cleaning the thread.
-
(BOSCHO)
DELETED
by the_angry_angel : Cleaning the thread.
As I've said, you can't get the layout. It was made privately, so I can't release it.
You can't really do that without a lot of work...InSim allows you to take the XY position of each player, and the current Node of each player. But of course, the tracks aren't all straight lines perpendicular to each other, so using XY would be very hard, and take ages. The Nodes can't split the track in half, they just tell you what "sector" of the track you're in
I switched to MySql just because it is easier to handle then flat files. Also I was getting annoyed that when a person have no cars it doesn't add them to Connections. (Causing many many problems with collisions from a person ingame not being in Connections)
Now there is a 8 Players limit (not connections).
What happens is when you have 9+ people on the track. you have a line like this
for (int i = 0; i < Players.Count; i++)
loop through MCI 9+ times when it itself has only 8 elements. giving you an index out of bounds of array error.
I fixed this by completely rewriting how you handle MCI. (Also my rewrite makes it run faster :P).
-
(Mikjen)
DELETED
by the_angry_angel : Cleaning the thread.
-
(ReVoX)
DELETED
by the_angry_angel : Cleaning the thread.
Could you PM me with the changes you made? I'm curious as to what the problem was. If you don't want the fix to be included in this project in the future though, that's no problem. The PM will stay private
Do you actually know how to use Visual Studio
You have to upload the exe, why is the source even on the server
-
(Mikjen)
DELETED
by the_angry_angel : Cleaning the thread.
-
(Mikjen)
DELETED
by the_angry_angel : Cleaning the thread.
When a racer starts a client-host (so not a dedi host), that racer becomes the 'host user' that runs the host. This user cannot be banned or kicked, but the insim application doesn't take this into consideration. When the application tries to ban this user for some reason, it ends up in an infinite banning loop. This loop will not ban or kick the user but it will cause ban statistics to be sent to LFS World. This in turn causes an instant 30day master ban for that user.
So this requires fixing. Mostly because this appears to happen quite frequently.
It's very easy to detect whether a user (a connection) is local or remote. When you get an NCN packet, just look at the Flags byte to determine if a connection is a local one or a remote one. Store this flag with every connection and then when the application tries to ban someone, skip the ban if the user is local. Only allow bans on remote connections.
Until this is rectified..... Just put into the inSim App if the user is an admin, dont pass the banning function call onto him, just give a message instead if you have to do something to this guy offending and remove what ever it is causing the ban. What is it negative cash or something? A simple if<>Then<>rule will take care of this before the /ban call is executed.
or just blame dougie lol
Actually no, the ppl running this should be using dedi host. SERIOUSLY !
Yes, I assumed that those using this would be on dedi's, I didn't even think of this... The only time a /ban was called was at negative cash, and /kick was only called at spectating.
Anyway, here's the fixed version. v1.0.2 has also been modified to include the fix. If you don't want to start again, please make sure to take a look anyway, and then fix your own version...
-
(shaun463)
DELETED
by the_angry_angel : Cleaning the thread.
-
(Mikjen)
DELETED
by the_angry_angel : Cleaning the thread.
-
(Victor)
DELETED
by the_angry_angel : Cleaning the thread.
-
(elmohellno)
DELETED
by the_angry_angel : Cleaning the thread.
-
(Ca18Slider)
DELETED
by the_angry_angel : Cleaning the thread.
-
Cant Add Officers, (jackd)
DELETED
by the_angry_angel : Cleaning the thread.
-
(Evilvan911)
DELETED
by the_angry_angel : Cleaning the thread.
-
(Mikjen)
DELETED
by the_angry_angel : Cleaning the thread.
I don't know what you mean by 'Car renting problem', but there is a little bug I found in LFS_External when I used to use it. I thought It had been fixed, but I just checked and it hasn't. Anyway, Look for the following code in LFS_External....
if you rent more then 1 car, the last person to rent will be effected by everyone that rented before (Fined, money,etc).
lol I rewrote your whole example dougie.
It goes a lot faster if you don't stick 1000 things in MCI receive :P.
I think I'll post an example of how I rewrote the command system in this section later. Anyone interested? It makes it a lot easier to add more commands and keep them organized.
-
(Sheepy1977)
DELETED
by the_angry_angel : Cleaning the thread.
-
(elmohellno)
DELETED
by the_angry_angel : Cleaning the thread.
-
(Sheepy1977)
DELETED
by the_angry_angel : Cleaning the thread.
-
problem with !cadet. (Evilvan911)
DELETED
by the_angry_angel : Cleaning the thread.
-
(dougie-lampkin)
DELETED
by the_angry_angel : Cleaning the thread.
-
(Evilvan911)
DELETED
by the_angry_angel : Cleaning the thread.
Okay guys i got an error from the LFS_External_Client.exe , a box pop and told me "MCI- L'index se trouve en dehors des limites du tableau." Translated mean "Index goin out of the table limit" or something like that... anyones can help me please thanks you
People have been reporting this, but it hasn't happened to me. Until it does, I can't fix it. Maybe someone who already fixed it could post an updated version?