Search results

kill the character and then try to log back in. if it created the character (most likely did when if failed to connect) it will place you in debug until you actually spawn in, which is when you will be moved to the right location.

Well that solves the issue with that then! I use 5.16 series on all of my servers. Note: it is highly recommended to turn off UAC prior to running setup_perl. It seems that some machines have an issue with actually elevating the command prompt properly and it fails for other reasons.

There is nothing in there other then an error in disconnect. I would rebuild and update the files again, also make your your dayzmod files are 1.7.7.1 and not 1.7.7 ( dayzcommander is nice for this portion )

http://www.armaholic.com/page.php?id=10390

Post your server log to pastebin or something similar and link it here.

Haha, nope, there are still one or two tweaks I need to do for this (kill messages are saying nil for the victim). So you can expect an update within a day or two as I track down the final issues. I am also going to be adding some new mods (gcam possibly)

Yeah, that's when i updated it.

This is not an error, this is how 1.7.7 works, it will cancel your logins until the server is ready to accept them.

GT500, if you are getting a missing dependency, then most likely you also have Active Perl installed as well. The only time I have ever seen this issue is when Active Perl was installed and then Strawberry Perl was installed after. When you attempt to run the setup_perl while it is installed...

Make sure to use the official Reality if you would like support in this forum. It has the latest version of files and all the filters are properly setup. It also has an update system for updating to the latest battleye scripts. Thanks!

Its done :)

You may now update to the latest version of Reality from the github. I will be posting it to the auto updater shortly. In case you do not have the URl here it is! https://github.com/thevisad/DayZ-Private-master

They are doing this to try and prevent any possible reverse engineering using old files.

You can use it, but it might take more tweaks to get some things working properly since so many things changed 176->177. Right now I know that there are issues with the killmsgs and most likely with the carepackages/wrecks loot system. I need to convert those over to the new process for loot...

I just spent about 5 minutes going through this. First thing I noticed is they removed a hell of a lot of code client side.

Well, look in other buildings (military) loot has now been spread to other buildings and doesn't spawn in defined locations anymore.

No problem, so much has changed with Reality in the past its kinda hard to keep up.

Honestly? Unless something has drastically changed and I do mean drastically, this should be incredibly easy to convert to the current build.

Can you elaborate a bit more? My stance has always been to not mod any default Dayz stuff and only add to it where needed. I can; however, relay some information regarding this to the dev group.

Ok, I am at work atm, Ill check into it later tonight when I am able to actually test this and see what the problem is. RDp sucks for testing the game since it is so slow. FYI, there is a new schema version needed for this.