Miannie83
-
Content count
184 -
Donations
0.00 EUR -
Joined
-
Last visited
-
[Release] Exile Occupation (Roaming AI) & More - updated 2019-01-23
Miannie83 replied to second_coming's topic in Add-ons
Reinstalled PBO 1.4 no change, after making edits and repacking the pbo, it no longer works. Its the only one i'm experiencing this issue with. **edit** problem is now rectified, reinstalled pbo manager again and downloaded a new pbo, can now edit the config and repack the pbo. All running as intended now. -
[Release] Exile Occupation (Roaming AI) & More - updated 2019-01-23
Miannie83 replied to second_coming's topic in Add-ons
I am also experiencing this issue. Infistar and DMS and capture points pbo's are working as intended. -
Good to see that you made it over here sheep. Many people will be grateful for your repack.
-
Just noted that in your picture, you have 7 ExecVM on lines 43 and 44 and again on 48. Combine those lines so there is only one and that will probably solve your issue.
-
"\n" means "new line" and should only be added to the start of a new line before you make it one single line of txt. The n in your kick does not need the \ placed before it.
-
You will find that he is posting his .txt asking if he added it correctly. Posting his log would achieve nothing.
-
You won't find your answer in the server RPT file. You need to look in your battleye folder in your server. You will see a file called script.log there will be a reason for a kick. Once you have the reason i suggest you head over to the battleye section of the forum and read the "how to" sticky post.
-
Below should work. I'm not sure as to why it wouldn't. I can see it in your script file so i'm not sure as to why it isn't, did you reload the scripts via a RCON tool or restart the server? Simple questions i know but i have been guilty of not reloading the filters and wondering why it doesn't work. !="ys;\n \n _type = typeOf player;\n if!(_type isEqualTo 'Exile_Unit_Player')then\n {\n if((currentWeapon player != '')||(player !"This is the exception i had to add when i installed it. I copied it from my script file. !="\n \n \n _type = typeOf player;\n if!(_type isEqualTo 'Exile_Unit_Player')then\n {\n if((currentWeapon player != '')||(player !"Maybe that might work.
-
Line 48, you really should at least read the stickied post at the top of this section, it will save you some head aches. Looking at the kick i suspect its the line that starts with 7 isplayer
-
!="_fnc_vectorRandomize\",\"RHS_fnc_cbalTimeToDistance\",\"RHS_fnc_isPlayer\",\"RHS_fnc_sight_bmp2\",\"RHS_fnc_sight_1pz32\",\"RHS_fnc_sight_"
-
I experienced this issue last night on my server, no idea why its happening. The kick is #0 14:32 Not sure on why its happening, i can't really see anything in logs apart from that.
-
This mod allows you to connect taru pods to the taru. And load quads/cargo into the back of the hemmt and other various vehicles. To check if its working, spawn in an exile_hemmt and and eile_quad_black, park the quad behind the truck, then get in the truck and on your scroll wheel menu you should see a green text option to load cargo into vehicle. If you don't get the scroll wheel menu then you have missed a step somewhere.
-
I would suggest reading the post stickied at the top of this sub section to understand how battleye filters work. in the meantime, you are getting kicked due to the part i have put in bold, italics and underscored. _publicMessage remoteExecCall ["ExileServer_system_network_dispatchIncomingMessage"," Once you understand how to do the filters they are quite simple, read the document. And you will discover that you need to add this to the end of line 26 of your filters !="ssionId, _messageName, _messageParameters];\n_publicMessage remoteExecCall [\"ExileServer_system_network_dispatchIncomingMessage\","
-
I think you missed what he is telling you. You are asking the server to include config.cpp twice. Once on line 5 and then a 2nd time on line 92. It is not needed on line 92 as you already have it on line 5, so delete the second one. You will find that your server .rpt will have a heap of item already defined errors,
