joe201x
-
Posts
34 -
Joined
-
Last visited
Content Type
Profiles
Forums
Articles
Posts posted by joe201x
-
-
works great nice one
-
Still epoch autobans non admins even with all the battleeye exceptions, no errors showing in log
-
I had the zcp issue, make sure you havent double pbo'd it like x/epochhive/addons/zcp.pbo/x/epochhive/addons/zcp.pbo
should be x/epochhive/addons/zcp.pbo
-
my server spams this in rpt on startup after restart and it makes the server take ages to boot, any idea how to fix?
15:44:33 Error: Object(5 : 2) not found
15:44:33 Error: Object(5 : 3) not found
15:44:33 Error: Object(5 : 4) not found
15:44:33 Error: Object(5 : 5) not found
15:44:33 Error: Object(5 : 6) not found
15:44:33 Error: Object(5 : 7) not found
15:44:33 Error: Object(5 : 8) not found -
same as me ^^
-
epoch autoban #0 for every non admin that joins my server and I get this in log;
16:10:10 BattlEye Server: Script Log: #0 Trevayne (0c5e9766fbe55174f195e906d0a7387f) - #22 "leLineNumbers "scripts\ActionMenu\SC_compileMenu.sqf";16:10:10 [true] ExecVM "scripts\ActionMenu\SC_startMenu.sqf"; -
is the event menu with this?
-
I think it may be my database, I cant seem to connect to it. any idea what could cause it not to work and how to start it?
-
anyone?
-
still cant get it to work, I've tried all variations of start up parameters and my server still only gets to this and then crashes;
"10:13:02 [ZCP]: Capture Points is fully running.10:13:02 "#SEM INIT: Initialize Simple Epoch Missions"10:13:02 "#SEM Version 0.8.3 is running on Arma3 "dedicated server" version 1.42 [130244] Stable branch."10:13:02 "Epoch: Starting ArmA3 Epoch Server, Version 0.3.0.2" -
got it, thank you
-
dont that and now I get this in rpt
7:07:44 Item str_a3_flashlight1 listed twice
7:07:48 Warning Message: Addon 'A3_emod' requires addon 'A3_epoch_code' -
okay thank you i will read
-
just tried to run default chernarus and nope, I have checked my server.cfg and it is right. I have no idea what this is
-
yes, all thats in there is my epoch.Tavi.pbo and I updated the description.ext as it says to
-
after updating my server to the latest epoch patch 0.3.0.2 and updated it to the latest arma 3 patch my server wont work, instead of saying 0/70 players it says 0/64 and has no server information and cant join. I have checked my server.cfg and mission files over and over and cant find what it is, my rpt reads this at the end and doesnt go any further;
" 6:30:04 Attempt to override final function - bis_fnc_init6:30:04 EPE manager release (0|0|0)6:30:04 EPE manager release (0|0|0)6:30:06 VoteThreshold must be in 0..1 range. Defaulting to 0.56:30:06 Initializing Steam server - Game Port: 11802, Steam Query Port: 11803" -
@BenR, I see. I was told to do this by somebody,
"Change the file in a3_epoch_server.pbo in the folder compile/trading/ something like makenpctrade.sqf, change all cfgPricing "configfile" to "missionconfigfile"
Use emod, and precompilefinished the client side addtotrader.sqf aswel, and change all cfgPricing "configfile" to "missionconfigfile" again.
Then copy the cfgpricing from client file epoch_config.pbo, unpack pbo, unrap the config.bin and put cfgpricing into the mission file."
however when i attempted it, after i changed the 'configfile' parts to 'missionconfigfile' in the makenpctrade it broke my server, any idea?
-
I see, deadz servers have it working though?
-
-
-
here is the end of my config.cpp i have not edited anything else but the end http://pastebin.com/tynmCPiQ
-
I have edited the config.pp, could that be causing it?
-
my a3 taviana overpoch server gets stuck on 'please wait loading epoch' every time i load in then get kicked for 'server not ready' i had set the mission pbo to default to see if it was an error in that causing it and still no difference, i also cant see anything in the rpt. anyone know why?
-
what do you mean by go through it one at a time? what else can i do other than change 7 to something else? thanks.
Easy Kill feed/messages w/study & bury body function (Beta)
in Scripts
Posted
installed today, when players join they got autobanned with 'epoch autoban #0', this is what came up in log