Using Mods with Wasteland..

Using Mods with Wasteland..

« posted: May 13, 2017, 08:05 PM »
So, we want to use some mods with Wasteland which hasn't been a problem until I tried to add some of the side/players from the mod to for example blufor player joint list.

I am getting kicked with RemoteExec Restriction #0...What exactly do I need to edit to allow mod sides to be able to be used? I know its the BE filters but which one?

Re: Using Mods with Wasteland..

« Reply #1 posted: May 13, 2017, 11:00 PM »
Okay was able to get it up somewhat by editing my BE Filter createVehicle.txt. What I don't understand is if a side is in blufor, opfor and independent it should work regardless because AgentRev or whoever already added them to createVehicle.txt.

Example

Code: [Select]
5 "^[BOI]_[CG]_" // Comment this line if you need to allow guerilla units
BOI means Blufor,Opfor,Independent
CG means Civilian, Guerilla(s)

If a mod has a faction to Blufor side why would this still be restricted in Battleye? What would I need to add to this line to enable a mod's faction to BE? It doesn't make any sense.

What I did for example in using Operation:Trebuchet unit in Wasteland was add

Code: [Select]
5 "^[BOI]_[CG]_[OPTRE]_" // Comment this line if you need to allow guerilla units

This is not working so I am baffled with this as the unit/class I am trying to add is called OPTRE_UNSC_Army_Soldier_Demolitions_TRO

So if anybody can chime in with any help I would appreciate your help very, very much. This mod has some very cool uniforms and weapons..
  • Offline AgentRev
  • Developer
  • Veteran
  • ******
  • Posts: 2344

Re: Using Mods with Wasteland..

« Reply #2 posted: May 14, 2017, 08:55 AM »
Why are you looking at createVehicle.txt... it says RemoteExec Restriction, you should be looking at remoteexec.log to see whatever dumb kludge the mod makers have put together, and possibly undo it.

This is not working

We've already gone over this; you are not giving me any sort of useful information. I want to know WHAT is happening, give us some BE logs, RPT logs, error messages, anything. You need to provide more coverage.

Re: Using Mods with Wasteland..

« Reply #3 posted: May 14, 2017, 11:26 PM »
AgentRev,

Here is the BE RemoteExec.log of the Error#0

Code: [Select]
13.05.2017 11:03:22: WhatsUpDoc (73.55.38.191:2324) f86cd85913b229085e47d8dd75c63391 - #0 "say3d [B Alpha 2-1:1 (WhatsUpDoc) REMOTE,["OPTRE_Sounds_HUD_Visor",50]]"
13.05.2017 11:03:57: WhatsUpDoc (73.55.38.191:2324) f86cd85913b229085e47d8dd75c63391 - #0 "say3d [B Alpha 2-2:1 (WhatsUpDoc) REMOTE,["OPTRE_Sounds_HUD_Visor",50]]"
13.05.2017 11:35:57: WhatsUpDoc (73.55.38.191:2304) f86cd85913b229085e47d8dd75c63391 - #0 "say3d [B Alpha 2-1:1 (WhatsUpDoc) REMOTE,["OPTRE_Sounds_HUD_Visor",50]]"


What I did was add a Faction to blufor side. Then whenever I joined the server I chose that faction/unit which is from the mod Operation:Trebuchet. As soon as I choose the unit and press connect it starts to load them boom I get kicked with RemoteExec Restriction #0.

The RPTs shows:

Code: [Select]
"pvar_requestPlayerData: [3,B Alpha 1-6:1 (WhatsUpDoc) REMOTE,B Alpha 1-6:1 (WhatsUpDoc) REMOTE]"
down a little further on the RPT it shows:
 
Code: [Select]
"HandleDisconnect - [""WhatsUpDoc"",""76561198148406431""] - alive: true - local: true - isPlayer: false - group: B Alpha 1-6"

Sorry but I read in other posts that I should check the createVehicle.txt if I am getting RemoteExec Restriction #0 as it can also cause the same type of error. This happened before whenever I added the AdvancedSlingLoading and it was fixed by editing the createVehicle.txt per the Readme that came with AdvancedSlingLoading. It was the same exact kick error.

EDIT:

It wasn't createVehicle.txt I edited for AdvancedSlingLoading it was setVariable.txt that I edited. My mistake...
  • Offline AgentRev
  • Developer
  • Veteran
  • ******
  • Posts: 2344

Re: Using Mods with Wasteland..

« Reply #4 posted: May 16, 2017, 11:11 PM »
Ok so it seems OPTRE is sending raw commands thru remoteExec. I've seen this before, here is the solution: http://forums.a3wasteland.com/index.php?topic=2654.msg15780#msg15780

There might be more commands to whitelist, you'll have to come back with the remoteexec.log if you get more kicks.

Re: Using Mods with Wasteland..

« Reply #5 posted: May 17, 2017, 02:58 AM »
Okay thanks Rev I will test this after I fix what I missed on your 1.3c update.