Search results

Works fine Also there is debug info in the file i linked i.e If u look @ clients rpt logs appdata/local/arma oa/rpt log u will see a bunch of xxxxxxx.p3d or something similar each time u try to chop wood... It is basicly listing all the objects within 30 meters of player, when u try to...

Shrugs @ not allowing people to see the logs that they caught by... But i personnally hope u don't add people to banzunion banlist over solely having a public variable weapon restriction. Since it is rather easy for an innocent player to get caught by that one i.e picking up wrong weapons from...

Love the news of a github repo to submit ideas / changes i.e similar to Lingor / Offical Dayz ones... Always nice to help out espeically when people find the odd fix / improvement etc.. Waiting patiently on release..

rcon error is different thing altogether.... Just highlights a problem with the C# app, it just logs onto server sends it reloadbans & disconnects. It doesn't add bans to bans.txt https://github.com/Torndeco/pyBEscanner/blob/master/modules/bans.py#L186-L201 It is in the same small block of...

edit: To clarify pyBEscanner doesn't rescan log files... In console u will see the following as a ban is added ( u can ingnore the start messages etc. Ban Added: xxxxxxxxxxxxxxxxxxxxxxxxxxxxx This happens when a new ban added to bans.txt... -------------------------------------...

Default behaviour for dayz checks if the ground = defined as forest area. Try mission fix the chopwood.sqf.. http://opendayz.net/index.php?threads/chopping-wood-fix-v0-1.7757/ Its a chopwood.sqf i made up for Sahrani map... find some empty space & try to chop some wood... Then check a...

Just need to remove the entries from bans.txt afterwards i.e Ban gets added to bans.txt But server never receives reloadbans, no-one gets banned... Makes it handy todo while server = running & u can alter the rules till they are right ----- As for 1.7.5.1 changes.... He does have a point u...

Hint u change the rcon username + password to something rubbish... That way pyBEscanner can't ban kick or ban anyone + u can update the rules & review the logs etc... Just need to remove the entries from bans.txt afterwards

Seriously ? Look @ the rules files for pyBEscanner They aren't complicated... Update the rules for 1.7.5.1 & send a pull request with the new exceptions for dayz 1.7.5.1 Or update your battleye filters to filter out the new zombie types + new backpack (since it already filters out the rest...

Its a new backpack in 1.7.5.1 They aren't filtering the DZ_TK_Assault_Pack_EP1 out in CBL filters yet. Or u could just add the exception to your pyBE rules for createvehicle spam

Its just arma complaining the battleye log file = missing when it goes to append a log entry to it... Never seen it cause any issues yet, except the odd warning about it... i.e used the same method of moving log files & then scanning them since day 1 I look into rewriting the scanning code to...

@norsk2277 pyBEscanner should have no problems running on windows / linux (needs mono). Just remember to run it in a console, that way if it crashs / stops u can see the reason why. ------------------ ------------------ @Everyone else Updated Conf Info for for IP Ban Time. Turns on i...

Just add the chop fix @ last restart like 30 mins ago Before that it was broken for like 12 hours on the server :p edit:- If u found an area with 3 or more tress that u can't harvest give me a shout. Did a quick test & looks good

Its pretty much the chopping wood fix from tavianna.com, just altered the strings for the trees used in sara map... Basicly instead of dayz standard chop wood check floor surface = forest... The fix checks all objects within 30 metres + if they match the string for tress. If it find 3 matchs...

@Richie Are u launching beta/expansion/armaoaserver exe ? (i.e that is the one that is patched using beta patchs) Believe there was a beta patch that removed that needed sm2 shader support from server exe

Player spawn code isn't that hard.. Just change up the spawn locations is half the battle in the mission file.. Then u can alter the code to read more than 4-5 markers for spawn locations.. Also can change up the conditions for finding a spot i.e not to look only @ shore spots so u can spawn...

There is also another typo mistake.. i.e class Land_bouda2_vnitrek : Farm { maxRoaming = 2; lootPos[] = {{-1.34631 1.36914, -0.610504}, {0.775391, -1.76465, -0.610504}}; }; First position, has no comma... Looks like a copy/paste Dayz code ends up reading this as a...

Question does this app auto send reload bans to server ? Any chance to add option to disable this if possible thx

Just incase any admins have this thread watched.. Have a workaround fix for some of the bugged loot positions @ http://opendayz.net/index.php?threads/loot-bug-fix-for-v-0-1.7697/

This is a client mission bug fix for 0.1 There is typos in the loot arrays basicly i.e class Land_ammostore2 : Military { maxRoaming = 2; lootPos[] = {-0.383789, -2.19238, -2.72875}; should be class Land_ammostore2 : Military { maxRoaming = 2...