Search results

What I mean is, delete the the following from the database: proc_AddWhiteListed proc_CheckWhiteList proc_GetWhitelisted proc_GetWhitelistLog proc_LogWhiteList proc_SetWhitelistedStatus Once you've deleted those, run your edited whitelist.install.sql file with 'dayz' replaced with 'root'.

This can be achieved with a few different MySQL queries. Try these: Players alive SELECT COUNT(`id`) AS 'total' FROM `survivor` WHERE `is_dead` = 0 AND `last_updated` > now() - INTERVAL 30 day; # Live players in last 30 days OR SELECT COUNT(`id`) AS 'total' FROM `survivor` WHERE `is_dead`...

Have you tried dropping (deleting) all of the procedures before running your SQL again? I'm not quite sure why the setup isn't working for you. Can you try to install this version to see if it works: http://uk8008.co.uk/files/DayzWhitelisterProPlusx86.zip

Let me just confirm a few things. You're using the 'root' user to login to your database? What is the name of the database you've created for the whitelist? Have most of the tables been created? or none at all? Let me know and I'll edit the whitelist.install.sql to suit your database server...

I'm glad it's working well for you guys. Quarterbreed, do you have .NET 4.0 installed? You need at least 4.0 to run this application. I'm almost certain it should run on XP. Try installing it here: http://www.microsoft.com/en-gb/download/details.aspx?id=17718 You also need to make sure you...

The error is clearly stating the user 'dayz' does not exist. That means that somewhere in whitelist.install.sql you're still referencing the user 'dayz'. You need to relace that with root.

If you log in with the username 'root', then use that. Also, I've updated the OP with the new release. Let me know if you find any bugs as I haven't had much time to test this version.

You need to be replacing all instances of 'dayz' with your database username, not database name. Give that a shot. I'll be releasing another version in a few minutes that access commands through any RCon client.

Same for me. I've also had several players combat log on me, again, with no combat log message. I know players could alt + tab out and end the process, but these players somehow just logged out to the lobby. So I have my doubts that this feature is working as intended.

If you check the 'logtypes' table, you should just have 2 entries. If you have 2, then you're all good.

Another great idea. I think the easiest way to do this would be to check for an admin message being sent that perhaps contains '#whitelist on' or '#whitelist off' and change the whitelist's status depending on the messages it recieves. I'll take a look at doing this tomorrow and keep you updated...

That's a great idea actually. I might do some work on it tonight. If I manage to get it working tonight I'll update this post with the new release. Thanks for the suggestion! :)

Not currently, no. This is something I'll add to the next release over the weekend.

I've found this no longer works that well with the latest version of Bliss. For example, the chernarus map no longer renders properly. Looking in the 'tiles' folder, the images no longer exist and have been replaced with a text file. Not really sure what's happening with this project. I used to...

Hi mate, I'm going to be attempting this soon aswell. From my understanding, unpacking, editing + repacking the pbo isn't enough. You need to rebuild bliss using build.pl after you've made the changes. If someone else with more knowledge could chime in on this, that'd be great as I'd like to...

DayZ Whitelist Pro Plus is a simple windows application that allows you restrict which players can join your server by adding their GUID. I've tried to make this application as simple as possible. Next Version The next version will start saving options like whether the whitelist was off last...

Hmm that's strange. What is your whitelist database name? Have you just tried to insert the tables and routines into the same database as your hive tables? Or have you created a separate database specifically for the whitelist? I'll have a look through the code later on this evening to see if...

Run this against your database: SHOW GRANTS FOR 'DBUSER'@'%'; which should return something like: GRANT ALL PRIVILEGES ON `whitelist`.* TO 'DBUSER'@'%' If you do see that you've been granted all privileges on your whitelist table, then I'll have to look into the code. Let me know.

That's strange. Are you using the same DB user in the whitelister as the one you can add new rows with? The error states "INSERT command denied to user 'DBNAME'@'MYIP' for table 'log'" which tells me whichever user you're logging in as on the whitelister, doesn't have permission to insert rows...

Can you add new rows manually from a database client like HeidiSQL or phpMyAdmin?