chernaruski

Because ui_f_data folder is considered a3\ui_f\data , its just the way PBO's are configured. Read about $PREFIX$ to understand more. Engine considers pbos: ui_f_data.pbo = a3\ui_f\data ui_f.pbo = a3\ui_f So when Biki says to use a3\ui_f\data\logos... it's the correct path, it's you who is looking for logos in the wrong pbo file.

What do you mean "so that it updates to the latest version" , you have outdated exile mission ? So how did you put ravage modules in, in a first place? Also , the mission.sqm you've posted is just small part of the proper mission file, are you using proper mission file ?

@Karel Delmoitie try changing these to : mode = 2;  jip = 1;

He wants to create a server with a dedicated PvP zones throughout the map, while the rest of it is PvE (do damage player vs player). I tried finding "out of the box" solutions and at the end used Infistar feature that allows that. @JerryAtricks this will require overwriting exile files that are changing the way the damage delivered to players. eXile-PvEzones is just an addition on top that only alerts player when they enter the area, but not really changing anything damage related. It literally says it in the description: Now infistar had some changes done into their admin server tool, so you better make sure on their Discord that the paid version still have it. This is how it looks in infistart config, you just enter the area params and thats it: Yes its paid service/tool, but if you have no other alternatives and you want to save yourself the time, its worth it.

WIP: https://trello.com/b/SQbMmUkx/chr-dev-road-map-external WIP screenshots:

https://github.com/Ghostrider-DbD-/blckeagles-revisited-RC

It would be nice to have it for the weekend beach sunbathing. @Chairborne fantastic job man!

config.cpp in your mission.pbo

Check if its in your config.cpp, at the bottom where all XM8 Rsc things go. Maybe it was added there. Or at class CfgXM8 > extraApps

Update: Due to authors request. Link has been removed.

Yes send me the PBO, I have no idea what custom version of DMS you using, so it's hard for me to know.

You are not paying attention, that's exactly what I meant in the second case. Look at the objects code, its not the same. Drop me your DMS setup archive, so I can look on how the objects spawned, cause they are different and true in your case may have a different purpose. Yours have one param inside the brackets []: ["Land_Cargo_Tower_V1_No3_F",[2487.58,22426,0.287491],59.0909,[[0.857983,0.513677,0],[0,0,1]],true], The one I talked about have two: ["Land_Device_disassembled_F",[15140.764648,13606.168945,1.780041],[[0,0.999298,0.0374736],[0.0945738,-0.0373056,0.994819]],[true,false]]

I'm pretty sure, these are vanilla mission params. You set via mission start date and then the game engine calculates it. If I understood you correctly, by what you mean...

Is it possible you are editing the wrong mission (static, dynamic, special, etc) or the objects are pre-spawned on server start / spawned via different file? Also, I've seen different objects spawn methods. DMS have edited versions circulating around, recheck that these code lines match yours. Same { } for each_objects , same private_objects. If it's different, a different approach may be required.

You are welcome. What the hell is "styled text", how code can be styled? In what software you do your edits? Glad you go it working.

https://github.com/secondcoming/a3_exile_occupation

Hm... Try removing the / before the sound's path, for moaning sounds only at the moment, and see if it changed: class ryanzombiesmoan1 { name = "Zombie Moan 1"; sound[] = {"sounds\moaning1.ogg",0.6,"0.925 + random 0.15"}; titles[] = {}; }; Plus moving cfgSounds into description.ext directly without using #include maybe. Move the sounds.sfq up in the init file maybe. I'm shooting all directions here & running out of ideas. Make sure you have all the sound files in the respective folders with correct names. You can do direct comparison what worked for me and find the differences to make it work for you. Here are files I used way back

Why do you have $PREFIX$ file inside your mission pbo ? From what I know, $PREFIX$ may change your "root folder path" , so basically you changing the whole file path structure. Try removing it, if its there for no reason. Your current file rewires the root folder name to "Exile.Altis", maybe that's the reason. 1) When .hpp files included on binarization (pbo-ed), they use this file to structure the whole thing. 2) The same goes for Z&D sound arrays. Probably it breaks these paths set "mpmissions\__cur_mp.cup_chernarus_A3\Custom\zombie\Aggressive\..." and makes it "Exile.Altis\_cur_mp.cup_chernarus_A3\Custom\zombie\Aggressive\.." or something like that.

Typo. Missing brackets. Thanks. Should be ok, I was running heavily modified Exilemod back then. CfgSounds looks fine, if sound files are in their correct folder, it should work from the start. This looks very wrong. It looks like the game is trying to read the ryanzombiesmoan1 sound file from cfgSounds folder ? very strange it's like your description.ext have some code errors & it stops loading. Can you send me your whole mission.pbo & full RPT file ? (to PM if you don't want it to be public)

Hey. Yes, it still should work. Try following the instructions to the letter. Re-check you have correctly structured cfgSounds or have no class duplicates somewhere. Without logs, your configs, and setup, I can't direct you anywhere else but pointing back to the instructions.

Don't worry about it. You actually generating and sharing knowledge and solutions, which may help any future beginners that may encounter the very same problem.

Hmmm, interesting. I definitely never experienced this. Tho, I only used CUP's Weapons/Gear. Hard to tell, man. I assume you have a heavily modified exile mod, have you edited anything related to "pickup" action or some code related to the number of magazines on "pickup"/looted? Keep monitoring, try to find the exact scenario that reproduces this bug (not randomly caught, but reproduce exactly when & where you want it). Try to rebuild the exact steps & pay attention to the weapons/ammo/backpacks (mods) used. I also wouldn't scratch out an option of some gear mod that causes this (TRYK ?).

Yep. It's = "true". How bad is it for you? It happens often?

mmm, I never had this or never actually noticed (because it happens on a very rare occasions? )