HVAA优化及BUG修复#155
Conversation
|
最近转法发现一个问题: |
@Qiyue0515 现在这个应该就是先we再im的啊 |
你好,能分享一个法系的设置给我导入吗? |
|
法师好像不能正确的释放im 只会释放weaken 在给每个怪都上完weaken之后就卡在这里了 |
|
@DreamSeeker08 @SakuyaSaki 之前的debuff逻辑有条件判断时可能会有点问题,分支新上传了一版(2.90.22.22),可以测试看下还有没有问题 |
|
@WayneFerdon 2.90.22.22 imp正确释放了 但是全部上好imp之后不会自动释放攻击,但是鼠标移动到对应的怪上后才会攻击 且有的时候只会用普通攻击 不会释放t123法术 |
@SakuyaSaki |
|
@WayneFerdon 确实是因为中途才开启脚本导致的 如果在一开始就开启然后再进入战斗的话就能正常释放t123 |
|
AR好像是ok 的但是GF不行 不知道为什么 |
@SakuyaSaki 有bug,修复了(2.90.22.24) |
|
发现现在的全部上debuff好像逻辑和之前的相比 不一样 之前会优先释放258这3个位子然后再释放没有释放到的 |
|
@SakuyaSaki |
|
@WayneFerdon 感谢 现在自动gf 已经正常工作了 但是debuff顺序释放好像还是没生效 现在还是按照权重来释放的 |
@SakuyaSaki 应该修复了(2.90.22.26) |
|
@WayneFerdon 观察了一下 现在的释放 第一次 释放目标1 会给 123上(可能是机制?给第一位上会顺延到后面) 第二次就会释放4 但是这个时候只会给45上debuff 这样3的位置会被重复上debuff 浪费了一个轮次 感觉还是应该改为给2 5 8位置轮流释放 |
让GPT写了一下 我试了一下这样是ok的 可以正确的释放到正确的258的位置() |
@SakuyaSaki 原来的是按照顺序从上往下选需要释放的
不过这个也有问题,新的版本已经改为:
|
|
新版这个 选择权重好像还是有点问题 在8个怪的时候 有时候会先在2或者6释放,这样123 567都会上上debuff 然后就会空下来4和8 这样会多放一次imp 这里的逻辑感觉如果是要按照释放的debuff到底有没有赋予 然后再对应的改变逻辑好像有点复杂() |
|
想到一个逻辑大概是就是重下往上检测第一个带debuff的 然后+2就是下一个需要释放的目标 |
|
@SakuyaSaki 遍历的时候忘记按照顺序遍历了,导致还是按照权重遍历,后面权重高,先遍历到被记录了,然后遍历到前面的低权重的时候,算出来有效范围都一样,不大于先记录的,所以没覆盖掉
从下往上找这个如果之前手动选了最后一个,就会变成直接补漏,所以还是得上面这个修复( |
|
@WayneFerdon 试了一下好像好像正常工作了 感谢更新 |
|
@WayneFerdon 这个有没有什么办法能导出log之类的吗 |
|
@lukasva77 It should be harmless, be still fixed in 2.91.16. |
|
userscript.html?name=%255BHV%255DAutoAttack.user.js&id=3f7312a3-4de3-4254-be84-fca477d537ea:5987 爆火花的时候时不时会出现,需要刷新页面才能恢复运行 |
@JKU533 更新2.91.17试试 不确定是什么原因导致怪物数据丢失了,不过这里本来就是相当于重新加载,因此先只做了个非空兼容 而且看报错不是整体丢失,像是丢失了其中部分怪物(应该是末尾的)。之前只在战斗中途开关脚本,导致读取了以前的怪物数据,导致数量对不上这种情况出现过类似的报错( |
|
有开启次要攻击模式的时候会误触发"以太之触"一直平A |
@JKU533 2.91.22 应该正常了 因为 2.91.22 把原来判断里的 想了下还是加回去才对,因为如果确实需要完全自定义条件,其实可以通过 另外2.91.22 新增了buffStack、targetBuffStack作为公式参数 |
|
2.91.20 getting defeated spams the developer console on firefox I'm not sure if there were any different red messages cause it lags the browser if they're too many closing the developer tools restores performance In hindsight should have copied all messages to .txt and looked them over Uncaught TypeError: can't access property "style" of null |
|
2.91.22 null Uncaught (in promise) DOMException: Node cannot be used in a document other than the one in which it was created |
|
seems both these 2 errors are not caused by hvAA but by other scripts and caught by hvAA's exception handling (or at least by compatibility issues). Which are unhandled in their process, such as the second one is by HVUT. The first one spams because the hvAA is waiting for the window to returns a |
|
2.91.23 improved the compatibility when defeated, which should fix the spamming error. |
次要攻击勾选某个攻击模式后,还是会一直用法杖平A |
@JKU533 那可能是条件判定出了问题 |
根本没公式...我现在用的是遭遇战配置 非常干净 折叠配置{"version":"2.91.3","lang":"0","buffSkillSwitch":true,"debuffSkillSwitch":true,"dropMonitor":true,"optionStandalone":true,"pauseButton":true,"stepInButton":true,"alert":true,"notification":true,"delay":0,"delay2":0,"attackStatus":1,"battleOrderName":"Pause","battleOrder":{"autoPause":true},"attackStatusSwitch":{"5":true},"attackStatusSwitchCondition5":{"0":["(skillOTOS.151+skillOTOS.152+skillOTOS.153) == 0"]},"highSkillCondition":{"0":["monsterAlive,3,2"],"1":["roundType,5,\"rb\""],"2":["roundLeft,5,0"],"3":["roundType,5,\"ba\""]},"turnOnSS":true,"turnOnSSCondition":{"0":["oc,1,249"]},"turnOffSSCondition":{"0":["oc,2,120"],"1":["_isCd_1111,5,0","oc,2,180"]},"autoPause":true,"pauseCondition":{"1":["roundType,5,\"rb\""],"2":["sp,4,50"],"3":["roundType,5,\"gr\""],"4":["roundType,5,\"iw\""],"5":["roundType,5,\"ar\""]},"battleUnresponsive":{"Alert":true,"Reload":true},"battleUnresponsiveTime":{"Alert":20,"Reload":20},"encounterDisplay":true,"idleArenaLevels":"1,10,20,30,40,50,60,70,80,90,100,110,120,130,140,150,165,180,200,225,250,300","idleArenaValue":"1,3,5,8,9,11,12,13,15,16,17,19,20,21,23,24,26,27,28,29,32,33","arLevel":{"1":true,"10":true,"20":true,"30":true,"40":true,"50":true,"60":true,"70":true,"80":true,"90":true,"100":true,"110":true,"120":true,"130":true,"140":true,"150":true,"165":true,"180":true,"200":true,"225":true,"250":true,"300":true},"staminaEncounter":20,"staminaLow":30,"itemOrderName":"FC,Cure,HP,SP","itemOrderValue":"313,311,11195,11395","itemOrder":{"FC":true,"HP":true,"Cure":true,"SP":true},"item":{"FC":true,"HP":true,"Cure":true,"SP":true},"itemFCCondition":{"0":["_buffTurn_sparklife,5,0"]},"itemHPCondition":{"0":["_buffTurn_sparklife,5,0"]},"itemCureCondition":{"0":["hp,4,65"]},"itemMPCondition":{"0":["mp,4,50"]},"itemMECondition":{"0":["mp,4,20"]},"itemSPCondition":{"0":["sp,4,55"]},"itemSECondition":{"0":["sp,2,45"]},"channelSkill":{"AF":true},"channelSkill2":true,"channelSkill2OrderName":"AF","channelSkill2OrderValue":"432","channelSkill2Order":{"AF":true},"buffSkillOrderValue":"Re,AF","buffSkillOrder":{"Re":true,"AF":true},"buffSkillMDCondition":{"0":["mp,2,85"]},"buffSkillSDCondition":{"0":["sp,2,85"]},"buffSkillSLCondition":{"0":["hp,2,35"]},"buffSkillSSCondition":{"0":["hp,2,60"]},"buffSkill":{"AF":true,"Re":true},"buffSkillAFCondition":{"0":["mp,1,40"]},"buffSkillHeCondition":{"0":["mp,1,40"]},"debuffSkillTurnAlert":0,"debuffSkillOrderValue":"Im","debuffSkillOrder":{"Im":true},"debuffSkillWeAll":true,"debuffSkillDrCondition":{"0":["monsterAlive,5,1","bossAlive,5,1"]},"debuffSkill":{"Im":true},"debuffSkillImAll":true,"skillOrderValue":"OFC","skillOrder":{"OFC":true},"skillOFCCondition":{"0":["bossAll,3,1","monsterAlive,3,3"],"1":["monsterAlive,3,5"]},"scrollRoundType":{"rb":true},"scroll":{"Av":true,"Go":true},"scrollAvCondition":{"0":["turn,5, 2"]},"scrollGoCondition":{"0":["turn,5, 1"]},"weight":{"We":-4,"Bl":3,"Slo":3,"Si":-4,"Sle":5,"Im":-5,"PA":-4,"BW":-4,"Co":-1,"Dr":-4,"MN":-4,"Stun":-4,"CM":-5},"dropQuality":"0","roundNow":1,"roundAll":1} |
|
@JKU533 2.91.24应该好了( 原因是新的功能 |



Uh oh!
There was an error while loading. Please reload this page.