Leaderboard

View File BadCase's Il2Cpp Edits By Name This script allows users to create Il2Cpp edits by method name, this means no offsets are needed. As long as method names are not changed in the game the edits will continue working even after a game updates. Create Edit Here you will enter a known method name or search for a method name and create an edit for it. Edits you create for a game are added to the main menu above this menu item. Import Edits Here you can import edits created and exported by other users of this script. Export Edits Here you can export edits you have created to share them with other users of the script. Delete Edit Here you can delete edits for a game and remove them from the main menu. Submitter BadCase Submitted 02/01/2022 Category Tools  

are you rooted? if so, scrap the VM's and set to 'SElinux' in the 'fix it' section once everything is properly installed natively in the device. if your not rooted: i can't really help, i'd not own a device i couldn't root (even my old lollipop LG VK815 is rooted and that was a pain in the a** to do way back when). IN THE EVENT that you set it to work with SElinux (in a fully rooted device running android 10, 11, and/or 12) and still encounter crashes or problems, please be sure to upload the logcat file, crash log, and any helpful details of exactly what you where doing at the point of the crash, as the users that will tackle the problem will also try to reproduce the same error if possible on similar hardware should it be available to them.

Read: http://www.catb.org/~esr/faqs/smart-questions.html 1. The title of the topic is "help me" and others like that. Indicate a clear reason. With such titles, you can not wait for help. 2. The wording “how to fix it?”, And then the screen or code. Or “help fix the error” and then two pages of code. No one will guess what mistake, where, how or what. Do not specify specifically - do not receive help. If after a quick reading of the question it is impossible to understand the essence of the question, then no one will ask you many suggestive questions. This is for you, not the one who answers. 3. Ask what is written in help. Before asking a question, carefully read the help, and also carefully study all the messages that you receive. It is quite possible that the answer is in these messages, or in the help. 4. The code is not formatted. When the code is not formatted (there are no line breaks and indentation) it is difficult to work with it and it is difficult to notice an error. Edit the post and format the code by adding line feeds and indentation. Perhaps after that you yourself will see where the error is.