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

Change remaining Vulcan vs Light values to 50 #14244

Merged
merged 1 commit into from Nov 12, 2017

Conversation

Projects
None yet
6 participants
@Smittytron
Contributor

Smittytron commented Oct 22, 2017

Closes #14185
Was intended with #13790

@MustaphaTR

This comment has been minimized.

Show comment
Hide comment
@MustaphaTR

MustaphaTR Oct 22, 2017

Member

Warhead@1Dam: SpreadDamage is still using default 60 coming from Inherits: ^HeavyMG. Please add Light: 50 under None: 200 under there too.

Member

MustaphaTR commented Oct 22, 2017

Warhead@1Dam: SpreadDamage is still using default 60 coming from Inherits: ^HeavyMG. Please add Light: 50 under None: 200 under there too.

@Smittytron

This comment has been minimized.

Show comment
Hide comment
@Smittytron

Smittytron Oct 22, 2017

Contributor

Warhead@1Dam:` SpreadDamage is still using default 60 coming from Inherits: ^HeavyMG. Please add Light: 50 under None: 200 under there too.

Hmm, talked to SoScared about that. Problem is that'll nerf Yaks and Hinds vs light vehicles as well, which was not intended. Would it be best to take Vulcan off of inheritance?

Contributor

Smittytron commented Oct 22, 2017

Warhead@1Dam:` SpreadDamage is still using default 60 coming from Inherits: ^HeavyMG. Please add Light: 50 under None: 200 under there too.

Hmm, talked to SoScared about that. Problem is that'll nerf Yaks and Hinds vs light vehicles as well, which was not intended. Would it be best to take Vulcan off of inheritance?

@MustaphaTR

This comment has been minimized.

Show comment
Hide comment
@MustaphaTR

MustaphaTR Oct 22, 2017

Member

Hmm, talked to SoScared about that. Problem is that'll nerf Yaks and Hinds vs light vehicles as well, which was not intended. Would it be best to take Vulcan off of inheritance?

You need to change it under Warhead@1Dam: SpreadDamage of Vulcan, not ^HeavyMG. Then it won't affect another weapon.

Member

MustaphaTR commented Oct 22, 2017

Hmm, talked to SoScared about that. Problem is that'll nerf Yaks and Hinds vs light vehicles as well, which was not intended. Would it be best to take Vulcan off of inheritance?

You need to change it under Warhead@1Dam: SpreadDamage of Vulcan, not ^HeavyMG. Then it won't affect another weapon.

@Smittytron

This comment has been minimized.

Show comment
Hide comment
@Smittytron

Smittytron Oct 22, 2017

Contributor

Ugh, I clearly don't know how to squash correctly

Contributor

Smittytron commented Oct 22, 2017

Ugh, I clearly don't know how to squash correctly

@reaperrr

This comment has been minimized.

Show comment
Hide comment
@reaperrr

reaperrr Oct 22, 2017

Contributor

Do you rebase via commandline or GUI?
For the former, you'd just have to git rebase -i HEAD~2, delete the line with the first commit, then execute :x. Then force-push your local branch to this PR branch again.

Contributor

reaperrr commented Oct 22, 2017

Do you rebase via commandline or GUI?
For the former, you'd just have to git rebase -i HEAD~2, delete the line with the first commit, then execute :x. Then force-push your local branch to this PR branch again.

@Smittytron

This comment has been minimized.

Show comment
Hide comment
@Smittytron

Smittytron Oct 23, 2017

Contributor

Thanks! This should look more sane now.

Contributor

Smittytron commented Oct 23, 2017

Thanks! This should look more sane now.

@reaperrr

This comment has been minimized.

Show comment
Hide comment
@reaperrr

reaperrr Nov 3, 2017

Contributor

Just wondering, do you know if @SoScared actually made that balance change based on test results with correct values (as in this PR), or did he also only change that 1 value on the balance test maps?

I'm asking because if the 60 -> 50 nerf decision was based on only 1 nerfed warhead, a value of 57 or 58 for all warheads would be the closest match.
I have no idea if the pillbox is still considered too powerful on bleed/current release so maybe this PR is wanted as-is either way, I just want to make sure we don't merge a change based on a misconception.

Contributor

reaperrr commented Nov 3, 2017

Just wondering, do you know if @SoScared actually made that balance change based on test results with correct values (as in this PR), or did he also only change that 1 value on the balance test maps?

I'm asking because if the 60 -> 50 nerf decision was based on only 1 nerfed warhead, a value of 57 or 58 for all warheads would be the closest match.
I have no idea if the pillbox is still considered too powerful on bleed/current release so maybe this PR is wanted as-is either way, I just want to make sure we don't merge a change based on a misconception.

@Smittytron

This comment has been minimized.

Show comment
Hide comment
@Smittytron

Smittytron Nov 3, 2017

Contributor

I couldn't find a change to vulcan values in SoScared's playtest maps. It looks like he had the change listed as a potential alternative apart from the playtests. I'll see if I can get ahold of him to clarify.

What I can confirm is that the strength of pillboxes, including the ability to shred light vehicles, is still a common complaint I hear.

Contributor

Smittytron commented Nov 3, 2017

I couldn't find a change to vulcan values in SoScared's playtest maps. It looks like he had the change listed as a potential alternative apart from the playtests. I'll see if I can get ahold of him to clarify.

What I can confirm is that the strength of pillboxes, including the ability to shred light vehicles, is still a common complaint I hear.

@SoScared

This comment has been minimized.

Show comment
Hide comment
@SoScared

SoScared Nov 12, 2017

Member

The vulcan change was on the loose end of the playtests. As @Smittytron mentioned its strength vs light armor was a common observation however, having a very limited area of effect (and new path for the game meta) fixing the values to all-50/60 is probably fine either way.

Member

SoScared commented Nov 12, 2017

The vulcan change was on the loose end of the playtests. As @Smittytron mentioned its strength vs light armor was a common observation however, having a very limited area of effect (and new path for the game meta) fixing the values to all-50/60 is probably fine either way.

@pchote

pchote approved these changes Nov 12, 2017

@pchote pchote merged commit e65ffc8 into OpenRA:bleed Nov 12, 2017

2 checks passed

continuous-integration/appveyor/pr AppVeyor build succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details

@Smittytron Smittytron deleted the Smittytron:Vulcan-vs-Light branch Nov 14, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment