This guide will walk through how to decompile/reverse engineer IL2CPP games for modding usage.
Note: expect this entire process to take upwards of an hour. Have something ready to do on the side while waiting for processing to finish.
| // Maintains a renamed copy of certain Unity Resources asset files in your project. | |
| // E.g. by default Unity won't include SVG files as XML for further processing. | |
| // | |
| // Put this file in the Assets/Editor folder. | |
| // | |
| // This script automatically rename resource files with a .txt (text) or .bytes (binary) extension, | |
| // to be readable as Resources.Load<TextAssets>(path).text or Resources.Load(path) as byte[]. | |
| // | |
| // | |
| // License: CC0 |
This isn't a guide about locking down homebrew so that it can't touch the rest of your system security-wise.
This guide doesn't fix the inherent security issues of a package management system that will literally yell at you if you try to do something about "huh, maybe it's not great my executables are writeable by my account without requiring authorization first".
But it absolutely is a guide about shoving it into its own little corner so that you can take it or leave it as you see fit, instead of just letting the project do what it likes like completely taking over permissions and ownership of a directory that might be in use by other software on your Mac and stomping all over their contents.
By following this guide you will:
sudo to forcefully change permissions of some directory to be owned by your account
| func scrollViewDidScroll(_ scrollView: UIScrollView) { | |
| for (i, view) in scrollView.subviews.enumerated() { | |
| var ty = 0.0 | |
| if scrollView.contentOffset.y < 0 { | |
| // We're scrolling past the top of the scroll view. | |
| // Translate each item in the scroll view by some amount based on its index and scroll offset. | |
| ty = CGFloat(i) * abs(offsetY) / 8.0 * pow(1.12, CGFloat(i)) | |
| } | |
| view.transform = CGAffineTransform(translationX: 0, y: ty) | |
| } |
| #!/bin/zsh | |
| makeXCFramework () { | |
| BASEDIR=$(pwd) | |
| echo "Script location: ${BASEDIR}" | |
| LIBNAME=$(basename $BASEDIR) | |
| echo "lib is: $LIBNAME" | |
| cd Frameworks |
The libdispatch is one of the most misused API due to the way it was presented to us when it was introduced and for many years after that, and due to the confusing documentation and API. This page is a compilation of important things to know if you're going to use this library. Many references are available at the end of this document pointing to comments from Apple's very own libdispatch maintainer (Pierre Habouzit).
My take-aways are:
You should create very few, long-lived, well-defined queues. These queues should be seen as execution contexts in your program (gui, background work, ...) that benefit from executing in parallel. An important thing to note is that if these queues are all active at once, you will get as many threads running. In most apps, you probably do not need to create more than 3 or 4 queues.
Go serial first, and as you find performance bottle necks, measure why, and if concurrency helps, apply with care, always validating under system pressure. Reuse
| extension JSONDecoder { | |
| func decode<T: Decodable>(_ type: T.Type, from data: Data, keyedBy key: String?) throws -> T { | |
| if let key = key { | |
| // Pass the top level key to the decoder. | |
| userInfo[.jsonDecoderRootKeyName] = key | |
| let root = try decode(DecodableRoot<T>.self, from: data) | |
| return root.value | |
| } else { |
| iOS Create a Carthage Supported Framework | |
| #iOSBySheldon | |
| A little bit Background of Carthage: | |
| - Carthage works like Cocoapods, but a little bit simpler. | |
| * When creating a Cocoapods supported framework need a .podspec file to do some config, which is not required by Carthage. | |
| * When using a Cocoapods supported framework, a workspace file will be automatically created, the umbrella header will be setup in a pod project inside workspace. It feels simple, but the whole process creates a lot files including a "giant" workspace. | |
| * When using a Carthage supported framework, it will just download the framework, and its dependencies if any, to a folder. All we need to do is to drag and drop it to the binary linking section in the project build setting tab, for the first time. It sounds complicated but it makes the project clean. | |
| - Carthage is written in Swift. | |
| - Carthage internally uses `-xcodebuild` to build dependency. |
Author: Chris Lattner
