HVAA优化及BUG修复 by WayneFerdon · Pull Request #155 · dodying/UserJs

WayneFerdon · 2025-08-21T03:19:04Z

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

Qiyue0515 · 2025-09-05T04:36:44Z

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

WayneFerdon · 2025-09-05T04:49:59Z

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

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

DreamSeeker08 · 2025-10-21T15:18:10Z

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

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

Kotone-Hikaru · 2025-10-22T10:09:30Z

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

WayneFerdon · 2025-10-22T10:28:33Z

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

Kotone-Hikaru · 2025-10-23T03:33:32Z

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

WayneFerdon · 2025-10-23T08:36:14Z

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

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

Kotone-Hikaru · 2025-10-23T10:15:27Z

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

Kotone-Hikaru · 2025-10-23T10:28:06Z

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

WayneFerdon · 2025-10-23T13:15:58Z

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

@Sakuyasaki 有bug，修复了(2.90.22.24)

Kotone-Hikaru · 2025-10-23T13:32:42Z

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

WayneFerdon · 2025-10-23T14:51:41Z

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

Kotone-Hikaru · 2025-10-24T05:05:54Z

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

WayneFerdon · 2025-10-24T13:14:10Z

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

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

Kotone-Hikaru · 2025-10-25T02:18:39Z

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

Kotone-Hikaru · 2025-10-25T03:52:00Z

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 · 2025-10-25T09:22:18Z

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

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

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

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

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

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

Kotone-Hikaru · 2025-10-25T09:35:37Z

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

Kotone-Hikaru · 2025-10-25T09:45:21Z

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

WayneFerdon · 2025-10-25T09:57:04Z

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

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

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

Kotone-Hikaru · 2025-10-25T10:01:23Z

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

Kotone-Hikaru · 2025-10-27T03:17:39Z

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

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

WayneFerdon · 2025-10-27T07:34:54Z

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

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

Kotone-Hikaru · 2025-10-27T08:02:47Z

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

Kotone-Hikaru · 2025-10-27T08:05:39Z

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

WayneFerdon · 2026-06-26T12:22:08Z

2.91.23 improved the compatibility when defeated, which should fix the spamming error.
Meanwhile the HVUT error is likely caused by an unresponsive fetch, which is usually due to a network issue.

JKU533 · 2026-06-26T12:38:50Z

2.91.22 应该正常了
因为 2.91.22 把原来判断里的 没有 EtherTap 或只剩 1 turn 给去掉了，想着可以自行配置，但是忘了会导致没配置条件时一直用法杖物理攻击有CM的目标

次要攻击勾选某个攻击模式后，还是会一直用法杖平A

WayneFerdon · 2026-06-26T12:59:04Z

2.91.22 应该正常了
因为 2.91.22 把原来判断里的 没有 EtherTap 或只剩 1 turn 给去掉了，想着可以自行配置，但是忘了会导致没配置条件时一直用法杖物理攻击有CM的目标

次要攻击勾选某个攻击模式后，还是会一直用法杖平A

@JKU533 那可能是条件判定出了问题
看下现在的配置是什么样的?
可以公式前面加个@看看log输出的参数正不正常

JKU533 · 2026-06-26T13:10:53Z

那可能是条件判定出了问题看下现在的配置是什么样的? 可以公式前面加个@看看log输出的参数正不正常

根本没公式...我现在用的是遭遇战配置非常干净
我试过选其他的次要攻击模式都是法杖平A，不论有次要攻击有没有条件

折叠配置

{"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}

WayneFerdon · 2026-06-26T13:41:53Z

@JKU533 2.91.24应该好了（

原因是新的功能 先尝试完所有模式的高阶魔法技能再继续中阶和低阶 未开启时tier = undefined，遍历开头的tier--会导致传入实际尝试攻击时的tier是NaN（预期应该是undefined），导致判断出了问题（

lukasva77 · 2026-06-28T13:39:35Z

Firefox + Violentmonkey

HVAA has a slight lag now well I noticed it a couple of weeks back
most noticable with HVUtils cause the transition of ui is clearly visible turning off HVUtils makes it better but still the same lag for the HVAA config button and random encounter timer

only console message from HVAA is from log happens on every click of HV menus

skip arena check [HV]AutoAttack.user.js:4241:17

lukasva77 · 2026-06-28T13:42:09Z

@lukasva77

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 Battle (for every 300ms), yet the window keeps failing by unknown reason (perhaps something is causing some element missing), meanwhile the same error is likely misleading the hvAA to wait for a Battle, yet the battle should not be waited for since it is already defeated.

I have been clicking around with console and figured the red messages are from the equipment screen I guess It's the bottom bar that was there before It's missing for me after HVUtils updates

EDIT or maybe not that feature got removed from HVUtils

lukasva77 · 2026-07-01T09:14:02Z

A new message in logs appears sometimes

onBattle clean onriddle [HV]AutoAttack.user.js:1161:17

WayneFerdon · 2026-07-01T10:44:45Z

A new message in logs appears sometimes

onBattle clean onriddle [HV]AutoAttack.user.js:1161:17

@lukasva77 It's just a normal debug notification. No worry.

…075428)

WayneFerdon mentioned this pull request Aug 21, 2025

修复技能可释放判断及其他技能技能排序无效问题 #154

Closed

WayneFerdon mentioned this pull request Sep 5, 2025

HV Auto attack 遇到BUG #157

Open

This was referenced Oct 20, 2025

HVAA 更新后的奇怪bug #159

Closed

HV Auto attack 使用雷法模式不会放陷危/ In Elec mage mode doesn't cast Imperil #160

Open

WayneFerdon mentioned this pull request Oct 25, 2025

HVAA 无法自动继续新回合 #161

Closed

2.91.23 Compatibility improvement for defeated return.

50982a7

2.91.24 修复attack流程

e48c19d

WayneFerdon added 6 commits June 26, 2026 23:55

fix UI

d85d2f6

2.91.25 refactor encounter logic

2697240

2.91.26 Try fix dodying#198

c207810

2.91.27

8b8f534

Update README_en.md

48570ce

Update README.md

4f37656

WayneFerdon added 10 commits June 28, 2026 22:27

2.91.28

5ca24b4

Update hvAutoAttack.user.js

beb56b7

UI optimization

40f140b

2.91.29 支持检查消耗品是否已装备

7c318a1

2.91.30 增加装备槽位检查

d391781

2.91.31 fix idle arena option loading

84d7f93

Update hvAutoAttack.user.js

ccbcb79

2.91.32 Use unified splitOrder

5194856

Update hvAutoAttack.user.js

d04a9fd

2.91.33 fix idle arena matching

3b529e6

WayneFerdon added 3 commits July 5, 2026 16:59

2.91.34 Compatibility improvement for window.open

486e9aa

2.91.35 fix the missing of [E!] (dodying/issues/198#issuecomment-4887…

4dcfc7f

…075428)

2.91.36

0c4bacd

Uh oh!

Conversation

WayneFerdon commented Aug 21, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Qiyue0515 commented Sep 5, 2025

Uh oh!

WayneFerdon commented Sep 5, 2025

Uh oh!

DreamSeeker08 commented Oct 21, 2025

Uh oh!

Kotone-Hikaru commented Oct 22, 2025

Uh oh!

WayneFerdon commented Oct 22, 2025

Uh oh!

Kotone-Hikaru commented Oct 23, 2025

Uh oh!

WayneFerdon commented Oct 23, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Kotone-Hikaru commented Oct 23, 2025

Uh oh!

Kotone-Hikaru commented Oct 23, 2025

Uh oh!

WayneFerdon commented Oct 23, 2025

Uh oh!

Kotone-Hikaru commented Oct 23, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

WayneFerdon commented Oct 23, 2025

Uh oh!

Kotone-Hikaru commented Oct 24, 2025

Uh oh!

WayneFerdon commented Oct 24, 2025

Uh oh!

Kotone-Hikaru commented Oct 25, 2025

Uh oh!

Kotone-Hikaru commented Oct 25, 2025

Uh oh!

WayneFerdon commented Oct 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Kotone-Hikaru commented Oct 25, 2025

Uh oh!

Kotone-Hikaru commented Oct 25, 2025

Uh oh!

WayneFerdon commented Oct 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Kotone-Hikaru commented Oct 25, 2025

Uh oh!

Kotone-Hikaru commented Oct 27, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

WayneFerdon commented Oct 27, 2025

Uh oh!

Kotone-Hikaru commented Oct 27, 2025

Uh oh!

Kotone-Hikaru commented Oct 27, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

WayneFerdon commented Jun 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

JKU533 commented Jun 26, 2026

Uh oh!

WayneFerdon commented Jun 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

JKU533 commented Jun 26, 2026

Uh oh!

WayneFerdon commented Jun 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

lukasva77 commented Jun 28, 2026

Uh oh!

lukasva77 commented Jun 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

lukasva77 commented Jul 1, 2026

WayneFerdon commented Aug 21, 2025 •

edited

Loading

WayneFerdon commented Oct 23, 2025 •

edited

Loading

Kotone-Hikaru commented Oct 23, 2025 •

edited

Loading

WayneFerdon commented Oct 25, 2025 •

edited

Loading

WayneFerdon commented Oct 25, 2025 •

edited

Loading

Kotone-Hikaru commented Oct 27, 2025 •

edited

Loading

Kotone-Hikaru commented Oct 27, 2025 •

edited

Loading

WayneFerdon commented Jun 26, 2026 •

edited

Loading

WayneFerdon commented Jun 26, 2026 •

edited

Loading

WayneFerdon commented Jun 26, 2026 •

edited

Loading

lukasva77 commented Jun 28, 2026 •

edited

Loading