The Membership Admin gui will do this as weel in that it allows you to make a racer a guest, visitor. full member or admin. Then you can just test that when they log on to see what permissions they have. No reason why it cannot be modified to be a license grading system as well.
There is no need to place this in default_1.ini : $ApprovedFile = "./Authorisation.txt";
I have just tested the code myself (with the new uploaded Lapper version 6.0.1.3) and I spotted a small error in the code I gave you earlier, this is the right code:
########################################## #New PLayer joining race or leaving pits)# ##########################################
Event OnNewPlayerJoin( $userName ) # Player event UserGroupFromFile( "authorised_users", "./Authorisation.txt" ); $userName = GetCurrentPlayerVar ( "UserName" ); IF( UserInGroup( "authorised_users",$userName ) != 1 ) THEN cmdLFS("/spec " . GetCurrentPlayerVar("Nickname") ); cmdLFS("/msg " . GetCurrentPlayerVar("Nickname") . "^3 not allowed on this server"); ENDIF EndEvent
Further you have to make sure the Authorisation.txt is in the same place as your LFSLapper.lpr file , and to put one username per line in the Authorisation.txt , like this:
Could you upload your LFSLapper.lpr file here?
You have to rename it to *.txt and then will be able to upload it, so I can have a look.
Which version of Lapper are you using?
I've tested your file in Lapper 6.0.1.2 and it's working instantly.
As soon as I try to join, I get the message that I am not allowed.
When I then put my name in the Authorisation.txt , I can immediatly join the server, without having to restart Lapper.
Does Lapper make any connection to your LFS server at all?
Have you opened an insim port on your LFS server?
To do that, type this into the LFS chat: /insim 29999
That portnumber must be the same as set in your default_1.ini
This is my LFSServers.cfg:
# Configuration of LFSServer to be Managed with LFSLapper # One line per server # Remote port is the port used to manage LFSLapper remotely, future extension # One remote port per LFSLapper on one machine, autoStart is optionnal #Unique ID|GroupId|Ip|Port|WorkDir|IniFile|autowork timeOutScript=10000; remotePort=3001; DEF1|gr1|127.0.0.1|29999|./default|default_1.ini|autowork
but this code !! I do not know why this still not working
I am surprised that it worked well with you
if you want take a look to server :saudi_arabia_criuse
maby there is something should we do inside (addonsused.lpr) or Something Missing.
include ("./gui.lpr"); include( "./utils.lpr"); include( "./myInc.lpr"); # Help GUI
#### Include for splitting infos #### #include( "./pitboard.lpr"); include( "./pitwindow_gui.lpr"); # OR #include( "./defPitInfo.lpr"); #####################################
#### Include for drifting infos #### #include( "./driftdef.lpr"); # OR #include( "./driftmeter.lpr"); #####################################
include ("./debug.lpr"); # GUI Framework main include - this MUST be first include ("./gui.lpr");
# Help GUI include ("./gui_help.lpr"); # Multi-tabbed help (all in one)
# Admin GUI include ("./gui_admin.lpr"); # Admin GUI root include include ("./gui_admin_membership.lpr"); # Admin GUI Membership administration include ("./gui_admin_handicaps.lpr"); # Admin GUI Handicap allocations
include ("./gui_help_cruise.lpr"); # Cruise help file (remove if not reqd) include( "./safetycar.lpr"); include( "./ctrack.lpr"); #include( "./Cruise.lpr"); #include( "./Cruise_Settings.lpr"); include( "./guiconfig.lpr"); include( "./racecontrol.lpr"); include( "./who.lpr"); include( "./tops.lpr"); include ("./cif/info_newbie.lpr"); include( "./listevent.lpr"); #include( "./winnerflags.lpr"); include( "./scripts.lpr"); include ("./cif/help_custom.lpr"); include ("./cif/help_stats.lpr"); include ("./cif/help_admin.lpr"); include ("./cif/help_general.lpr"); include ("./cif/info_mystats.lpr"); # MyStats Information include ("./cif/info_rules.lpr"); # Server Rules
Those are the log files of Lapper it self.
Inside the "default" directory, you will find another "logs" directory and I need the ERR file from there please.
Hmm, the log file doesn't show any problems regarding the event we are talking about.
So I only have one last solution, make a RAR file of the whole Lapper directory and upload it here.
I will download that and start your Lapper on a test server of mine.
I have tried to find the problem in your installation of Lapper, but it is so messed up, I gave up in the end.
I have created a new installation using Lapper 6.0.1.3 with the desired functionality we have been talking about all the time.
Download and unzip it, then customize the scripts to your likings and remember, files have a specific place for a reason, you can't just move them around, merge sub-directories etc.
im sorry to till u lfslapper u give me. not working at all !
1-Delete all files of old version
2-upload Lapper 6.0.1.3
3-unzip
4-i Edit only 2 file
LFSServers.cfg Edit
# Configuration of LFSServer to be Managed with LFSLapper # One line per server # Remote port is the port used to manage LFSLapper remotely, future extension # One remote port per LFSLapper on one machine, autoStart is optionnal #Unique ID|GroupId|Ip|Port|WorkDir|IniFile|autowork timeOutScript=2000; remotePort=3001; #DEF1|gr1|127.0.0.1|31993|./default|default_1.ini|autowork [B]^7Saudi_Arabia_Cruise[/B]|gr1|84.45.52.141|17684|./default|default_1.ini|autowork #SAC|gr1|127.0.0.1|17684|./default|default_1.ini|autowork
default_1.ini Edit
for exp
$password = "viktoor_lfs";
No problem bro its not very important if we did not find the solution : D
The Lapper I gave you is a clear download from this forum, in which I only added your server name (there is no need to put the name with colour tags there, nobody will see it) and insim port number. Then I added the code needed for authorisation and tested everything on a test server. So there is no way of it not working.
*edit*
I have currently 7 LFS server with Lapper running and I've written a lof of add-ons over the years, so I think I know my way around Lapper.
I'm sorry but I have invested enough time into this now and won't help you any further.
There appear to be a couple of issues, but the biggest seems to be a timing issue when lapper trying to save data - the error appears as Time Out in Event or Sub 2000 ms
<?php # Configuration of LFSServer to be Managed with LFSLapper # One line per server # Remote port is the port used to manage LFSLapper remotely, future extension # One remote port per LFSLapper on one machine, autoStart is optionnal #Unique ID|GroupId|Ip|Port|WorkDir|IniFile|autowork timeOutScript=2000; remotePort=3001; DEF1|gr1|127.0.0.1|29999|./default|default_1.ini|autowork ?>
sinanju .. i try it All of these numbers 2000 & 5000 & 10000 & 20000 . Still the same problem !!
welcom Gai-Luron
i think its all about 500servers coz when i want to press start lfslapper its takes long time to show me Running . also when i stop it . maby takes 30 sec !! for Minimum
You can't have 2 versions of lapper running at same time, which is what you're trying to do with one LFS server.
Stop one, and restart the other.
Unless there's something specific that you want in Krayy's V6.013, then I'd advise stopping that one, and leaving your original lapper running, as that's likely to be setup the way you want it and have developed it over last few months or so.
I would also advise that for any lapper changes you want to make, you try them on your local pc (127.0.0.1), then if you're happy everything appears to be working, then copy the amended files onto 500Servers.