https://github.com/alexknauth/asr-unity-mono-offsets-tool

A tool for finding which Unity / Mono offsets work and which don't work
https://github.com/alexknauth/asr-unity-mono-offsets-tool

Last synced: about 1 month ago
JSON representation

A tool for finding which Unity / Mono offsets work and which don't work

• Host: GitHub
• URL: https://github.com/alexknauth/asr-unity-mono-offsets-tool
• Owner: AlexKnauth
• License: mit
• Created: 2023-11-03T02:32:27.000Z (about 1 year ago)
• Default Branch: master
• Last Pushed: 2024-05-16T02:43:45.000Z (8 months ago)
• Last Synced: 2024-10-16T02:55:10.667Z (3 months ago)
• Language: Rust
• Size: 92.8 KB
• Stars: 1
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE.txt

Awesome Lists containing this project

README

        
# asr-unity-mono-offsets-tool

A tool for finding which Unity / Mono offsets work and which don't work.

## Compilation

This auto splitter is written in Rust. In order to compile it, you need to

install the Rust compiler: [Install Rust](https://www.rust-lang.org/tools/install).

Afterwards install the WebAssembly target:

```sh

rustup target add wasm32-wasi --toolchain stable

```

The auto splitter can now be compiled:

```sh

cargo release

```

The auto splitter is then available at:

```

target/wasm32-wasi/release/asr_unity_mono_offsets_tool.wasm

```

Make sure too look into the [API documentation](https://livesplit.org/asr/asr/) for the `asr` crate.

## Development

You can use the [debugger](https://github.com/LiveSplit/asr-debugger) while

developing the auto splitter to more easily see the log messages, statistics,

dump memory, step through the code and more.

The repository comes with preconfigured Visual Studio Code tasks. During

development it is recommended to use the `Debug Auto Splitter` launch action to

run the `asr-debugger`. You need to install the `CodeLLDB` extension to run it.

You can then use the `Build Auto Splitter (Debug)` task to manually build the

auto splitter. This will automatically hot reload the auto splitter in the

`asr-debugger`.

Alternatively you can install the [`cargo

watch`](https://github.com/watchexec/cargo-watch?tab=readme-ov-file#install)

subcommand and run the `Watch Auto Splitter` task for it to automatically build

when you save your changes.

The debugger is able to step through the code. You can set breakpoints in VSCode

and it should stop there when the breakpoint is hit. Inspecting variables may

not work all the time.