Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
MythicCrucible MythicCrucible
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 53
    • Issues 53
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • MythicCraft
  • MythicCrucibleMythicCrucible
  • Issues
  • #7

Closed
Open
Created Dec 28, 2020 by __BadName@s6007449

[Crucibles] ~OnShoot skills executed by a bow have power dependant on bow pull which can't be disabled

Summary

I've been making and testing items with mythiccrucibles and noticed my bows are acting weird. It turns out that how much the bow is pulled back affects the damage and speed of the projectile shot by ~onShoot trigger, as if the skills' power are being multiplied.

Steps to reproduce

Add any projectile skills on a bow with ~onShoot trigger and observe the damage and velocity of the projectile

Current behavior

It seems to modify the skill's power by multiplying rather than setting to a certain value. pav/pad=false will make the projectile velocity/distance normal but the damage will still be multiplied. power=(number) will just multiply its power again, suggesting that the power is being multiplied rather than set by pulling the bow, and as such can't be overriden/disabled. javadoc said there is a 'powerScale' option but it doesn't seem to do anything.

Intended correct behavior

the feature should be able to be disabled since it wasn't present in artifacts and this may cause unintended interactions.

Proposed fixes

allow disabling of the said feature, or let either power=(number) override the skill's power or powerScale=0.0 effectively disable it.

Edited Dec 28, 2020 by __BadName
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking