HVAA优化及BUG修复

[WayneFerdon]

1. 增加初始闲置竞技场配置非空检测
2. 修正其他技能的OC判断及选择范围判断，修正条件判断中iscd的值与Readme中示例不相符的问题 (修复技能可释放判断及其他技能技能排序无效问题 #154 未进行冲突处理直接覆盖了，因此按照其中实际有效的内容重新修改了)

[Qiyue0515]

最近转法发现一个问题：
// 先处理特殊的 “先给全体上buff”
let skillPack = ['We', 'Im'];
这里改成先上weaken再上Imperil会比较好，这样血线的压力会小一点

[WayneFerdon]

最近转法发现一个问题： // 先处理特殊的 “先给全体上buff” let skillPack = ['We', 'Im']; 这里改成先上weaken再上Imperil会比较好，这样血线的压力会小一点

@Qiyue0515 现在这个应该就是先we再im的啊

[DreamSeeker08]

最近转法发现一个问题： // 先处理特殊的 “先给全体上buff” let skillPack = ['We', 'Im']; 这里改成先上weaken再上Imperil会比较好，这样血线的压力会小一点

你好，能分享一个法系的设置给我导入吗？
我不太会弄，更新到最新的v2.90.22.20还是不会释放陷危、虚弱等debuf

[Kotone-Hikaru]

法师好像不能正确的释放im 只会释放weaken 在给每个怪都上完weaken之后就卡在这里了

[WayneFerdon]

@DreamSeeker08 @SakuyaSaki 之前的debuff逻辑有条件判断时可能会有点问题，分支新上传了一版(2.90.22.22)，可以测试看下还有没有问题

[Kotone-Hikaru]

@WayneFerdon 2.90.22.22 imp正确释放了 但是全部上好imp之后不会自动释放攻击，但是鼠标移动到对应的怪上后才会攻击 且有的时候只会用普通攻击 不会释放t123法术

[WayneFerdon]

@WayneFerdon 2.90.22.22 imp正确释放了 但是全部上好imp之后不会自动释放攻击，但是鼠标移动到对应的怪上后才会攻击 且有的时候只会用普通攻击 不会释放t123法术

@SakuyaSaki
我这里测试是正常的，普通和高级的都能够释放，不确定是什么原因
不过推测可能是战斗中途启用新脚本，导致ability数据未初始化，战斗中读取技能范围数据出错，这个节点刚好是点击完技能还没选目标（在算范围），如果有mb等脚本的话刚好移上去就选中了?
新的版本（2.90.22.23）增加了非空检测，可以再看下

[Kotone-Hikaru]

@WayneFerdon 确实是因为中途才开启脚本导致的 如果在一开始就开启然后再进入战斗的话就能正常释放t123
不过这个 自动闲置竞技场好像有点问题 还是说逻辑改变了

[Kotone-Hikaru]

AR好像是ok 的但是GF不行 不知道为什么

[WayneFerdon]

AR好像是ok 的但是GF不行 不知道为什么

@SakuyaSaki 有bug，修复了(2.90.22.24)

[Kotone-Hikaru]

发现现在的全部上debuff好像逻辑和之前的相比 不一样 之前会优先释放258这3个位子然后再释放没有释放到的
现在是按照优先级来释放的 大部分时候是乱序 会导致有的时候会多1t 理论上来说假如敌人是8个的话 第一次释放 2 5 7 这样应该是最好的 （有机会补到6号位没有上到debuff的情况）其他的按照258释放 一遍然后补漏掉的 比较好

[WayneFerdon]

@SakuyaSaki
给全体放debuff的两个各加了选项，可以选是按照位置还是权重释放
按位置还是用权重的逻辑，但是统一权重为-1而非按状态计算，保留结合用死亡、已有debuff等的特殊权重进行排除
本来想直接改了，但是We给高权重的先放有时也能降低自己受到的伤害，所以各自处理了（

[Kotone-Hikaru]

@WayneFerdon 感谢 现在自动gf 已经正常工作了 但是debuff顺序释放好像还是没生效 现在还是按照权重来释放的

[WayneFerdon]

@WayneFerdon 感谢 现在自动gf 已经正常工作了 但是debuff顺序释放好像还是没生效 现在还是按照权重来释放的

@SakuyaSaki 应该修复了(2.90.22.26)
漏了选初始目标也要按顺序了（

[Kotone-Hikaru]

@WayneFerdon 观察了一下 现在的释放 第一次 释放目标1 会给 123上（可能是机制？给第一位上会顺延到后面） 第二次就会释放4 但是这个时候只会给45上debuff 这样3的位置会被重复上debuff 浪费了一个轮次 感觉还是应该改为给2 5 8位置轮流释放

[Kotone-Hikaru]

function getRangeCenterID(target, range = undefined, isWeaponAttack = false, excludeCondition = undefined, forceUseIndex = undefined) {
    // 静态计数器
    if (typeof getRangeCenterID.callCount === 'undefined') getRangeCenterID.callCount = 0;
    getRangeCenterID.callCount++;

    // --- 固定顺序目标 ---
    const fixedIndices = [1, 4, 7]; // 数组索引
    let msTemp = JSON.parse(JSON.stringify(g('battle').monsterStatus));
    msTemp.sort(objArrSort('order'));

    if (getRangeCenterID.callCount <= fixedIndices.length) {
        // 尝试获取固定目标，如果越界或死亡就跳过
        for (let i = getRangeCenterID.callCount - 1; i < fixedIndices.length; i++) {
            const idx = fixedIndices[i];
            if (idx >= 0 && idx < msTemp.length && !msTemp[idx].isDead) {
                return getMonsterID(msTemp[idx].order);
            }
        }
        // 如果固定顺序没有可用目标，回归正常逻辑
    }

    // ---------------- 原本逻辑 ----------------
    if (!range) return getMonsterID(target);

    const centralExtraWeight = -1 * Math.log10(1 + (isWeaponAttack ? ((g('option').centralExtraRatio / 100) ?? 0) : 0));
    let order = target.order;
    let newOrder = order;

    let unreachableWeight = g('option').unreachableWeight;
    let minRank = Infinity;

    for (let i = order - range; i <= order + range; i++) {
        if (i < 0 || i >= msTemp.length || msTemp[i].isDead) continue;

        let rank = 0;
        for (let j = i - range; j <= i + range; j++) {
            let cew = (j === i) ? centralExtraWeight : 0;
            let mon = msTemp[j];

            if (j < 0 || j >= msTemp.length || mon.isDead || (excludeCondition && excludeCondition(mon))) {
                rank += unreachableWeight - cew;
                continue;
            }

            rank += cew;
            rank += forceUseIndex ? -1 : mon.finWeight;
        }

        if (rank < minRank) {
            minRank = rank;
            newOrder = i;
        }
    }

    return getMonsterID(newOrder);
}

让GPT写了一下 我试了一下这样是ok的 可以正确的释放到正确的258的位置（）

[WayneFerdon]

@WayneFerdon 观察了一下 现在的释放 第一次 释放目标1 会给 123上（可能是机制？给第一位上会顺延到后面） 第二次就会释放4 但是这个时候只会给45上debuff 这样3的位置会被重复上debuff 浪费了一个轮次 感觉还是应该改为给2 5 8位置轮流释放

@SakuyaSaki
gpt这个即使不是全体或按顺序也会强行按顺序，而且目标死亡往后跳一个实际也会将死亡的包含在范围内了，也是不对的

原来的是按照顺序从上往下选需要释放的
但是释放本身可能会失败（被抵抗了）
你的这个可能是放了123，然后选5放456，但是6被抵抗了
例如：

1. 在2放完123
2. 在5放456，5失败
3. 此时因为5需要释放，而包含5的最优的范围为567，就会在6释放567

不过这个也有问题，新的版本已经改为：

1. 释放全体时会遍历全部需要放的目标
2. 然后选出包含任意目标中权重最优的（按顺序的话仍是单个权重为-1）
3. 这样就能优先往后去释放一片目标（无论是按顺序还是实际权重，确保收益最大化）
4. 然后再进行补漏（失败或者未释放到的）

[Kotone-Hikaru]

新版这个 选择权重好像还是有点问题 在8个怪的时候 有时候会先在2或者6释放，这样123 567都会上上debuff 然后就会空下来4和8 这样会多放一次imp 这里的逻辑感觉如果是要按照释放的debuff到底有没有赋予 然后再对应的改变逻辑好像有点复杂（）

[Kotone-Hikaru]

想到一个逻辑大概是就是重下往上检测第一个带debuff的 然后+2就是下一个需要释放的目标
比如给123上好imp了 然后下一个就应该上在5
假如1和3抵抗了 就给2的+2上 那就是345 然后漏掉的之后再补？
不知道能不能实现（）

[WayneFerdon]

@SakuyaSaki 遍历的时候忘记按照顺序遍历了，导致还是按照权重遍历，后面权重高，先遍历到被记录了，然后遍历到前面的低权重的时候，算出来有效范围都一样，不大于先记录的，所以没覆盖掉
2.90.22.29已改为要按顺序的话就会按顺序遍历，这下应该行了（

想到一个逻辑大概是就是重下往上检测第一个带debuff的 然后+2就是下一个需要释放的目标 比如给123上好imp了 然后下一个就应该上在5 假如1和3抵抗了 就给2的+2上 那就是345 然后漏掉的之后再补？ 不知道能不能实现（）

从下往上找这个如果之前手动选了最后一个，就会变成直接补漏，所以还是得上面这个修复（

[Kotone-Hikaru]

@WayneFerdon 试了一下好像好像正常工作了 感谢更新

[Kotone-Hikaru]

发现卷轴使用有点异常 守护卷轴好像 有点问题 同样的条件 一次 gf 其他卷轴都是15左右 守护卷轴用了150

且这个好像没有效果 在ar也会不停释放守护卷轴

[WayneFerdon]

发现卷轴使用有点异常 守护卷轴好像 有点问题 同样的条件 一次 gf 其他卷轴都是15左右 守护卷轴用了150 且这个好像没有效果 在ar也会不停释放守护卷轴

@SakuyaSaki 我这里是正常的啊（
没有一直放，而且筛选也是有用的
不过原来的释放逻辑也有点问题，也稍微改了下（2.90.22.30）

[Kotone-Hikaru]

@WayneFerdon 这个有没有什么办法能导出log之类的吗

[Kotone-Hikaru]

You evade the attack from Macallan. -- Aiga Mizuki crits you for 3810 wind damage. You evade the attack from Google Dancing Israelis. You evade the attack from Hemidactylus. You evade the attack from Storyteller. Youshi153 gains the effect Imperiled. Hemidactylus gains the effect Coalesced Mana. Hemidactylus gains the effect Imperiled. Practiced Ass Spanker gains the effect Imperiled. You cast Imperil.   Cooldown expired for Storms of Njord You are healed for 11583 Health Points. You cast Cure.   You gain the effect Protection. You use Scroll of Protection.   Cooldown expired for Cure You evade the attack from Youshi153. You evade the attack from Practiced Ass Spanker. Hemidactylus gains the effect Coalesced Mana. Hemidactylus gains the effect Imperiled. Practiced Ass Spanker gains the effect Imperiled. Macallan gains the effect Imperiled. You cast Imperil.   You evade the attack from Macallan. Aiga Mizuki crits you for 3487 wind damage. You evade the attack from Storyteller. Hemidactylus crits you for 5077 slashing damage. Your spirit shield absorbs 1553 points of damage from the attack into 24 points of spirit damage. Aiga Mizuki gains the effect Imperiled. Storyteller gains the effect Coalesced Mana. Storyteller gains the effect Imperiled. Google Dancing Israelis gains the effect Imperiled. You cast Imperil.   Google Dancing Israelis hits you for 2676 wind damage. You evade the attack from Youshi153. You are healed for 11583 Health Points. You cast Cure.   Spawned Monster G: MID=282436 (Youshi153) LV=500 HP=174260 Spawned Monster F: MID=110494 (Hemidactylus) LV=500 HP=203444 Spawned Monster E: MID=153284 (Practiced Ass Spanker) LV=500 HP=183060 Spawned Monster D: MID=124000 (Macallan) LV=500 HP=183060 Spawned Monster C: MID=112618 (Aiga Mizuki) LV=500 HP=179060 Spawned Monster B: MID=194240 (Storyteller) LV=500 HP=171860 这是一次异常的释放保护卷轴的战斗记录

我试了几次 每次在异常释放卷轴的时候 都会放一个cure

[lukasva77]

version 2.91.5

this happened today two long red messages than a yellow one and then a short red one

no any ill effects that I can see

but the message
Blocking requests for 40 seconds due to excessive request rate
scares me it happened inside the page I'm doing persistent and isekai at the same time I wonder if it's that maybe we need an option to set the speed to half
also this happened after finishing an arena and then this message appeared

Blocking requests for 40 seconds due to excessive request rate

as I tried doing something

TypeError: can't access property "textContent", gE(...) is null
getCurrentStamina moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:4710
asyncSetStamina moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:4325
asyncOnIdle moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:4108
asyncOnIdle moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:4110
onIdle moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:1113
VMol1gxq6vzhm moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:382
VMol1gxq6vzhm moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:7232
VMol1gxq6vzhm moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:7233
ln moz-extension://30326764-a8bc-4293-9765-e4fad582e458/sandbox/injected-web.js:1
moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:1
[HV]AutoAttack.user.js:4714:29

TypeError: can't access property Symbol.iterator of undefined
asyncSetStamina moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:4325
asyncOnIdle moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:4108
asyncOnIdle moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:4110
onIdle moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:1113
VMol1gxq6vzhm moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:382
VMol1gxq6vzhm moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:7232
VMol1gxq6vzhm moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:7233
ln moz-extension://30326764-a8bc-4293-9765-e4fad582e458/sandbox/injected-web.js:1
moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:1
[HV]AutoAttack.user.js:4392:29

This page is in Quirks Mode. Page layout may be impacted. For Standards Mode use “”. hentaiverse.org

GET
https://hentaiverse.org/favicon.ico
[HTTP/3 404 73ms]

Blocking requests for 40 seconds due to excessive request rate

[lukasva77]

Red message inside sell salvage screen I wonder if it's native or from HV Utils cause that still has bugs and a new version will be coming soon
also happened after I salvaged stuff I think somewhere in those menus

Uncaught ReferenceError: curr_hover_eqid is not defined
unhover_equip https://hentaiverse.org/z/091/hveqc.js:5
onmouseout https://hentaiverse.org/?s=Bazaar&ss=am&screen=salvage:1
hveqc.js:5:425

[lukasva77]

Latest version 2.91.7
This stuff repeated after trying later in persistent can't start auto arena and blocking request was higher like 120 seconds
also wasn't doing battle in isekai so don't know

TypeError: can't access property "textContent", gE(...) is null
getCurrentStamina moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:4512
asyncSetStamina moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:4226
asyncOnIdle moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:4019
asyncOnIdle moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:4021
onIdle moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:1110
VMiulv4ow83fm moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:382
VMiulv4ow83fm moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:7021
VMiulv4ow83fm moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:7022
ln moz-extension://30326764-a8bc-4293-9765-e4fad582e458/sandbox/injected-web.js:1
moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:1
[HV]AutoAttack.user.js:4516:29

TypeError: can't access property Symbol.iterator of undefined
asyncSetStamina moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:4226
asyncOnIdle moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:4019
asyncOnIdle moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:4021
onIdle moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:1110
VMiulv4ow83fm moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:382
VMiulv4ow83fm moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:7021
VMiulv4ow83fm moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:7022
ln moz-extension://30326764-a8bc-4293-9765-e4fad582e458/sandbox/injected-web.js:1
moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:1
[HV]AutoAttack.user.js:4293:29

This page is in Quirks Mode. Page layout may be impacted. For Standards Mode use “”. hentaiverse.org

GET
https://hentaiverse.org/favicon.ico
[HTTP/3 404 80ms]

[lukasva77]

Wait should be HV Utils I think check page 34 of thread

[Script] HV Utils 4.2.1 (8 Jun 2026), A comprehensive out-of-battle script for Hentaiverse and ISK

so it has serious bugs after this big transition that happened to persistent

well atleast the being banned for x amount of seconds

[lukasva77]

version 2.91.7

I've disabled HV Utils but
Idle arena seems to stopped working clicking reset Isn't helping

[lukasva77]

Also random encounter got skipped I think most of this is from HV Utils

[lukasva77]

disabled HV Utils started an arena got a freeze on round 28 out of 35

and then after refresh got
Blocking requests for 61 seconds due to excessive request rate

Uncaught SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data
api_response https://hentaiverse.org/?s=Battle&ss=ar line 5556 > injectedScript:9
process_action https://hentaiverse.org/z/091/hvc.js:39
api_call https://hentaiverse.org/?s=Battle&ss=ar line 5536 > injectedScript:9
touch_and_go https://hentaiverse.org/z/091/hvc.js:38
commit_target https://hentaiverse.org/z/091/hvc.js:38
onclick https://hentaiverse.org/?s=Battle&ss=ar:1
clickMonster moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:6497
tryAttack moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:6774
onAttack moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:6813
attack moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:6717
onBattleRound moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:5205
onclick moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:5413
onload https://hentaiverse.org/?s=Battle&ss=ar line 5536 > injectedScript:12
api_call https://hentaiverse.org/?s=Battle&ss=ar line 5536 > injectedScript:10
touch_and_go https://hentaiverse.org/z/091/hvc.js:38
commit_target https://hentaiverse.org/z/091/hvc.js:38
onclick https://hentaiverse.org/?s=Battle&ss=ar:1
clickMonster moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:6497
useDebuffSkill moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:6686
useDeSkill moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:6592
onBattleRound moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:5205
onclick moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:5413
onload https://hentaiverse.org/?s=Battle&ss=ar line 5536 > injectedScript:12
api_call https://hentaiverse.org/?s=Battle&ss=ar line 5536 > injectedScript:10
touch_and_go https://hentaiverse.org/z/091/hvc.js:38
commit_target https://hentaiverse.org/z/091/hvc.js:38
onclick https://hentaiverse.org/?s=Battle&ss=ar:1
clickMonster moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:6497
useDebuffSkill moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:6686
useDeSkill moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:6592
onBattleRound moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:5205
onRoundEnd moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:5476
onclick moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:5422
onload https://hentaiverse.org/?s=Battle&ss=ar line 5536 > injectedScript:12
api_call https://hentaiverse.org/?s=Battle&ss=ar line 5536 > injectedScript:10
touch_and_go https://hentaiverse.org/z/091/hvc.js:38
commit_target https://hentaiverse.org/z/091/hvc.js:38
onclick https://hentaiverse.org/?s=Battle&ss=ar:1
clickMonster moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:6497
tryAttack moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:6774
onAttack moz-extension://30326764-a8bc-4293-9765-e4fad582e458/ [HV]AutoAttack.user.js#23:6813
hentaiverse.org:9:24

[lukasva77]

Sorry for message spamming

[lukasva77]

Also I tried downgrading from 2.91.7 to 2.91.5 so the red text two messages above might be from that

[lukasva77]

Idle arena is dead in latest version

[lukasva77]

downgrading to 2.91.5 works and idle arena is back

that version I called looking stable at least it does everything that I'm using

[lukasva77]

Also about the random encounter It tends to miss one or two here and there all the time it got the next one anyway it's nothing important

It was always like this over the years

[JKU533]

打开着控制台运行每步刷新很卡是这个影响吗?
Duplicate form field id in the same form
Multiple form field elements in the same form have the same id attribute value. This might prevent the browser from correctly autofilling the form.
To fix this issue, use unique id attribute values for each form field.
100 项资源

吸收卷轴的使用失效了

[WayneFerdon]

@lukasva77 idleArena should be fixed in 2.91.8

---

Red message inside sell salvage screen I wonder if it's native or from HV Utils cause that still has bugs and a new version will be coming soon also happened after I salvaged stuff I think somewhere in those menus

Uncaught ReferenceError: curr_hover_eqid is not defined unhover_equip https://hentaiverse.org/z/091/hveqc.js:5 onmouseout https://hentaiverse.org/?s=Bazaar&ss=am&screen=salvage:1 hveqc.js:5:425

This seems to be caused by HV Utils.

---

TypeError: can't access property "textContent", gE(...) is null

These are caused by the temporary block, which is due to HV Utils (exactly the situation below)

Wait should be HV Utils I think check page 34 of thread

[Script] HV Utils 4.2.1 (8 Jun 2026), A comprehensive out-of-battle script for Hentaiverse and ISK

so it has serious bugs after this big transition that happened to persistent

well atleast the being banned for x amount of seconds

Try the temporary method below: (from the above comment #155 (comment))

No conflicts as far as I know. I myself use HVUT as well. Yet to restrict the general update frequency, try editing the HVUT and replace const $ajax = { with const $ajax = window.top.$ajax ??= unsafeWindow.$ajax ??= {, and reorder the script execution order to run hvAA before HVUT. This should ensure HVUT uses the same connection frequency restriction as hvAA (with a global cooldown).

// AJAX
- const $ajax = {
+ const $ajax = window.top.$ajax ??= unsafeWindow.$ajax ??= {
interval: 300, // DO NOT DECREASE THIS NUMBER, OR IT MAY TRIGGER THE SERVER'S LIMITER AND YOU WILL GET BANNED

PS: $ajax in the current version of hvAA is based directly on the one from HVUT – and then further improved.

PPS: Even if HV Utils itself does not cause frequent connections, it is still recommended that both scripts use the same AJAX approach to avoid the combined connection frequency becoming too high.

---

Also random encounter got skipped I think most of this is from HV Utils

• check if HV Utils' encounter option is enabled, which will conflict with hvAA's encounter. HV Utils will attempt to fetch an eh gallary, which will making an encounter uncatchable for hvAA.
• Not sure if this will cause a decrease of the number of daily total encounters, but it's ok if the number of encounters finished per day is 24
• But it could also be a original hv issue since:

Also about the random encounter It tends to miss one or two here and there all the time it got the next one anyway it's nothing important

It was always like this over the years

[WayneFerdon]

@JKU533

打开着控制台运行每步刷新很卡是这个影响吗? Duplicate form field id in the same form Multiple form field elements in the same form have the same id attribute value. This might prevent the browser from correctly autofilling the form. To fix this issue, use unique id attribute values for each form field. 100 项资源

卡可能不是因为这个，可能是 控制台记录 或 网络>录制的网络日志 过多导致的，不过现在照理说hvAA应该没有很多日志输出（

吸收卷轴的使用失效了

吸收卷轴我这是能放出来的，因此不确定和具体的条件有没有关系

[JKU533]

可能不是因为这个，可能是很多控制台记录或网络>卡记录的网络日志过多导致的，不过现在照理说hvAA应该没有日志输出

看来是网络问题，今天梯子延迟有点高加上开着控制台会闪烁加载看着很卡

吸收卷轴我是能放出来的，因此不确定和具体的条件没有关系

是我自己的问题,异世界用错人格，没插吸收卷轴，表世界根本也没插
不好意思打扰了,感谢!

[lukasva77]

I didn't apply the HV Utils fix my bad cause I thought It will be updated soonish
but I wonder if the fix will be needed to be applied every time but on another hand the next HV Utils version might be the last for a long time like next version will come a couple years from now who knows

[JKU533]

2.91.10报错 降级2.91.9没问题
主世界没问题 异世界直接加载失败
userscript.html?name=%255BHV%255DAutoAttack.user.js&id=3f7312a3-4de3-4254-be84-fca477d537ea:7022
TypeError: Cannot convert undefined or null to object
at Function.values ()
at loadOption (userscript.html?name=%255BHV%255DAutoAttack.user.js&id=3f7312a3-4de3-4254-be84-fca477d537ea:1396:18)
at checkOption (userscript.html?name=%255BHV%255DAutoAttack.user.js&id=3f7312a3-4de3-4254-be84-fca477d537ea:1044:7)
at checkIsWindowTop (userscript.html?name=%255BHV%255DAutoAttack.user.js&id=3f7312a3-4de3-4254-be84-fca477d537ea:970:9)
at userscript.html?name=%255BHV%255DAutoAttack.user.js&id=3f7312a3-4de3-4254-be84-fca477d537ea:380:12
at Proxy. (userscript.html?name=%255BHV%255DAutoAttack.user.js&id=3f7312a3-4de3-4254-be84-fca477d537ea:7025:3)
at At (:10:89)
at userscript.html?name=%255BHV%255DAutoAttack.user.js&id=3f7312a3-4de3-4254-be84-fca477d537ea:1:88
at window.__f__mqaxzxzu.gj6 (userscript.html?name=%255BHV%255DAutoAttack.user.js&id=3f7312a3-4de3-4254-be84-fca477d537ea:1:425)
at At (:10:89)

[WayneFerdon]

@JKU533

2.91.10报错 降级2.91.9没问题 主世界没问题 异世界直接加载失败

忘加非空检查了，2.91.11应该好了（