Skip to content

Conversation

@Regisle
Copy link
Member

@Regisle Regisle commented Jun 7, 2022

extension of #4423 by Wires

from his:

The only things missing from this PR are setting physical damage and still setting hex resistance and armour behind the scenes. This functionality might not be what is desired, but would supercede #4417

This still misses those, but also I would like a reset button to remove user inputs from certain boss value fields,
and it would be nice if enemy corpse life also used presets

and am planning on adding a placeholder function, which can set placeholder value based on a function

edit: a function to update values is both unneeded and complex

@Regisle Regisle added the user-interface Changes that only affect the UI label Jun 7, 2022
@Regisle Regisle requested a review from Wires77 June 7, 2022 13:20
Copy link
Member

@Wires77 Wires77 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good pending an export of the skill data. Would help keep the tooltip up-to-date. Putting the damage values in the tooltip doesn't make a lot of sense to me, though, since we're populating the boxes anyway.

One other thing I noticed that might want to get fixed here is that the values of the damage can go into the negatives on the config page

Comment on lines 325 to 326
elseif type(v) == "boolean" then
child.attrib.boolean = tostring(v)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This probably doesn't make sense if only edit controls have placeholders

Comment on lines 403 to 405
--if self.placeholder and (self.buf == '' or not self.buf) then
-- self:SetPlaceholder(self.placeholder)
--end
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove

Comment on lines +860 to +861
local enemyCritChance = env.configInput["enemyCritChance"] or env.configPlaceholder["enemyCritChance"] or 0
local enemyCritDamage = env.configInput["enemyCritDamage"] or env.configPlaceholder["enemyCritDamage"] or 0
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can this ever be 0 now?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

because of order of initialization it will be nil for a first pass, but is instantly rebuilt so, no the value will never be zero but it errors due to nil value on initialization

--survival time
do
local enemySkillTime = env.configInput.enemySpeed or 700
local enemySkillTime = env.configInput.enemySpeed or env.configPlaceholder.enemySpeed or 700
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Again, not sure if this will ever get to the 700 value

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same as above

local defaultPen = ""
build.configTab.varControls['enemyLightningPen']:SetPlaceholder(defaultPen, true)
build.configTab.varControls['enemyColdPen']:SetPlaceholder(defaultPen, true)
build.configTab.varControls['enemyFirePen']:SetPlaceholder(defaultPen, true)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For these boss values we might want to set the actual input, as I imagine people will want to see the real values regardless of what they had in the box before.

@Regisle Regisle mentioned this pull request Jun 25, 2022
Shaper Ball: Allocating Cosmic Wounds increases the penetration to 40% and adds 2 projectiles
Shaper Slam: Cannot be Evaded. Allocating Cosmic Wounds doubles the damage and cannot be blocked or dodged
Maven Memory Game: Is three separate hits, and has a large DoT effect. Neither is taken into account here.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Based on feedback this should explicitly state that for EHP hits before death >=4 to survive

Copy link
Member

@Wires77 Wires77 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A lot of discussion happened in Discord, but to summarize future work/concerns:

  • Users will have to put a value in each box that has a placeholder, otherwise the placeholder will take effect
  • A global config setting around enemyIsBoss is probably needed at this point, since "No" probably shouldn't be the default, and not everyone is doing exclusively the highest boss setting anymore

@Wires77 Wires77 changed the title Preset boss damage Add new config options for Boss Skill Presets Jul 2, 2022
@Wires77 Wires77 merged commit b007a6c into PathOfBuildingCommunity:dev Jul 2, 2022
@Regisle Regisle deleted the preset_boss_damage branch August 13, 2022 10:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

user-interface Changes that only affect the UI

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants