Skip to main content

Forced Tedium - Raids 166-170 - Level 24

Need Funds

Raid 166 - Shoreline Stash Run (successful)

Time In Raid: 22 minutes, 42 seconds
Exp: 769

Raid 167 - Shoreline Stash Run (failed)

Stupid sniper scav killed me through a tree with a single shot Lps gzh that registered as two shots. 

Time In Raid: 11 minutes, 8 seconds
Exp: 124
Shots: 9, Hits: 0.  
Killed By: Vasya Borov

Raid 168 - Shoreline Stash Run (successful)

Time In Raid: 36 minutes, 16 seconds
Exp: 1050
Shots: 9, Hits: 2, Accuracy: 0.22, Body: 147
Kills: Matvey Pogon (sniper).  Godspeed Matvey

Raid 169 - Shoreline High Risk Loot Run (successful)

With the new flea market fees, these stash runs are not as profitable as they used to be.  I usually do a stash run with just a pistol to keep losses down in the event of failure, but despite hitting a lot of stashes and filling my bag, I'm still strapped for cash.  I evaluated the keys in my collection and all my best keys are on Shoreline. So now instead of hitting stashes, I'm going to try and move faster and hit safes and keyed rooms.  Has the potential to be more exciting, quicker, maybe bag me a Punisher 4 kill, or, if none of those things, bring in some cash.

I was in the cottage when I found, once again, the Emelya brand croutons. This is a bad sign. Every time I pick up these croutons, I die. They are cursed.  But Jaeger needs them, so I took them.  Seconds later, I heard footsteps outside. Not close, but worrying. I got quiet. And then the game disconnected.  So awesome.  I reconnected and discovered I was still alive. Listened, but no sound of movement. Finished looting and headed out. No sign of anyone else. Extracted. Weird.

Time In Raid: 24 minutes, 10 seconds
Exp: 1055
Kills: Fyodor Krokodil (sniper)

Raid 170 - Marking Tanks on Reserve

Still trying to level up Peacekeeper to Level 3. He wants me to mark a bunch of vehicles. This quest is probably impossible because I need the RB-ST key to complete it, and it's not for sale on the flea. So the only way I can complete it is to show up to RB-ST late and hope that someone has already unlocked it. But that's ok, I have other unachievable quests for Ragman and Therapist here (because their keys are likewise not on the flea right now). And, lastly, I need to kill raiders down below, which can be fun if they actually spawn.

I started identifying and marking vehicles. There was a bunch of shooting near the the docks - I think Gluhar and his guards are up. I managed to mark the vehicle on the hillock without bringing their hellfire down on me.  I circled round and was approaching the Knight buildings when my game disconnected.  That's two raids in a row - on different days and after restarts - need to investigate.

When I managed to reconnect, I discovered that both my arms were injured and one was broken. I ran, and threw myself into one of the Knight buildings, as a scav started firing on me. Patched myself up, leaned out and shot him in the chest with the Ash-12, but he didn't sit down. Damnit.  He fired back, but I was already behind cover. He disappeared into some bushes, I couldn't get a bead on him. Another scav came up to investigate and I dispatched him.  Ok - I can't hang around here making noise, need to move.

Ran up the back side of the garages and then hooked into them. RB-ST is locked. Damn.  Returned north through the garages and marked the tank there.  I think that's all the tanks, right? My plan was to go to White Bishop, see if the doors for Therapist were unlocked and if so pick up her things. And then go to the bunker to look for raiders and loot.

BUDDA BUDDA BUDDA BUDDA. BAM. Weapon fire and Gluhar's screaming very close by. Offline I like fighting Gluhar and his guards, but you need to manage their approaches and where I am right now is the absolute worst place, as at least one of them is likely above me. I aimed down sight and stepped out the door - a guard - I fired, landing a good shot. He didn't fire back - he's throwing a grenade, I ran to the other side of the garage, the grenade exploding and hurting my arm. Move! Move! Move!

Back south through the garages towards RB-ST again. Peeked the parking area again - no sign of that guard or any others - he's probably following behind me right now. Should I try fighting him here? I don't like it. I pushed across, took cover and waited. Nothing. Waited a bit more. Hmm. Then I continued away and stepped into the King garages. Players have been here. Crossed the King building. Ran across to White Bishop - someone moving in the bushes - shit. Pushed to cover in White Bishop and set up.

I'd prefer to go down this hallway, but the windows are exposed to the bushes - that's not safe. I stayed put, listening for Mr. Bushes. He moved, but just a step or two. I should push him. But suddenly there were footsteps, seemingly inside the building. Upstairs? Downstairs? I peeked the other hall - definitely not on this level. Turned on my flashlight. 

And then something very strange happened. A loud noise played - sounding like a giant door creaking open - along with clank clank clank, a bit like the loading sound of the AGL, very loud and close. And then two quick blasts of a shotgun and I was dead. Never saw my attacker because I was trying to locate the source of the sounds.

Time In Raid: 21 minutes, 48 seconds
Exp: 255
Kills; Zhenya Opasnyy (AI Scav).  Godspeed Zhenya
Shots: 8, Hits: 4, Accuracy: 0.38 , Body:368, Armor:14
Killed By: Nayk Piterskiy (TagillaTV player scav).  GG TagillaTV 

Mistakes

  • I don't understand what that loud sound was.  Maybe an ad in some browser window? Though that seems quite unlikely.  
  • Possibly TagillaTV  abused VOIP to play a sound to cover his advancing footsteps?  Maybe, but shouldn't that sound be placeable - emanating from him?  Ironically, the one other time I've had someone abuse VOIP with sounds was also on Reserve. If you were abusing audio, TagillaTV, then I retract the friendly GG I proffered before.
  • Could the sound have just been a bug in EFT? I did have a disconnect earlier in the same raid. 
  • There was one other tank I forgot to mark underneath the dome, in addition to the RB-ST one.
  • Should I have pushed the combat with the guard once I repositioned? Not sure - I had lost contact with him, and I waited after the second repositioning.
  • Shouldn't have let my attention stray from the danger outside that doorframe. 
  • staying in one place. I make this mistake a lot. Though, if I had heard those footsteps after entering the building I might have been braver about moving - but once I heard those, plus an enemy outside, for which none of whom I had exact placement - it encouraged caution. But maybe wrongly. 

Successes

  • marked most of the tanks

Labels:

Comments

Post a Comment

Popular posts from this blog

Field of Fire of Emplaced Weapons at Lighthouse USEC Base, for BEARS

On the new Lighthouse map, the USEC rogues are very aggressive against BEARS and will sight on you out to 300 meters or more, and will fire on you far quicker than they will on a USEC PMC.  The fixed guns are particularly dangerous as they can kill you with a single hit when you might not even realize you are close to the base. I made a map with some fields of fire noted on it. There are two mounted machine guns on building 1 , two mounted machine guns and a grenade launcher on building 2 , and a single machine gun on building 3 .  Plus there is a mounted machine gun and grenade launcher on the southwest corner of the base (lower right on this map).  I have noted the general field of fire of each of these weapons on the map. Obviously, there is a lot of cover, so just because you are standing in a red zone on this map doesn't necessarily mean you can be seen and hit. BUT, if there is any sort of line of sight (including through trees, bushes, walls and vehicles) and you are BEAR, t
Post a Comment
Read more

Counting Cheaters - Part 4

Methodology Because of this blog, I have a record of the name of everyone who kills me, as well as a mostly complete record of the name of everyone I manage to kill.  Every two months this wipe (12.12) I look up all those names in the in-game chat tool.  The presumption being that if a name is no longer in the chat tool then either that person changed their name, or they were banned for cheating.   It is not a perfect methodology nor do I have a lot of data, but it's far better than just going by feel, which is what most people do. The arguments about cheating on Reddit are mostly silly as people just try to generalize anecdotal experiences.  My Anecdotal Experience Since I broached the topic, here is my own anecdotal experience. Before I started doing this I didn't feel like I had encountered many cheaters in Wipe 12.12.  Just a couple.   But since I've started tracking, my view has become more jaundiced and now I have more suspicions. BUT, overall this wipe, I feel like I
Post a Comment
Read more

On "The Video"

 No doubt, anyone following Tarkov has seen the video from Goat:  https://www.youtube.com/watch?v=p5LfGcDB7Ek If you've read my blog before, you know I've tried tracking cheaters in the past by checking all my kills and killers in the in-game chat tool over time. I made several posts, the last of which was this one:  https://itarkovpoorly.blogspot.com/2022/06/counting-cheater-part-4.html My take on the video?  The reason it's called "The wiggle that killed tarkov" is because if cheaters are signaling each other via wiggling, it means there is a CULTURE of cheating and cheaters. And that's the shocking thing. It's not just "some people cheat", it's that there is a whole CULTURE of people cheating, with their own set of spoken/unspoken rules, behaviors, norms and manners. And if you've got a whole culture around something, then it's likely widespread and endemic. And disappointing.  Someone made the remark on Reddit that watching the vi
Post a Comment
Read more