LixAssistantLimbusCompany
LixAssistantLimbusCompany copied to clipboard
【新版本预告/Flag】LALC 2.2.0 / [New Release Preview/Flag] LALC 2.2.0
中文版本
众所周知,要做的事立为 Flag ,做的应该就快很多。而且以往很多同学都会发个“求更新”的帖子,干脆就把更新内容和更新进度放在这里,有意见或想催更的同学也可在下面盖楼:)
温馨提示
该预告的发布不意味着下个版本就是 2.2.0 :)
下面是 LALC 2.2.0 很可能(1000%)具备的特性
- [ ] 更整洁,更便于开发的 GUI
- [ ] 实现图形化操作 队伍人员顺序
- [ ] 实装饰品倾向,将影响一些任务的饰品选择、购买、刷新
- [ ] 任务执行逻辑重构,借鉴 MAA 任务执行流程
- [ ] 镜牢卡包的选择,趋吉避凶
- [ ] 放烧屏设置(可定时移动)自己最小化
- [ ] 可记录多个数字配置并调用,默认恢复上次使用设置
- [ ] 可在任务执行结束后关机/重启/关闭游戏和 LALC
- [ ] LALC star 达到 321 这个条件应该可以拖延足够的时间:)
- [ ] ……
估计有的同学看完该 Issue 连忙问:队伍轮换呢?根据陆爻齐目前的体验,星光溢出 5000,根本不需要啊,找个菜刀队迅速解决就行:)
嘛,届时看看镜五再说罢
English Ver translated by deepl(probably not update as soon as Chinese Version above)
As we all know, if you set a Flag for something you want to do, you should be able to do it much faster. In the past, many of you would post a ‘request for update’ thread, so I'll just put the update content and progress here, and if you have any comments or want to push for an update, you can also put your comments in the following :)
Note
The release of this preview does not imply that the next version will be 2.2.0.)
Here are the features that LALC 2.2.0 will most likely (1000%) have
- [ ] A cleaner, more developer-friendly GUI.
- [ ] Implementation of graphical operation of team personnel order
- [ ] Actual trinket tendency, which will affect the trinket selection, purchase and refresh of some tasks.
- [ ] Task execution logic refactoring, borrowing from MAA task execution process.
- [ ] Selection of Mirror Prison card packs, to avoid bad luck.
- [ ] Put the burning screen settings (can be moved regularly) to minimise themselves
- [ ] Record multiple digital configurations and recall them, and restore the last used settings by default.
- [ ] Shutdown/Restart/Shutdown game and LALC at the end of a mission.
- [ ] LALC star reaches 321 which should stall it long enough :)
- [ ] ......
Some of you may have read the Issue and asked: what about team rotation? According to Lu Yaoqi's experience so far, the starlight overflow of 5000 is not needed at all, just find a chopper team to solve it quickly:) maybe will be considered in Mirror5?