Closed azynkron closed 5 years ago
I guess this tool is dead. Uninstalling.
First off, it's 630 am for me. For second, if you don't see it your formatting could be wrong. What's your superadmins.txt look like?
It's been 06:30 for two days? What time zone do you live in?
From: Larry notifications@github.com Sent: Wednesday, June 26, 2019 12:31 PM To: VanillaPlusPlus/VPP-Admin-Tools Cc: azynkron; Author Subject: Re: [VanillaPlusPlus/VPP-Admin-Tools] Admin menu won't open (#6)
First off, it's 630 am for me. For second, if you don't see it your formatting could be wrong. What's your superadmins.txt look like?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/VanillaPlusPlus/VPP-Admin-Tools/issues/6?email_source=notifications&email_token=AMLLGG5WSITECDW33TANYODP4NOTHA5CNFSM4H24DR7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYTLTYA#issuecomment-505854432, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMLLGG7CMLWDAKKD6OFRBG3P4NOTHANCNFSM4H24DR7A.
Make sure the steam64 id actually leads to your profile.
Make sure you placed your id in the EXACT same way as we have the default generated IDs
with NO spaces after the ID or between the |
and the rest of the ID
Once you run the server, check the logs in your server profile. scripts_%timestamp% and look if your ID is there, if it is then you have successfully done the most simple thing in the world. :)
Well, that was the first thing I checked.. for typos. I've run Arma servers for years so I'm aware of how sensitive they are and how easy it is to miss a single line.
The logs say SCRIPT : Adding SuperAdmin: BadTrip GUID: 76561197994947226 To the SuperAdmin List!
So, that part works but the menu isn't. Anyway.. Thanks for the reply.
From: Da0ne notifications@github.com Sent: Wednesday, June 26, 2019 4:20 PM To: VanillaPlusPlus/VPP-Admin-Tools Cc: azynkron; Author Subject: Re: [VanillaPlusPlus/VPP-Admin-Tools] Admin menu won't open (#6)
Closed #6https://github.com/VanillaPlusPlus/VPP-Admin-Tools/issues/6.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/VanillaPlusPlus/VPP-Admin-Tools/issues/6?email_source=notifications&email_token=AMLLGG2ARBBCVBI2HLWNHCTP4OJOLA5CNFSM4H24DR7KYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOSGC62PQ#event-2441473342, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMLLGG22D3M4GPIY73PLDS3P4OJOLANCNFSM4H24DR7A.
What's your client start up command line?
I'm having the same issue, and I'd really like to fix it. This appears for my ID in logs
16:7:41 | [PermissionManager] Adding Super Admin (765611988076xxxxx)
...
18:11:6 | Player "xxxx" (steamId=765611988076xxxxx) connected to server!
and in the scripts log I get this
SCRIPT : string log = '2022/11/5 | [VPPAdminTools] Player 765611988076xxxxx attempted login, and failed! Total Attempts: 2'
SCRIPT : string log = '2022/11/5 | [VPPAdminTools] Player 765611988076xxxxx attempted login, and failed! Total Attempts: 3'
Running in Nitrado, startup command is
== C:\SERVICES\*********_SHARE\ftproot\dayzstandalone\DayZServer_x64.exe
== "C:\SERVICES\*********_SHARE\ftproot\dayzstandalone\DayZServer_x64.exe" -ip=*********.24 -port=********* -cpuCount=4 -limitFPS=100 -adminlog -config=serverDZ.cfg "-mod=@CF;@Community-Online-Tools;@Dabs-Framework;@VPPAdminTools;*******************;@WindstridesClothingPack" -profiles=C:\SERVICES\************_SHARE\ftproot\dayzstandalone/config -BEPath=C:\SERVICES\*****************_SHARE\ftproot\dayzstandalone\battleye -noFilePatching -dologs -VMErrorMode "log_only" -freezecheck
Edit: the behaviour isnt consistent. After certain restarts it works just fine, I havent noticed whether there's something about the order of admins that would make it work or not,
(Using DayZ 1.03) I can't get the admin menu to open.
Nothing happens. Is there a debug log somewhere so I can see where it goes wrong? I'm experimenting on a LAN server right now if that matters.