Unity il2cpp type_info_definition_table regression
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 13
- Forks
- 16
- Avg merge
- 16d 9h
- Merged PRs (30d)
- 15
Description
# Issue
There has been a couple of reports that the update to the `type_info_definition_table` address sigscan behaviour has regressed and no longer works in certain cases.
https://github.com/LiveSplit/asr/blob/master/src/game_engine/unity/il2cpp/mod.rs#L63-L89
## Known Games affected
- Sea of Stars (2021.3 LTS)
## Other games with invalid definitions (old doesnt fix)
- GRIME II (unity 6)
---
Making this issue as a reminder to work on a reproduction case and potentially some fallback behaviour using the old (potentially slower?) method if an address cannot be resolved using the new method.
I'm assuming the new method was introduced to solve a specific case, would be curious as to what game that was @Jujstme
It could be a matter of testing more games with the newer method to resolve the issue.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading src/game_engine/unity/il2cpp/mod.rs lines 63-89 and reproduce the type_info_definition_table address sigscan behavior with Sea of Stars or GRIME II. Compare the newer method with the old method when definitions cannot be resolved; done means the affected cases work with an agreed fallback or the regression is otherwise resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, unity
- Domain
- game-dev, reverse-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100