当前时间: 2026-05-31 05:01:46
分类:办公文件
评论(0)
点名竞技场恶钢vs银武士,高伤害逻辑说明这场战斗的关键是上来就先闷头怼个SP3,激活持续时间长的且不可提前终止的铁之光环。然后打个SP1封锁住对手的SP使用,接下来就无脑平A三四连后撤再前冲,循环N次,你会发现涨狂怒很快。到3格能后,放3,再接SP1封SP,再无脑连环平A。等到第三次SP3,第三轮光环下打完,狂怒基本上就已经叠到99层了。后续是SP3+SP1+SP2循环。有人可能问,中间能不能不放SP1封技能。我感觉是可以的,但是放了之后封了技能,你拦截技术又过关的话,攒狂怒会很效率。放SP1唯一影响就是进入下一个SP3速度会稍微慢一点点。而不放的话,如果你压不好格挡,你可能会需要引几次技能对面技能,这样其实反而也浪费时间,拖节奏了。2、SP3后平A务必中结尾,尤其是把对手打到满3格能的位置。只要你中结尾,就会消能,他就不会满3格,可以放心继续平A;3、SP3后,没有用SP1封对手技能之前,在对手快满3格能的时候,别傻兮兮的去推格挡,SP3后,双方都有通能被动,涨能比较快,不小心把对手推上3格,后面勇猛叠高了,会秒人的;1、只有SP3之后激活的铁之光环不会被提前终止,而前面中击引发了冲击,你重击会消耗冲击转为铁之光环,这个光环在下一次引发冲击时会被立即消耗掉的;2、SP3之后,会大幅增加暴击值,这样平A就会更频繁的引发立即冲击(也就是不仅中击会引发冲击效果,轻击也有),而只要有这个效果,且在光环下,那么就会能量燃烧对手。这一系列的逻辑有点套娃的味道,不仔细观察真的会有点费解。这也是为什么SP3后,叠狂怒飞快的主要原因(这个战斗的节点是只要被能量消耗或燃烧,就会涨被动狂怒);
基本
文件
流程
错误
SQL
调试
- 请求信息 : 2026-05-31 05:05:12 HTTP/1.1 GET : https://www.yeyulingfeng.com/a/687056.html
- 运行时间 : 0.116532s [ 吞吐率:8.58req/s ] 内存消耗:4,676.88kb 文件加载:145
- 缓存信息 : 0 reads,0 writes
- 会话信息 : SESSION_ID=a9bb43cfa42327e01b492605b3ceeaef
- CONNECT:[ UseTime:0.000511s ] mysql:host=127.0.0.1;port=3306;dbname=wenku;charset=utf8mb4
- SHOW FULL COLUMNS FROM `fenlei` [ RunTime:0.000810s ]
- SELECT * FROM `fenlei` WHERE `fid` = 0 [ RunTime:0.000335s ]
- SELECT * FROM `fenlei` WHERE `fid` = 63 [ RunTime:0.000270s ]
- SHOW FULL COLUMNS FROM `set` [ RunTime:0.000494s ]
- SELECT * FROM `set` [ RunTime:0.000184s ]
- SHOW FULL COLUMNS FROM `article` [ RunTime:0.000607s ]
- SELECT * FROM `article` WHERE `id` = 687056 LIMIT 1 [ RunTime:0.000445s ]
- UPDATE `article` SET `lasttime` = 1780175112 WHERE `id` = 687056 [ RunTime:0.010869s ]
- SELECT * FROM `fenlei` WHERE `id` = 64 LIMIT 1 [ RunTime:0.000293s ]
- SELECT * FROM `article` WHERE `id` < 687056 ORDER BY `id` DESC LIMIT 1 [ RunTime:0.000564s ]
- SELECT * FROM `article` WHERE `id` > 687056 ORDER BY `id` ASC LIMIT 1 [ RunTime:0.004771s ]
- SELECT * FROM `article` WHERE `id` < 687056 ORDER BY `id` DESC LIMIT 10 [ RunTime:0.001520s ]
- SELECT * FROM `article` WHERE `id` < 687056 ORDER BY `id` DESC LIMIT 10,10 [ RunTime:0.001218s ]
- SELECT * FROM `article` WHERE `id` < 687056 ORDER BY `id` DESC LIMIT 20,10 [ RunTime:0.000707s ]
0.120581s