Try searching for 5 "nest_" and adding the ones with nest_ in them to that too.
Also, you may want to check 5 "B_" for the camo net B variants, and 5 "Fort_" for the ones with fort_ in them. Note, they may be 1s instead of 5s.
Ah sorry, totally forgot about that part haha. What schema are you running that you don't already have the needed tables?
If you've not got them, then you'll need two tables; 'deployable' and 'instance_deployable'. You can run this as an SQL query to create the tables.
CREATE TABLE IF NOT...
The only dayz_server file to change was server_monitor.sqf, and the only change to the mission files was the change in version number so you don't really need to start all over again. :)
Oh, though for 1.8.0.3 don't use the file SchwEde linked as the 1.8.0.3 file works great now. I've updated...
It may, not all files change when updates are released, so I can't tell for sure if fn_selfActions will be updated in the new Epoch version or not. However, your mission files probably will be so you'd need to reinstall any scripts you're running on updated mission files anyhoo. :)
You're looking for your arma 2 operation arrowhead install\@dayz_epoch\addons\dayz_code.pbo
If it's done through steam it should be in your steamapps\common\arma 2 operation arrowhead
You may want to check the server or client RPT logs to see why you can't connect. There are two things I can think of off the top of my head that usually cause the hang at wait for host. Description.ext hasn't been edited properly, or you're actually getting a BE kick and it's not telling you...
Ok, that means you've used the wrong fn_selfActions.sqf, which means you probably have the wrong compiles.sqf still too if you took them both from the same place.
You have to take them both from @DayZ_Epoch\addons\dayz_code.pbo\
Hmm, errors are never a good thing haha. What is the error it's coming up with? I've noticed that sometimes you get an error, and then if you restart it doesn't happen again. DayZ/Arma at it's finest. :)
You don't need to worry about making it a .pbo, just edit the files in the folder (still make backups where possible because it's always better to be safe) and it will work straight from the folder.
Yeah, sorry I didn't mean literally from, meant as in I don't know what mod it was supposed to be running because it certainly wasn't an Epoch mission file. The only part of it that seemed ok was the init.sqf.
Ok, looking at that zip, I think the mission file you should be editing is either the folder called DayZ_Epoch_11.Chernarus or the one called DayZ_Epoch_17.Chernarus since those are actually proper Epoch mission files. I'm not too sure what that one you were using was from.
There should be...
Ok, so you've got the files in the right place now. But it's still not working? Did you put the .pbo you sent me in there, or did you find the correct .pbo in there?
Well that mission.sqm is a 1.8 file. I wouldn't recommend using it with Epoch since it may cause unforseen problems or just prevent connecting all together.
Inside the MPmissions directory, you should have the dayz_1.chernarus.pbo or a dayz_1.chernarus folder. If not, then I don't have a clue...
I think the latest version of Epoch is 1.0.2.3
This may be a stupid question, but you are removing the (3) from the end of the mission file yeah?
Edit: Actually, yes it must be the wrong folder because with an empty mission.sqm you shouldn't even be able to connect to the server.
Did you try moving around, or did you just log in and scroll wheel? Options in the fn_selfActions.sqf tend not to show until you've moved slightly, even 1 metre.
Strange that it's running ok with nothing in the mission.sqm. I don't know what server host you are using, usually they state what...
Yeah, that all looks fine I think (been up all night so my eyes may be playing tricks on me). Is it just not showing the option? Or is it failing when you try to use it?
One thing I just noticed, you're using a rather outdated version of the actual player_selfbloodbag.sqf, that file doesn't...
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.