Please open your text/code editor of choice to your tweak folder.
.
├── Makefile
├── Tweak.x
├── control
└── testtweak.plist
This is what your file structure in the folder should look like. The .plist file may have a different name depending on the tweak name you chose, but the rest should be the same. Let’s take a deeper dive into what each file is.
MakefileThis file essentially has information regarding the build protocol. TARGET, for example, contains the target operating system that you can choose. Another example would be ARCHS which have a dozen or so values you can choose from, but you will most likely use arm64, (every iPhone before the Xs series and after iOS 6) and arm64e, (every iPhone after and including the Xs series).
ARCHS would be written like this: ARCHS = arm64 arm64e
Tweak.xThis file is the most “important” out of these four. This is where you write all your code. This code will be written in a language called Objective-C, however you could use Orion to utilize Swift instead. This is a separate template called tweak_swift instead of tweak.
controlThis file contains the information about your tweak. Things like the name of the developer, what iOS version it supports, etc. Some DPKG managers display bits and pieces of it when the user looks at the tweak depiction.
testtweak.plistThis file contains what the tweak will be hooking/injecting into. This won’t be touched much, compared to the other files, but it does exist and is also important.
More information about this file can be found at The Apple Wiki. Knowing the various uses of filters can be very beneficial if you want to hook several classes throughout iOS without injecting into com.apple.UIKit, for instance.