agree but shit kids wud leave when their partner is shit |
Hence the faust
So I have to Faust it, ensure the gren's arent wiped in 2 shots from the AEC, then ensure my MG is setup with incendiary rounds. Even then the AEC can smoke and get out in time EASILY. Honestly you must fight trash people to think this is an acceptable counter.
A good player wont even get his AEC fausted since it has 50 sight range and can SELF SPOT. GL bro |
|
OKW is a fairly easy faction where cheesy-strats like blobbing is encouraged as they work. The larger the gametype (1v1, 2v2 and up), the more the cheese works. Their FRP, free meds, free reparistation, free AA, cheap units and cheese units like Obers are ultra bad game design.
My opinion, if you don't agree it's fine.
So just like USF |
This has got to be a joke... OH does NOT need 222 buff or changes to vehicle-play.
OH already has the right tools to fight early vehicles. Faust and HMG-42 vet 1 ability will absolutely wreck all allied light vehicles except for maybe Stuart. I agree, adjustments must be made to the AEC, but if you play your cards right with OH you WILL get the upper-hand...
EDIT: And i havent even begun to talk about Schrecks or PAK-40... OR TELLER MINES!!!
your obviously shit at this game to think that |
lel we beat them after you did on same map 2. |
OKW is fine, if not underpowered at the moment. With CalliOPes and bullshit AEC/cover arty they really struggle.
Once these are nerfed to shit then OKW will probably be fine. |
Not sure if you're talking about lastpass, or if you thought keepass2 was a web-based password management app buttttttttttt I'll try and ease your mind a little/enlighten you...
As long as the database in which your password(s) are stored on any given web server, even if that server is compromised, your passwords (in the environment of a properly managed database) will be secure. Part of this is your responsibility to make a strong password, no realistic amount of help is going to fix a weak password.
In simple terms this is what is going to happen: you give mywebsite.com your user name/password, they shouldn't need that information for anything other than authentication, therefore they will hash the password (preferably with some sort of salt), and store the hashed value of your password. When you authenticate in the future, they only compare the hash your browser sends them, to the hash they have stored - if they match, congrats you entered the same password and you're let in. Without going into the details of attacking something like this, suffice it to say that if your password is weak and the database is compromised, it will be trivial to crack your password. But if it strong, odds are your password is safe from anyone other than a state-backed actor.
Not to mention that it'll be exponentially more difficult to attack a properly hardened webserver than most people's local machines/home networks.
Now... I haven't done my research on lastpass because I don't use it but I'd be willing to bet that your passwords are safe there...
As for KeePass - all the passwords are only ever stored locally on your machine. You set up a master password and have the option of adding a key file and OS user account as additional layers of authentication to access your password database. You then get to set up your list of passwords, which KeePass will randomly generate for you if you'd like (yay copy/pasta) and never have to worry about remembering anything other than 1) your master password and 2) the location of your key file.
In order to compromise this an attacker would need full access to your local machine, they'd have to know where your key file is located, and they'd have to be logged in as you (well I guess that part is easy if your Windows/Linux/OS X password sucks). Anyways, the point being... the odds of this happening are incredibly low unless you derp up.
Edit: https://blog.lastpass.com/2010/07/lastpass-gets-green-light-from-security.html/
^ If lastpass is good enough for Steve Gibson, it's good enough for me. I'll stick with KeePass because I already have it set up, but there's some more reading material for those interested.
Agree with most you said apart from 'they only compare the hash your browser sends them' pretty sure your browser sends the password in normal format and the webserver hashes the submitted password and compares it to the store password. |
Thread: 22226 Jan 2016, 10:12 AM
You can do whatever you want with a 50fu 222, you'll just lose before you can field it.
ya tell me some more about 4v4 |
Thread: 22226 Jan 2016, 10:00 AM
Is this the same person? Not too long ago I thought you said a 222 buff would be too powerful, of course it might have been different ideas but still.
I still think 222 should be able to kite other light vehicles and be a scout skirmisher rather than trying to brute force them. Allow it to not chunk down light tank/vehicle HP, but the 222 can keep at range to remain safe and be a unit that is effective with good micro.
I only said that in regards to your buffs in relation to fuel costs. If the 222 was 50 fuel with your ideas, then that's great. |