Remote Exec #1

[CrazyCorky]

Not sure what is causing this but I have been kicked for this twice now on the TX01 server. It had happened on others at the time. Is there any known cause?

 

Then immediately kicked for RemoteExec #0 (just an update)

 

At the time of the first kick all I was doing was looting a trash pile.

[BioHazard050]

I got remoteexec 1 for looting ovens...twice. Never for trash cans.

[axeman]

Updating over the next patches. Safest way to deal with remote exec is to totally ban it. Also the spawn triggers are getting a make over once we're happy with the level of antagonists.

 

Way to spoiler hangender  :blink:  :angry:

[nedfox]

You don't need a patch Epoch to whitelist that specific remoteexec; why let us disconnect 4-5 times per session when the remote exec procedure is actually put in by the devs? whitelist your own code?

Or is that dangerous because it can be exploited?

[axeman]

To be honest this is more AWOLs area, though after chatting about it I understand that we are going with what is most secure..

Oh, and its an alpha with several developers adding content from different continents so testing is required. Am pretty sure we are OK with how to whitelist thanks though, you may have noticed this started happening half way through the latest patch.

This has been dealt with in the latest patch and new methods to be added for the next one.

[nedfox]

I know from a developers' perspective how code from different coders can harm the overall gameplay :)

The question I asked was basically if a quick fix (BEC whitelist) would improve testing (not being kicked is great) with the risk of introducing gamehacks.. If you settle for better code and no whitelisting I'm totally fine with it; it would be very nice to have some "work in progress" list for coming patches where it's stated those problems will be solved, so ppl won't post about it anymore.