Because you're not supposed to get there to see that there's nothing going on at all on the surface, 
HIP 22460 Permit Lock Initiated
- Thread starter Paul_Crowther
- Start date
Or be able to affect (shoot/exlode/kill) anything that might have been there...Because you're not supposed to get there to see that there's nothing going on at all on the surface,
Someone got there in a SRV launched from some other moon, apparently there was nothing going on.
Yes, that was on the previous page in this thread...
Sorry!
Instancing is a mess tonight....well alot worse than usual and thats saying something, not to mention chat keeps bugging out, cant even direct message a freind i know who is online as hes typing in system, cant type in system as it goes to a :Chat whatever that is
Last edited:
Chat has been messed up fro a few days. I wonder if FDev slipped some updates into the mix recently, under the radar?
And finding a spot to park a fleet carrier near HIP 22460, within the jump range of my AX ship, is a "fun" exercise...almost takes longer than the 15 minute jump sequence...
Speaking of a mess, I got an email for combat logging this morning I mean I fought back gankers all night and those that did enough damage (usually groups of 3 or more as I am max 5 grade hull) I got away from, except one time where two cutters layered pack hounds on me, I was almost at jump charge I still had20%+ shield and boom game crashed to desktop and now I am a combat logger @sallymorganmoore ? wouldn't mind logged back in instantly and was shot at again and escaped lol does this mean I now have a flagged account? think this is the ticket code Y4MR48-8DWOV
I mean I fought back gankers all night and those that did enough damage (usually groups of 3 or more as I am max 5 grade hull) I got away from, except one time where two cutters layered pack hounds on me, I was almost at jump charge I still had20%+ shield and boom game crashed to desktop and now I am a combat logger @sallymorganmoore ? wouldn't mind logged back in instantly and was shot at again and escaped lol does this mean I now have a flagged account? think this is the ticket code Y4MR48-8DWOV
Almost sounds like they are "Swatting" you. Since they could not have their way with you in-game, they're trying it with you IRL. Typical ganker behaviour.Speaking of a mess, I got an email for combat logging this morning
I mean I couldnt do anything due to having anti xeno weapons but combat log? never especially howmuch i earned from this cg what would be the point lol
i thought everyone says typical "ganker" behavior is fighting unarmed ships or newbies who are flying around not expecting to fight fully engineered ships. This guy seems like he was holding his own and is engineered.
So, typical normal pvp behavior. Ganker is a term meant for players setup for pvp combat killing players who obviously aren't.
(edit, not that the hypothetical irl swatting is typical anything. Just that there was no "ganking" going on here)
Well you see i wasnt setup for pvp...but the sheer hull etc for xeno is how i survived lol
additionally killing pilots who are anti-xeno is the only way to even attempt to push a pro-xeno agenda. So it's not like they're trolling some space trucker CG where there's an option to oppose it by trucking in something else and instead just shooting up space truckers. if you're gonna xeno in open, then you should be prepared not just for xeno opposition but also human opposition because that's how you limit the objectives of anti-xeno activity. As impotent as that option may be.
Oh yes definitly I welcome the people who want to try kill me (or kill me) im more concerned with being flagged as a Clogger when the game crashed due to a very known pack hound graphical overload bug lol
If the client crashed there should be an entry in the windows event viewer for the game executable. You can show that as proof that the client crashed. That shouldn’t be there if you closed the executable yourself or disabled the network (ie. legit combat logged).
Last edited:
There you go. Reply to the email accusing you of combat logging showing them that and tell them to stop harassing you and to fix their game.
since the launcher stays open, you'd think it would handle reporting hangs,expected/unexpected self imposed closes or term signals from windows ...and the client itself can tell on you if network connections stop responding (if it were coded to do so). Might still be something spoofable but probably mitigate the vast majority of false positives.
Of course. Much easier to "tell a story" than to make a movie about it.
It does monitor, that's how it pops up the crash reporter. If Davanix filled out the report and sent it there should be no question of innocence...