Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rebalance HVC #2022

Merged
merged 1 commit into from
Jul 25, 2021
Merged

Rebalance HVC #2022

merged 1 commit into from
Jul 25, 2021

Conversation

Tipchik87
Copy link
Contributor

At the request of some players made these changes. Reduced longRange by 1 cell, and improved ROF. The HVC is now more true to its name, but these changes were made not for the sake of the name, but for a more even balance between the HVC and the other T2 weapons.

@KJeff01 KJeff01 added this to the 4.1.1 milestone Jul 23, 2021
@Next67
Copy link
Contributor

Next67 commented Jul 23, 2021

Previously, the splash damage was removed under 0, now the range has also changed. All this together will weaken her greatly, so I don't like it.
The Cannon Line is weakening, but the Rocket Line will remain unchanged and this will affect the balance of the game.

@Tipchik87
Copy link
Contributor Author

Tipchik87 commented Jul 24, 2021

HVC's splash damage meant nothing (small 32 radius+incorrect splash mechanics) in all versions of the game except 4.0.1, so the splash was removed altogether. In version 4.0.1, HVC had a splash of 64 so was slightly better against light cyborgs. The problem that HVC is better than the rest of the T2 stage weapons was picked up in 3.4.1 or even earlier. As long as the HVC has a longRange of 10 and the cyborg has a 9, they will be the best weapon on T2 in No Shared Res mode.

@KJeff01 KJeff01 merged commit 2edbb1b into Warzone2100:master Jul 25, 2021
@Tipchik87
Copy link
Contributor Author

I'll start from afar. No Shared Res mode requires the ability to do research in the right order because you only have 5 labs, so in this mode the way to VTOL and artillery is dangerous because it comes down to skipping damage buffs, ROF, ACC or Composite Alloys and therefore in No Shared Res cyborgs are the main unit because they have good resistance against Cannons and Rockets and appearance of VTOL or artillery is unlikely and relevance of cyborgs remains until T4 stage. In Shared Res mode, cyborgs lose their relevance at T2 when artillery or VTOL Bombs appear. Also, these modes are differently affected by changes in balance. As an example, we recently separated the damage buff chain from Bombard. In Shared mode this will not affect the outcome of battles, and in No Shared mode it will make it easier to use mortars in general and access to howitzers. By doing so, we make battles on No Shared more varied, while not affecting the game on Shared.
Likewise will be if the changes in HVC hit the release i.e. on No Shared will become relevant to use the heavy cannon and twin assault cannon and also get rid of the point of no return. The point is that players using the Cannons branch on the No Shared getting HVC (later HVC cyborg) begin to produce it to the limit and when you reach a certain amount of HVC there is a point of no return. Anyone using Rockets or other Cannons from the Cannons branch will be effectively shot with HVC because all other weapons on T2 have a ranged of 1-2 cells less. Like if the rocket scourge was available before the needle for a few minutes would be a similar situation. In Shared mode changes of HVC will be unimportant because its use starts mostly on tracks and heavy body which increases production time, artillery and VTOL appear, cyborg production stops before reaching cyborg HVC, necessity of building mobile AA appears. As a result, HVC pales in comparison to everything that comes later.
I hope this will now become clear, especially for those who do not play No Shared mode. These HVC changes are taken from tests on version 3.4.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants