Serveur 1038 pve cheater named "Thief" i need help

Please Funcom do something, because for the 5th time, the player named “Thief” killed one of my characters again while we are not in PVP! It’s impossible, he’s a cheater, he takes pleasure in ruining other people’s games. I took a screenshot of the connected players, it’s one of those, I play in K5.
Please do something.
My player name is Brunhilde.
Thanks in advance.

1 Like

you shouldn’t be name/shame any player, even if he is a cheater. Write a ticket instead.
Also, can you elaborate a bit? How exactly does he manage to kill you in PVE? Gas clouds?

*edit: 1038 is a PVE Conflict server, he can kill you between 18:00 and 22:00, I think.

2 Likes

Hi thanks, i have sent a message to report him, he has killed many time thralls, and not in pvp time, just today.
That s s a cheater i have evidences and screenshot

but how did he kill the thralls?

I dont know, i have a screen shot to prove it, it s not the first time

he killed a lot of thralls ,not in pvp time in this server

Today at 13h26.14

I’m no expert on how to unalive other Clan’s thralls, but there definitely are methods to kill thralls, even outside PVP hours. Which aren’t even cheating just griefing. Like luring mobs to them, or the new one is to lure a sacred hunt monster to them, which can’t be attacked by thralls even.

Thanks Raudl for your replay !

have some new info for you…the Thief wasn’t a player. That is a new NPC that can spawn with Purges. He spawns closer to your Treasure Room.
It seems somebody griefed you with a Purge near your base and the Thief NPC spawned and was attacked by your Thrall, but the Thrall got killed.

1 Like

What was happed is that someone killed your thralls using an exploit, probally the zath’s orb exploit that is the easest to do even. It show killed by a thief on log. Even before the new purge mob thief. There are another one that shows on log that your thrall was killed by spwaned effect. I not certainlly about this one but seen that are something related with the thrall position is they are blocking a player spwan point they die if the player logs on. But i just heard about it. I was victim of the both methods.

Someone is summoning a Purge near your Thralls.

Funcom isn’t going to do anything.

What you and other players need to do is Hide your Thralls behind walls and set their radius to 5m. Guard and Passive stance.

Whoever is doing this is purposely doing it. The only way to defend against it, is to outsmart the purge itself.

2 Likes

This one would be my first guess too, based on the name. I’m unfamiliar with server play, so I’m not sure how NPCs and players are marked on the event log, so didn’t want to speculate based on the screenshot.

For players it’s something like: Florida Man (Punchin’ Gators) Clan name in the parenthesis. Not sure on the clanless. For NPCs it’s pretty much what OP said.

1 Like

Well when I played ( before even the thief new purge thrall ) on officials I often saw “thief” killing thigns ( it can be any npc brought by someone else to them using various methods ( like spikes at the time) ) I’ve witnessed it , also to be known , there is a discrepancy with the radius of thralls and wildlife dealing damage around a player, and if you are at the “right” ( should I say the wrong or evil ) distance , then wildlife will deal damage to thralls , while thralls won’t deal any damage ( this can also mean that this can happen if you stay in your base while having build near a camp ( or even a kappa that one of your guardians took aggro from and that you unfortunately stand at the wrong/“right” distance )

by the way @cams si tu peux dire " hey " à Wolfyymann de la part de Kanza1 pour moi ca serait sympa :hear_no_evil: :see_no_evil: :speak_no_evil:

est ce que c’est arrivé au meme endroit ? et lorsque tu reste dans ta base ? car il est possible que ça soit ce que j’ai décris au dessus en anglais !

en tout cas sur un serveur pve-c je te conseille de garder tes thralls et animaux à l’interieur de ta base et pas à l’extérieur.

2 Likes

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.