Search results

That's what happens when you overwrite table data. You should have exported SQL table contents (not structure) out of it, then reimport after overwriting

Here's the fixed repo: github.com/rajkosto/DayZ-Private-Server Direct download link for fixed version: github.com/rajkosto/DayZ-Private-Server/archive/master.zip

It's because PWNZOR imported the new tables as INNODB, but FORGOT TO INCLUDE THE INNODB cache files into the repo. He should IMO stick with MyISAM, because they're actually more suitable for git storage (innodb storage is just a big, statically sized file, where MyISAM will store each table's...

There was a README.txt included in the package And you didn't read it. Neither did you read the post on page 2 that says you shouldnt just blindly overwrite your ini

Yes you have to change your character_data schema according to what was said in this thread, and use the latest HiveExt, like the one linked above your post

Latest version of HiveExt which should fix all these hangs and crashes (and also adds some features too): github.com/downloads/R4Z0R49/DayZMod/HiveExt_f0.9.6.10_p0.8.0.4.zip (also mentioned on the issue page of github.com/R4Z0R49/DayZMod/issues/115)

Another crashfix for those interested (with some extra features): github.com/downloads/R4Z0R49/DayZMod/HiveExt_f0.9.6.10_p0.8.0.4.zip (also mentioned on the issue page of github.com/R4Z0R49/DayZMod/issues/115)

Well... the only reason it would be larger than 170 is if hackers put their script code escaped in there... So maybe put it at something crazy like 2000 and then you know anyone with > 200 is a hacker

You used ancient antirocket-dumped SQL files when there were nice and updated ones available on my HiveExt github. I just now updated them to even more closely match the public hive SQL layout, have a look: github.com/rajkosto/hive/tree/master/Hive/SQL

You can do it either way +------------------------+-----------------------+ | MAX(LENGTH(Inventory)) | MAX(LENGTH(Backpack)) | +------------------------+-----------------------+ | 1929 | 763 | +------------------------+-----------------------+...

That's what i said one post above yours, after someone posted me their HiveExt.log, and said that he got the "server pack" from this thread. Change the field lengths to the "at least" values of the lines marked with "IMPORTANT !!!"

You are using an ancient SQL schema, see opendayz.net/index.php?threads/dayz-private-server-files-pack-1-7-4-4-all-current-maps-not-updated.28/page-2#post-4246 Increasing the field lengths for entries marked IMPORTANT will fix it.

Off-topic.

The default is 28800 seconds, which is 8 hours... Set it to amount of time you think your server will be empty for + 20% 10 minutes is ok so make it like 600

That's a warning, not an error. Errors are marked with [Error] After that warning you should have a "Reconnected with..." message that says everything is back on track This is caused by the wait_timeout being too low in your mysql server configuration

It's not stapo's. The fix is from github.com/R4Z0R49/DayZMod/issues/115 And it says DO NOT USE if you are NOT suffering from crashes, because it didnt go through the testing procedure.

You SHOULD use it if you get crashes. That's why its a CRASHfix.

Thanks for causing me problems Pwnzor I don't know WHERE you got this table layout, but it's wrong on a couple of different levels: Player_DATA: 1. Missing PlayerMorality in case it's used in the future Player_LOGIN: 1. PlayerUID can be NULL 2. CharacterID can be NULL 3. Datestamp can...

Don't overwrite your ini file then, genius. Maybe think before you post BIG FAT WARNINGS that others might heed.