Search results

There are only so many spawn points however. If you increase limit_max for a vehicle past the number of spawn points for that vehicle then you can get multiple vehicles spawning on top of each other.

I understand this is frustrating. To find why the migration is failing you can run the migration SQL code manually. db_migrate.pl looks in schema/Reality/mysql and runs the SQL files in order that it finds. Let's try manually updating from 0.13 to 0.14. 10_spawns_heli.sql insert ignore into...

The migration or Reality schema didn't update from 0.13 so I think it is dying on the first migration step, executing the SQL files in schema/Reality/mysql/0.13-0.14. Do you have full rights granted to your database user? Run this in your SQL program. SHOW GRANTS FOR 'USER'@'HOST'; Where USER...

OK, try this but backup your database first. This should let db_migrate work. It thinks you are at version 0.01 but you are at 0.13. UPDATE migration_schema_version SET version = '0.130000' WHERE name = 'Reality'; Now try to run db_migrate.pl perl db_migrate.pl --name DBNAME --host DBHOST...

Wow, that is a really, really old Bliss database version. I'm not even sure how Bliss 1.7.4.4 would have worked on that old of a version. This will require some magic to fix but I need some more information first. How did you maintain your Bliss database? Did you run db_migrate.pl each time...

Unfortunately the perl package is hiding the MySQL error. If you could run the follow SQL queries (via navicat or something) and paste the output here that might help me understand what is going on. SELECT * FROM migration_schema_version; SELECT * FROM migration_schema_log;

Which tool?

Take a look at BlissAdmin, you can see how it is done there. https://github.com/R4Z0R49/BlissAdmin

Have you looked at BlissAdmin? It includes a Google Maps style map with optional player/vehicle tracking. https://github.com/R4Z0R49/BlissAdmin I'm not familiar with dayz.st hosting but there might be something in BlissAdmin you can use.

Can you screenshot the error message?

It looks like you did not grant permissions for the user. Do you see the appropriate grants? SHOW GRATNS FOR 'Dayz'@'HOST1';

Each vehicle has a certain chance of spawning each time the spawn script is ran. In theory if you ran the script enough times with the limit 89 or greater you would get all of the default vehicles spawned in. mysql> SELECT COUNT(*) FROM world_vehicle WHERE world_id = 1; +----------+ | count(*)...

If you are upgrading an existing Bliss database then skip step #6 of the Automatic Installation instructions. I haven't used the control panel but it sounds like it may be hiding the errors from you. In step #7 you can set your MySQL parameters, including the port. Does step #8 work for you?

Posting the exact error messages you see would most likely help us help you.

I know. All that over a missing semicolon. :(

It looks like your backup of the survivor table drops and recreates the table and it is now missing a column. Try running schema/Reality/mysql/0.37-0.38/20_survivor.sql manually against your database to add the missing column.

OK, I found the issue. This is related to a couple edits I did to pkg/killmsgs/compile/server_playerDied.sqf. When I turned off global death message I broke player death. Derp.

This is my character in survivor table after dying in game. I can login and die over and over and over and over.... but never die in the database so I just respawn as is next to my dead body. *************************** 1. row *************************** id: 1865 unique_id...

I've been testing this off and on all day and am now even more confused. :( I can't die on my main (upgraded from Bliss) database. Sometimes if I make a fresh database I can die, other times I can't. There doesn't seem to be any consistency to it. Am I the only one having this issue...

I'll test this again after you fix https://github.com/thevisad/DayZ-Private-master/issues/63 as they may be related.