i think we are all aware, that CCP is monitoring all known botting sites and forums and see how they adapt to the changes they make.
logically this applies to this forum as well.
As I have seen some people post screenshots whithout censoring their char name, time and place, i advise everyone to be careful when uploading screenshots to botting forums of your client.
over and out
Carefully handle information on botting related sites/forums
- VanGoghGaming
- Site Admin
- Posts: 3096
- Joined: Mon Jan 07, 2008 4:25 am
Re: Carefully handle information on botting related sites/fo
Well tbh I doubt CCP is investing any resources into such matters. Not to mention that the registered version sections of the forum are private and cannot be accessed without a paying account, however that is hardly an obstacle for a determined bot-hater. So this doesn't mean that an ill-intended, already registered user can't copy this information and post it somewhere else, so overall Peztos has posted a sound advice for everyone to consider!
VanGogh - Power-Gamer at Large!
Power-Gamers RPG Vault - So eager to play, so reluctant to admit it...
TinyMiner - EVE Online Mining Bot - The EVE Bot Macro Miner of choice, your own ISK Printing Machine!
Power-Gamers RPG Vault - So eager to play, so reluctant to admit it...
TinyMiner - EVE Online Mining Bot - The EVE Bot Macro Miner of choice, your own ISK Printing Machine!
Re: Carefully handle information on botting related sites/fo
LOL, time to fake the screen shots... I can see it now, "Hey guys, we need to ban this Mittani guy as he keeps posting in TM with some rediculous screenshots of him in a retriever".
I fact, if someone has some good video editing software we can get a youtube clip of him doing it real time as well. Anyone up for that challenge?
I fact, if someone has some good video editing software we can get a youtube clip of him doing it real time as well. Anyone up for that challenge?
Re: Carefully handle information on botting related sites/fo
With paintbrush you can write any name there, so you can blame a developer