Except, there clearly are differences, but you just dismiss other people because of some highsec v anti-everything else position you have.
One of my Alliance mates was baiting our current war targets in their home system. He was in a safe spot, hoping they would see what he is in on d-scan and then undock in something he could fight against. No combat probes on d-scan at any point:
Before he even finished a single cycle of his armor reps, he was dead. In a safe spot, no combat probes and they warped in on him at range, insta-pointed him and killed him before a single rep cycle completed.
Thatās not behaviour seen anywhere else at any time.
So maybe people arenāt talking ā ā ā ā Nevyn. Maybe itās just that you lack any ability to consider they might be telling the truth because you have a huge bias.
1 Like
It is behaviour we saw months ago in highsec. You clearly havent been paying attention to drifters.
Also you clearly werenāt paying attention to what I wrote as I was talking about stats, not AI behaviour, even if that is known behaviour.
1 Like
Enough hurf blurf. Show me a single kill at a safe spot in highsec months ago. Prove it.
Prove that was a safe spot kill, zkill lists it as at celestial.
See the issue?
1 Like
if it says 14AU away from celestial, I guess itās a safe.
But we digress.
Null Sec should be more dangerous not less. Its time for NS to man up and accept the fact that they have had it beyond easy for far to long. High rewards should equate to high risks. NS is always screaming about content content, well CCP just might have hit the nail on the head. If you can not take the heat to bad, the party is over and we hope CCP continues to Provide valuable content to such placid regions of EVE.
2 Likes
There is no issue. It was a safe.
However, your response is the typical hypocrit answer. You are happy enough to call out others as basically liars unless they prove what they say, but when asked to do the same thing, suddenly, itās diversion.
Other people arenāt lying by default, just because they donāt play in highsec.
4 Likes
As far as the NS alliances losing their ever loving minds and threatening to burn down high sec and perform a trade embargo to starve high sec out to threaten CCP, I say bring it on. Since we already have high sec NPC mining corporations mining ores, why not null sec mining corporations doing the same as well taking over unmanned or drifter destroyed moon goo facilities. CCP is in the business of making money, donāt threaten what you can not enforce. And I predict for each one of these special case null sec care bears that rage quits EVE that three to five new players will join. You wanted content, CCP gave it to you, you wanted more movement of your products thus justifying your ganking fleets well now you can spend your time defending your holdings, your reputation and selling your products to afk toons not used to playing EVE in such a long time. You wanted change, dude you got what you wanted. Now man up or quit so we can forget your candy asses existed. Thank you CCP.
2 Likes
Is that based on anything at all?
1 Like
Sure. I never said it wasnāt a safe. you should try injecting reading skills.
The point I was making that zkill lists it as a celestial. The times I was in a fleet where drifters followed people that I personally witnessed no ships were lost, because we were flying anti drifter doctrines, soā¦
That leaves random player KMs. Who you canāt prove were at safes.
The bit I ACTUALLY was calling out was claims of drifters having the range of the entire grid, and earlier claims here of drifters being invulnerable etc. There are clear stats on the Npcs that donāt show that sort of range. So yeah, those bits Iām calling out as incorrect.
1 Like
um:
ok, sure.
Still lots more diversion, but total willingness to call out others.
I donāt even really expect you to try to prove it. It was just about the double standard. One standard for you. Different standard for everyone else.
Andā¦ thank you for not reading yet again and showing you arenāt even worth the time of reading in this thread anymore.
You are seizing on single words and part sentances to twist as you want.
1 Like
Iām not. The whole sentence is there where you asked for proof it was a safe, when the proof is already in the killmail. Not single words, not part sentences. The whole thing and every word in the sentence.
If after seeing the killmail you still want more proof, because you donāt believe it, then what is it other than saying you donāt believe it was a safe.
But, keep diverting. Iām sure youāll keep calling out others as a hypocrit, even though you arenāt prepared to back up your own claims.
3 Likes
looking at the km all I see is that the location was the star.
Also the whole point was that posting a km doesnāt prove things and if I went back 500 pages of drifter kills and found one, it wouldnāt prove anything anyway.
1 Like
drifter stats
Drifter Battleship(34495) group=Drifter Battleship(1310) category=Entity(11)
targetAttack(10)[is_offensive]
range(54)=150000.0
falloff(158)=150000.0
tracking(160)=0.06
duration(51)=5000.0
warpScrambleForEntity(563)[is_offensive]
range(103)=500000.0
duration(505)=5000.0
modifyTargetSpeed2(575)[is_offensive]
range(514)=500000.0
duration(513)=5000.0
entitySuperWeapon(6042)
duration(2009)=5000.0
entityEnergyNeutralizerFalloff(6691)[is_offensive]
range(98)=40000.0
duration(942)=10000.0
mass(4)=1.09E7
hp(9)=15000.0
charge(18)=0.0
speedFactor(20)=-10.0
maxVelocity(37)=3500.0
capacity(38)=120.0
rechargeRate(55)=1000000.0
damageMultiplier(64)=16.0
energyNeutralizerAmount(97)=60.0
warpScrambleStrength(105)=5.0
emDamage(114)=80.0
explosiveDamage(116)=80.0
kineticDamage(117)=80.0
thermalDamage(118)=80.0
volume(161)=109000.0
radius(162)=350.0
maxLockedTargets(192)=4.0
maxAttackTargets(193)=1.0
scanRadarStrength(208)=500.0
scanLadarStrength(209)=500.0
scanMagnetometricStrength(210)=500.0
scanGravimetricStrength(211)=500.0
propulsionGraphicID(217)=397.0
gfxTurretID(245)=34580.0
gfxBoosterID(246)=397.0
entityAttackRange(247)=122500.0
entityLootCountMin(250)=1.0
entitySecurityStatusKillBonus(252)=0.2
shieldCapacity(263)=5000.0
shieldCharge(264)=0.0
armorHP(265)=17000.0
armorEmDamageResonance(267)=1.0
armorExplosiveDamageResonance(268)=0.5
armorKineticDamageResonance(269)=0.5
armorThermalDamageResonance(270)=0.5
shieldEmDamageResonance(271)=0.51
shieldExplosiveDamageResonance(272)=0.51
shieldKineticDamageResonance(273)=0.51
shieldThermalDamageResonance(274)=0.8
entityFlyRange(416)=49000.0
entityEquipmentMin(456)=3.0
entityEquipmentMax(457)=6.0
entityReactionFactor(466)=0.6
entityAttackDelayMin(475)=1000.0
entityAttackDelayMax(476)=5000.0
shieldRechargeRate(479)=500000.0
capacitorCapacity(482)=7700.0
shieldUniformity(484)=1.0
entityWarpScrambleChance(504)=1.0
entityCruiseSpeed(508)=235.0
modifyTargetSpeedChance(512)=1.0
armorUniformity(524)=0.75
structureUniformity(525)=1.0
signatureRadius(552)=400.0
entitySecurityMaxGain(563)=5.0
scanResolution(564)=360.0
entityChaseMaxDelay(580)=5000.0
entityChaseMaxDelayChance(581)=0.25
entityChaseMaxDuration(582)=10000.0
entityChaseMaxDurationChance(583)=1.0
optimalSigRadius(620)=20.0
entityGroupRespawnChance(640)=1.0
entityChaseMaxDistance(665)=33000.0
entityBracketColour(798)=1.0
disallowAssistance(854)=1.0
energyNeutralizerEntityChance(931)=1.0
effectDeactivationDelay(1579)=5000.0
AI_ShouldUseTargetSwitching(1648)=1.0
AI_ShouldUseSecondaryTarget(1649)=1.0
AI_ShouldUseSignatureRadius(1650)=1.0
AI_ChanceToNotTargetSwitch(1651)=0.0
AI_ShouldUseEffectMultiplier(1652)=1.0
entityOverviewShipGroupId(1766)=26.0
damageDelayDuration(1839)=3000.0
entitySuperWeaponEmDamage(2010)=160000.0
entitySuperWeaponKineticDamage(2011)=160000.0
entitySuperWeaponThermalDamage(2012)=160000.0
entitySuperWeaponExplosiveDamage(2013)=160000.0
entitySuperWeaponMaxRange(2046)=250000.0
entitySuperWeaponFallOff(2047)=250000.0
entitySuperWeaponTrackingSpeed(2048)=0.132
entitySuperWeaponOptimalSignatureRadius(2049)=125.0
Drifter Battleship(34561) group=Drifter Battleship(1310) category=Entity(11)
targetAttack(10)[is_offensive]
range(54)=150000.0
falloff(158)=150000.0
tracking(160)=0.04
duration(51)=5000.0
warpScrambleForEntity(563)[is_offensive]
range(103)=500000.0
duration(505)=5000.0
modifyTargetSpeed2(575)[is_offensive]
range(514)=500000.0
duration(513)=5000.0
entitySuperWeapon(6042)
duration(2009)=5000.0
entityEnergyNeutralizerFalloff(6691)[is_offensive]
range(98)=40000.0
duration(942)=10000.0
mass(4)=1.09E7
hp(9)=15000.0
charge(18)=0.0
speedFactor(20)=-60.0
maxVelocity(37)=3500.0
capacity(38)=120.0
rechargeRate(55)=1000000.0
damageMultiplier(64)=40.0
energyNeutralizerAmount(97)=60.0
warpScrambleStrength(105)=5.0
emDamage(114)=80.0
explosiveDamage(116)=80.0
kineticDamage(117)=80.0
thermalDamage(118)=80.0
volume(161)=109000.0
radius(162)=350.0
maxLockedTargets(192)=4.0
maxAttackTargets(193)=1.0
scanRadarStrength(208)=500.0
scanLadarStrength(209)=500.0
scanMagnetometricStrength(210)=500.0
scanGravimetricStrength(211)=500.0
propulsionGraphicID(217)=397.0
gfxTurretID(245)=34580.0
gfxBoosterID(246)=397.0
entityAttackRange(247)=122500.0
entityLootCountMin(250)=1.0
entitySecurityStatusKillBonus(252)=0.2
shieldCapacity(263)=5000.0
shieldCharge(264)=0.0
armorHP(265)=17000.0
armorEmDamageResonance(267)=1.0
armorExplosiveDamageResonance(268)=0.5
armorKineticDamageResonance(269)=0.5
armorThermalDamageResonance(270)=0.5
shieldEmDamageResonance(271)=0.51
shieldExplosiveDamageResonance(272)=0.51
shieldKineticDamageResonance(273)=0.51
shieldThermalDamageResonance(274)=0.8
entityFlyRange(416)=49000.0
entityEquipmentMin(456)=3.0
entityEquipmentMax(457)=6.0
entityReactionFactor(466)=0.6
entityAttackDelayMin(475)=1000.0
entityAttackDelayMax(476)=5000.0
shieldRechargeRate(479)=500000.0
capacitorCapacity(482)=7700.0
shieldUniformity(484)=1.0
entityWarpScrambleChance(504)=1.0
entityCruiseSpeed(508)=235.0
modifyTargetSpeedChance(512)=1.0
armorUniformity(524)=0.75
structureUniformity(525)=1.0
signatureRadius(552)=400.0
entitySecurityMaxGain(563)=5.0
scanResolution(564)=360.0
entityChaseMaxDelay(580)=5000.0
entityChaseMaxDelayChance(581)=0.25
entityChaseMaxDuration(582)=10000.0
entityChaseMaxDurationChance(583)=1.0
optimalSigRadius(620)=40.0
entityGroupRespawnChance(640)=1.0
entityChaseMaxDistance(665)=33000.0
entityBracketColour(798)=1.0
disallowAssistance(854)=1.0
energyNeutralizerEntityChance(931)=1.0
effectDeactivationDelay(1579)=5000.0
AI_ShouldUseTargetSwitching(1648)=1.0
AI_ShouldUseSecondaryTarget(1649)=1.0
AI_ShouldUseSignatureRadius(1650)=1.0
AI_ChanceToNotTargetSwitch(1651)=0.0
AI_ShouldUseEffectMultiplier(1652)=1.0
entityOverviewShipGroupId(1766)=26.0
damageDelayDuration(1839)=3000.0
entitySuperWeaponEmDamage(2010)=187500.0
entitySuperWeaponKineticDamage(2011)=187500.0
entitySuperWeaponThermalDamage(2012)=187500.0
entitySuperWeaponExplosiveDamage(2013)=187500.0
entitySuperWeaponMaxRange(2046)=250000.0
entitySuperWeaponFallOff(2047)=250000.0
entitySuperWeaponTrackingSpeed(2048)=0.132
entitySuperWeaponOptimalSignatureRadius(2049)=125.0
Drifter Battleship(50093) group=Drifter Battleship(1310) category=Entity(11)
Iām missing the last one, I guess itās the one that does not have a superweapon.
I guess CCP copied it and just removed the superweapon from it.
Pretty sure itās just an AI tag that stops the superweapon from firing, the stats are actually there still.
The Arithmos is the one you are missing which is the tanky wh one. Which is not what null is facing.
1 Like
Try this representation then (the actual killmail from CCP that zkillboard then uses). THe x, y and z position are there. You can see plot this in system and see exactly where his safe was:
https://esi.evetech.net/latest/killmails/77614449/6191be572c968f86d00dc8a51a4fbe7cfb3b7ef1/?datasource=tranquility
There many people who have quit EVE because of the bully effect that some NS alliances have had on the entrance to EVEās new players, High Sec. Now that the new management of EVE has seen the population drop its easy to determine one of the main causes of the population drop is the sadistic harassment of the new players entry point into the game. This new NPC for NS is what I believe is just the beginning of CCPs attempts to give some special case narcissistic bloated Egos NS care bears content to leave the front door to the game alone long enough to regrow the membership. I for see more harsher moves by CCP to protect their real investment and look forward to some people learning that you should not piss on your own garden. This is a great game, but some either out of envy or malice want to destroy it and I believe that CCP has done the statistical analysis to prove this very point resulting in the current content we are now seeing in NS at this time. I look forward to egos to overcome common sense and the rebirth of EVE as special cases rage quit because they have been weighed, measured and found lacking. CCP is in the business of making money not stroking bloated toxic egos.
2 Likes
I hope they remove asset safety next. People might be motivated to defend in that case. Otherwise, thereās plenty of structure spam to clean up and if people donāt want their sov, others will take it. People will adjust.
3 Likes
And we have a map of all sigs in the system at the time? Note. Iām not doubting that this was a safe. My point is that actually proving it after the fact from months old random KMs is impossible.
Especially when itās just to satisfy you trying to call me a liar for saying weāve seen the behaviour you are talking about.
1 Like