Sure thing. Make sure you make backups prior to any changes you make.
The main file you want to focus on is "player_monitor.fsm" which is located in the system folder of dayz_code.pbo (extracted). Line 1115 is where the antihack is executed:
"[] execVM...
The teleporting to ocean after changing to bandit skin is the result of the anti-teleport. When you change skin, you are in fact been given a different unit to control hence why the anti-teleport is kicking in. There are steps to disable the anti-teleport in this thread.
How is this a database issue? I was under the impression that it would only be a database issue if the vehicles would revert back to their old state after a server restart. If you can't repair a vehicle during a session, it's most likely a issue with the dayz code itself right?
Hey man, are you able to elaborate?
When you say 'Damage [] not a number also hitpoints [] and fuel []", are you saying that are suppose to be a number or not?
In my example, the variables were quoted as the datatype for the damage, hitpoint and fuel fields in the database are VARCHAR opposed...
Server: Vanilla Chernarus
Hello, I've managed to successfully migrate players from Reality to Lite however I seem to be having issues with the tents. Here is a snippet of what was added to the object_data table:
INSERT INTO `object_data`...
I don't think it's worth it due to the fact it is killing legitimate players. I would love to know how to disable it though this wouldn't be the appropriate thread to discuss this.
I just noticed this in the RPT logs
23:57:31 "TELEPORT REVERT: PLAYER NAME (000000) from [6388.29,6559.97,0.00158691] to [6379.99,6576.8,0.00167847] now at [6388.29,6559.97,0.0015564]"
I feel as if the new inbuilt anti-teleport may have been causing the skin change issue/teleport to ocean issue.
Hey everyone.
I'm using Reality and I've noticed some issues since the 1.7.6.1 hotfix. I'm wanting to see if I'm the only one or if others are having the same issue as well.
Can't repair vehicles. Only have the option to repair windscreen
"Something went wrong" on connect
People teleporting...
Unfortunately, it's not the easiest thing to do to catch mass killers. The only thing I can recommend is, if you have an active admin, try to grab a screenshot of the player list on TSW when the mass kill happens. Then do a search for every player in your script.log. If your lucky, there...
Any variable in the that publicvariable list will appear in your scripts.log. This means that you need to make sure that you are not kicking for these variables via your scripts.txt as they will be generated for all players.
In this instance, you most likely have the following in your...
I like the idea but one question:
Lets say you have two characters; one in Panthera and one in Chernarus. What would happen when you die in Panthera and then switch maps to Chernarus. Would you end up being gearless in the middle of NWAF (or where ever your Chernarus character last logged...
That was where I was getting at. While they won't be in the logs, they will still show up in rcon. I have in the past compared player screenshots, straight after a server wide teleport/mass kill, with the scripts.log and found the culprit by seeing which name is missing from the log.
I feel as if pyBEscanner has got the platform already in place to detect those who use a battleeye bypass. Would it be difficult, since pyBEscanner is already scanning the scripts.log file, to record player names from the log as well? It would need to then compare that list with a player list...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.