[TERA PC & Console] En Masse is closing, but TERA lives on! We will continue to support TERA PC (NA) and TERA Console until service is transferred. Stay tuned for more information.
[TERA Console] The Grotto of Lost Souls update (v85) is now live! Read the patch notes here: https://bit.ly/TERACon_v85
[TERA PC] The 64-bit update (v97) is now live. Check out all the changes delivered on August 11 here: https://bit.ly/tera64_patchnotes
[TERA PC & CONSOLE] Summerfest Part 2: The Beach Bash is on from August 11 until September 1! Participate in event activities to earn tokens redeemable for costumes, consumables, mounts, and more! Details: https://bit.ly/tera_sf20
XIGNCODE DISCUSSION!
This discussion has been closed.
Comments
It's not a coincidence, but it's actually an unrelated (but equally stupid/frustrating) reason. The equivalent patch in K-TERA had the same performance bug with dungeons, and it was patched in a later K-TERA patch. As often happens, when they gave us this build, they gave us the same bug without backporting the fix. Which is frustrating as hell, but as it turns out, is for a different reason.
That file date is when it installed itself, so whatever game put it there, it happened a little over a year ago (assuming that's US time format).
I've also noticed that TERA's implementation, for whatever reason, doesn't seem to put a file there. (But other games like BnS and Black Desert do.)
Hit the windows key + R to open the run window. Type 'regedit' without the quotes. The registry editor window will open. Be very careful in here.
On the left in this window, there'll be a few folders. Click where it says HKEY_LOCAL_MACHINE.
That'll open a new set of folders. In there, click where it says SYSTEM.
That'll open another set of folders. In there, click CurrentControlSet.
From there, click Services.
In this folder, you're going to scroll to the bottom until you find a file marked xhunter1. That is xigncode's, and it's how you'll know if it's on your PC or not. When I uninstalled BDO, I had to manually delete this because it would not remove itself upon uninstall.
For a quicker reference of the file directory: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\xhunter1
https://steamcommunity.com/app/582660/discussions/0/1290691308571849109/#c1290691308571902026
^ source for this info, did it myself a while back. If it doesn't appear, then it's as counterpoint said and this version will not make itself known even here in the registry files, which is troublesome and quite unusual. I'd try it now but I'm not home.
I think I found the game used xhunter1.sys before... Dragon Nest = = which i quitted so i didnt notice it.
I am obviously skeptical of these insinuations because of how widely tools like this are used and the major consequences if any of these "facts" came to light. But if the evidence is there, and you've already put it together anyway, let's have it.
They wont get Xing, as it directly conflicts with European general law.
The issue with that is, no one wants to start all over from scratch, that's just annoying as [filtered] and turns you off from a game.
All Korean based games that don't need to follow European law. Sure, they may update their terms to add in a bunch of garbage, but they don't have to follow any of it. You're just being ignorant and silly and pointing to stuff that you know can be ignored.
Why even give people hope and tell them to contact support? Do you think support is going to suddenly change the code to allow this cloud? Give it up already.
According to EME It's just there for fun.
They certainly have proven they can. PUBG is also made by BHS, supported by EME, uses XIGNCODE3, and is one of the featured games on GeForce Now (the very cloud service that's being referred to). Plus, by its very nature, that cloud service is going to host all sorts of other games that also have various kinds of anti-cheat software like this; they just probably weren't prepared for it being added to TERA. So... yes? It's certainly at least worth asking.
Vote with your feet they say ( and my wallet too)!
I totally understand the desire that BHS and EME would have for implementing some sort of anti-cheat system. The last two years has been pretty rough for NA TERA in relation to family of third party programs.
Here's the problem: Xigncode has been implemented by Nexon (Korea) and pmang (Japan) in their TERA builds for a couple of years now. In that time:
- Xigncode failed to stop the usage of DPS meters. Literally, if you have a KTERA account, you could start up the most popular DPS meter for TERA and it will run perfectly fine. [1]
[1] As an educational side story, DPS meters are actually allowed under the ToS for KTERA. This happened after Nexon and BHS said that they were going to ban players that were using them, which resulted in a nasty backlash of the "lots of players actually stopped playing" kind. The ToS was subsequently re-written to allow DPS meters (and third party softwares, as long as the way it was used wasn't considered cheating).
- As has been mentioned in this thread, Xigncode is stupidly easy to bypass. Said DPS meter is actually a good example here.
But for others, Google is your friend here. And that's assuming that the game actually installed Xigncode onto your machine in the first place. There are comments by a few people that TERA never actually installed Xigncode on the machine it was running on (though that may be down to the borked patch process that happened).
- Xigncode never stopped the cheating enabled by the exploits that we have seen over the last two years on NA. How do we know this? They have been used on KTERA and action against cheaters was only taken after the community managed to prove that cheating was occurring.
One such example was the Valkyrie Dreamslash exploit. This appears to have been considered by BHS and Nexon a problem that didn't exist on KTERA until the Battleground leaderboards were re-introduced, where a Valkyrie that was known to be pretty bad at the game was sitting at the top of the PvP leaderboards for BGs. It was only at that point where it was proven to be an issue in KTERA when they actually started to code in proper fixes for it