Without Hans, there is no reason to ever use my Jawbreaker again! It was a medium, they made it a heavy to keep the Energy the same at 10. Hans could double the Cheetah to 10 KPH from 5 KPH. Using Co-Driver who gives 5 KPH is not correct co-driver for Jawbreaker Caucasus Vehicle. Ruined Jawbreaker/Hans combination. You are missed Hans.
Stone Deaf, my Fused Trucker shall never ride the Wasteland again without you buddy, you are sorely missed.
I unlocked all new Co-Drivers with 506 remaining Intel. 2 days I will be at the 8,000 Intel limit.
I use R2D2 the most, he sucks compared to Stone Deaf, but he tries hard.
PS You use Phobos for Jawbreaker Caucasus but there is no energy remaining for a Cloak because the Jawbreaker fails to have 11 Energy! So, most of Phobosâ skill is wasted except the 5 KPH!
PPS You are forced to use Yuki for Tonnage and lose 5 KPH!
I love how on reddit, in the game, and on the discord people are talking about how they love hte new co-driver system and are thankful for the MJ to Grizzly nerf/buff.
Everything I said was true, not whining. I miss Hans, my Raid Vehicle is ruined.
Stone Deaf, you get the bonus to Turrets no matter where you are, enemy base, ramming an enemy across the map from your Turrets or maybe right near them so the Bots target you and not your Turrets. Also, paid good resources for a very specific perk to make my Trucker faster, only Stone Deaf did that, so I miss him more than Hans. But I adapt and overcome. Lose some Durability on my Raid Ride and just use Yuki. Use R2D2 and stay by my Turrets or do not, stupid bonus.
Then, I told how I had enough Intel to unlock all co-drivers which is a compliment.
Now I have max Intel by tonight another compliment.
I do not think I was whining, just telling the facts as I see them so far.
I, personally, never said the new co-drivers system sucks. I said that re-applying co-drivers every time sucks. And expressed my concern about intel for all resources spend on co-drivers. In a form of question
First one is the truth because you canât just choose one co-driver and theyâll be with you on each vehicle. You have to save it manually for each build and apply each battle anew if you havenât. This one is not good, compared to the previous one.
Second one is an opinion, which may or may not be truth.
But most importantly, plebbit and cuckscord are known hives of snowflakes. Itâs not a good example of a reasonal behavior. No form of the criticism are acceptable there because local brownnosers will report and downvote your comment if they donât like it. And they donât like criticism of their favorite drug because âmUh PoSiViTiTyâ.
People can agree or disagree with me or anyone they want. But calling someone âa known trollâ because you personally donât like their opition⌠yeah, I think I know whoâs the real passive-agressive troll here. Reported and henceforth ignored.
You sure Phobos is better than Billie for Caucasus? Both get 25% dmg boost, but Billie getâs spread reduction and rotation speed, which Caucasus badly needs.
New codrivers are so much better. I think some people just hate adapting.
Canât wait to unlock the last three! Surprised at how quickly intel accumulates, so I should have them all soon.
One thing abour you is that brown something on your nose but another thing is lie blatantly.
Active co-driver doesnât stay when you swap to other build. And it doesnât return when you swap back on the first build. One have to save the build in order to save the applied co-driver as well. Without saving the co-driver with the build co-drivers will not be active.
So you do need to re-apply the driver if you create a new build, in order to have the former active. In other case, youâll be having the needed driver until you change your build to other. Having a co-driver active for both account and build saved was much better.
See theyâre all kind of flat to me so I find them really boring replacements. With the old ones they all had at least one secondary skillset that let you use them a little differently if you didnât like their main skills. Thereâs a lot that I donât like with the new system though and itâs really not about not liking to adapt.
What are you going on about? Before the update, co-drivers were also saved to the build, in the same way. And just like before, when you scrap a blueprint and start over, you still have your last co-driver active.
Maybe you are confused because the update wiped out all our previously saved co-drivers, so now when you load up any old blueprint, there is no co-driver assigned?
I did, and it makes no sense. There was no âaccount co-driverâ before the update. How would that even work with saved co-drivers? The whole point is that a new driver loads with the new blueprint you select.
