BeamNG.Earth
A 1:1 scale streamed Earth for BeamNG.drive: real elevation and satellite imagery, floating origin, LOD streaming from a companion server
翻譯準備中
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證A native compatibility implementation for the MS-DOS game Battle Isle and its data disks.
翻譯準備中
取自儲存庫 README
正在載入完整 README。 以下為已儲存的摘錄。
Battle Isle (DOS) taken apart, with the aim of a native compatibility
implementation requiring an installed copy of the original game: our
own C code, which runs the game with the data of the player's GOG
release. See PROVENANCE.md.
1. Source from the programs (src/*.hints): doskit/tools/build.py
makes each program's assembly source from the player's copy and
checks that it assembles back to the same bytes.
2. Understanding: names, structures and rules in the hints, checked
by runs of the original (doskit/tools/run.py).
3. The port (port/): C on doskit's runtime.檢視完整 README ↗Battle Isle (DOS) taken apart, with the aim of a native compatibility implementation requiring an installed copy of the original game: our own C code, which runs the game with the data of the player's GOG release. See PROVENANCE.md.
src/*.hints): doskit/tools/build.py
makes each program's assembly source from the player's copy and
checks that it assembles back to the same bytes.doskit/tools/run.py).port/): C on doskit's runtime.No game files go into this repository, and no bytes of them.
git submodule update --init # doskit
git config core.hooksPath hooks # once per clone
python3 doskit/tools/isox.py /path/to/game.gog # -> game/
python3 doskit/tools/build.py src/NAME.hints
python3 doskit/tools/check.py
sh port/build.sh # port\build.bat on Windows
Python 3 with capstone (pip install capstone).
src/*.hints: what is known about each program.tools/NAMEfiles.py: a tool for each data format (tpwmfiles.py: the
packed files; palfiles.py: the palettes; ifffiles.py: the
pictures; libfiles.py: the graphics libraries; mapfiles.py: the
maps and their overviews; datfiles.py: the tables of unit types,
ground, maps' codes and AMOK.DAT; txtfiles.py: the texts and the
small font; sndfiles.py: the songs and the sound effects, played
again into the AdLib's registers and compared with a run's;
screens.py: the game's screens drawn from a run's memory
and compared with its video memory), and for the rules: fight.py
(a fight's outcome), scene.py (the fight scene, a pass at a time:
its values and its picture), moves.py (where a unit can move and
fire, the path it takes), turn.py (a move carried out, the change of
phase, a map's end) and computer.py (the computer player's
assessment, plan and commands, and the keys it carries them out
with), each done again from a run's memory and compared with what the
game made of it.port/: the implementation in C (its README says how far it is).docs/HANDOFF.md: state, what was learned, what is next.AGENTS.md: the rules for working on this; PROVENANCE.md: where the
code comes from.doskit/: the tools and the runtime (a git submodule).