Profile of Mr.Smith

Note that, despite appearances, Stug TWP ability does NOT lock the turret of vehicles temporarily. Instead it completely disables the main gun of the affected unit for 15 seconds.

Free squads for USF MVGame

Free squads?
You mean the 8 (Lieutenant) + 8 (Captain) + 5 (Major) + 4 (Ambulance) popcap squads the USF gets?

I only talked about popcap cost.

inb4: yes; USF popcap abuse is actually fixable

From my experience, the Ostwind can suppress an enemy unit outside cover in 2-3 bursts, depending on whether you're moving or not.

Using the bulletin requires a decent amount of effort, as you need to ensure that your Ostwind is facing the enemy squad at all times. The downside here is that you cannot control the target of the MG. Thus, if you're facing a blob the MG might end up changing targets with each burst.

Luckily, if you're facing a blob, it means your Ostwind will get tons of kills.

10/10 would use again.

Combine with hull down for the lulz.

Yes. At least the versions that were available, and due to lack mostly against AI. And the 222 changes were not impressive, to phrase it carefully.

Just out of curiosity, how was your preservation like with the 222? The new 222, as well as most of the vehicles in the patch, actually require you to acquire veterancy before you can go for the deep dives.

The new 222 is no longer a vet0 suicide-rush vehicle. You invest in it, it gets veterancy, and it pays back. It also pays back a lot better than live-version 222.

The changes also mean that you don't have to dive-in every time for the 222 to do any damage. You can sit back, and kite. Then, use the improved mobility and keep your distance and keep kiting; while doing damage; while gaining vet. Ask anybody that has actually played WBP vs a human opponent, and they will tell you the same.

This requires a change in mentality.

PS: If the only testing you did was vs AI then, of course, the changes in 222's mobility make absolutely no difference. The AI is static either way.

The thing is, that to port the changes we didn't create the files using the mod tools. Instead, we took the files from the mod, and used whichever IDs were assigned by my mod tools.

The situation I dread is as follows.

- Say, concurrent with the WBP somebody started creating their mod.
- When I created the first new file for the mod (say, penal PTRS), the attribute editor gave that file ID 10000.
- At the same moment, when the other modder created the first file for their mod (say, rocket launcher), that file also got file ID 10000.

This is OK, as two mods are normally never designed to play well with each other.

However, what I fear will happen is that the overlap in IDs might make live-version upgrades that give PTRS to interfere with the mod and give rocket launchers in the mod version, instead.

I have already experienced something like this during a failed clone when a newly-created file (ghost retreat points) had the same pbgid as a pre-existing file (major's retreat antenna). This was the reason why retreat point functionality was bugged in WBP v1.3 (it's not because I touched Major retreat point; it's because something else clashed with it).

I suspect that if somebody starts their mod after the patch hits, the tools will detect a clash and fix it automatically. I'm just not 100% sure what the outcome is going to look like for pre-existing mods that happened to use the same IDs as the new game-files for other mod-specific files.