ultratears
Unofficial native Windows port of Tears of the Kingdom 1.4.3 using static recompilation. Builds locally from the player's own extracted game dump; no game files included.
翻译准备中
尚未检测到更新。GitHub 发布版本后会显示在这里。
个人 GitHub 账号下公开仓库的所有者可以登录并验证所有权,自行管理介绍,无需管理员批准。
登录并生成验证文件,在 30 分钟内将其提交到此仓库的默认分支。其他分支或分叉仓库中的文件无效。然后在下方检查文件,即可无需管理员批准直接管理项目。请保留文件以维持管理权限。
如需登录,将前往登录页面。登录后请回到此处,再次点击所选的验证按钮。
在项目文件夹中运行 /nomorevibe verify,即可验证所有权并自行管理介绍。
一分钟完成验证制作者的介绍仅有上面的一句话。 更多详情请阅读仓库 README。 仓库 README ↗
正在加载完整 README。
查看完整 README ↗The site is a static page: it runs this repo's simulator directly in the
browser under Pyodide, with no packages to install on load. stlite.html is
the previous Streamlit-in-the-browser build, kept for the pages the static one
does not cover yet (Mana Generation). Both fetch the same .py files from this
repo, so neither can drift from the simulator the tests exercise.
This is a simulator for Teamfight Tactics. The intent of this project is to develop a way to mathematically determine the value that different items, buffs, augments, anomalies provide to different units in TFT, allowing the user to make more educated decisions during the game.
The sidebar allows you to configure the base settings, and the user can then plot the marginal DPS increase of adding an extra item / buff / augment / anomaly.
Double-click run_app.bat. That is the whole thing.
On the first launch it creates the virtual environment (.venv) and installs
everything; after that it goes straight to starting the app. It also notices
when requirements.txt changes and reinstalls on its own, so you never have
to remember to. The TFT Simulator then opens in your browser.
Double-click setup.bat instead. It does everything above, plus installs the
development extras (pytest, matplotlib) and runs the test suite. After that:
.venv\Scripts\python -m pytest
If you prefer to run commands manually:
Create a virtual environment and install dependencies:
py -3.12 -m venv .venv
.venv\Scripts\python -m pip install -r requirements.txt
Add -r requirements-dev.txt instead if you want the test tooling too.
Run the Streamlit app:
.venv\Scripts\python -m streamlit run app.py
Then navigate to the 'ChampionSelector' page in the app.
The site at the repo root is plain HTML/JS and fetches its Python sources over
HTTP, so it needs a server rather than opening index.html from disk.
Double-click serve.bat. It starts the server and opens the page. Nothing
to install first — serve.py is standard library only, and the site runs the
simulator under Pyodide in the browser, so none of requirements.txt is
involved.
serve.bat REM http://127.0.0.1:8618/
serve.bat 9000 REM a different port
serve.bat 9000 nb REM don't open a browser
It refuses to start when that port already has a server, which matters more than it sounds: Windows would otherwise let the second one share the port, leaving two servers splitting the requests between them: exactly the sort of half-stale page the next paragraph is about.
Or run it yourself:
.venv\Scripts\python serve.py
Then open http://127.0.0.1:8618/. Use this rather than
python -m http.server: that one sends no Cache-Control, so browsers invent
their own expiry and keep serving the files they already have — an edit to a
.py file then doesn't show up no matter how many times you reload or restart
the server, because the browser never asks. serve.py says "revalidate",
which costs a 304 per file and nothing else.