Luigi Auriemma

Hello :)

Could some one please give me a guide how to run that sampfp ?

i found some guide via RUN->CMD
but didn't understand exactly what to do next.

what i did:

• run->cmd->cd\
• when after cd\ i typed location:
  Documents and Settings\Luxeon\Desktop\sampfp.exe
  ,so it looked like:
  
  C:\>Documents and Settings\Luxeon\Desktop\sampfp.exe
  
• i got error:
  'Documents' is not recognized as an internal or external command,
  operable program or batch file.
  
• then C:\> appeared again

What is wrong? ;>
thanks,
Jaanus

you have forgotten to specify the cd command before the path and using the " before and after the path to delimit it.
anyway you have problems using the command-line and not the tools, so check on internet for help not here

got it working, but now i get this:

uhmm version 0.2X of samp is not supported yet, this is probably the cause

updated sampfp with support to the new server version

thanks ,i will test it asap and tell if it works correctly :)

off topic if it is 'off' ;) :

suggestion to add limiter of 'fake players'
like:
C:\destination\sampfp.exe IP:PORT NUMBER_OF_PLAYERS_TO_ADD


edit:

it sends sockets (players) ,but i do not see them on server (tried 2 servers+ own 127.0.1.0)

it sends till server is full ,then it writes it is full and then again sends till it gets full (but irl it doesn't get full - nothing happens)

they are "invisible fake players" because it's used only the first part of the connection which gets the free slot

should it crash server then or add ping ?

no

what it should do then? :o

hmm..at least i could :o
re-test it - i give 100% i could !

maybe fake player just left. i haven't really used THIS one, but this is what invisible fake players do. you have to run like 2 or more instances to really fill a server so nobody can join. it should show the message that server is full, then you are unable to join.

I think that if you have reserved slot, then you can still join reserved slot (fp tools don't fill reserved slots, cuz usually it needs permission or something like that)

I got it to work...sometimes, its just that when the cmd reaches server full, it just doesnt remain stable, it says server full, then carrys on filling the server were it says again, server full, then refills etc etc, then after about 45secs, it says "unknown packet" followed by a number, sometimes its 2 sometimes its 46, I get mostly 46, but when it does say server full and I connect to that server it says, server full, so I know its working.

if useful I can remove the termination of the tool when the unknown packet is received

That might work, so if any random unknown packet number was received, it would just carry on filling the slots? if you could stop the termination when that happens, that would be great.

ok I have released the new version, in short now it reports the "unknown packet" alert but doesn't quit.
anyway with the -f option this problem didn't exist

It lasts longer, but when it does receive an unknow packet and skips it, another unknown packet comes along then again then again and eventurly times out.

Also how do I make a picture attachment like jaanus did above, you can see exactly what the cmd prompt says then.

I guessed that was a bad idea (or an useless thing) to remove that termination, anyway try with -f.

for the image it's enough that you attach to the post using the "Add the file" of "Post Reply"

Does this -f acturly fill the server?, because it never says server full, just player: . everytime.

sure, the -f option ignores the receiving of the reply packet from the server (that's why it doesn't say if the server is full, it simply can't know it) and creates a new player each 100 milliseconds

Ok, well I just gave it a try with 20 instances, all flooding the server, but when I attempt to join, I can get on perfectly, as well as other people.

I tried that, however without the -f the whole thing just spirals out to a timeout, you receieve one unknow packet then another then another and everuturly times out, I also tried 20 instances, only 5 managed to work, but then those 5 did the same thing, spiraled to a timeout because of the unknown packets.

the only thing I can say is that there is no difference in the packets sent with -f and without it.
the situation you describe seems more like a "protection" on the server, in fact if you run your server locally you can see the success of the "fake players" attack without problems

How do I acheive this.