Both Opera GX Mods and documentation are still actively developed.
Mod_Template is created to give you a quick start into creating mods. It showcases all capabilities and is a convenient starting point to create own mods. Load it in Opera GX, look around, modify things and have fun.
Each mod consists of
- manifest.json - defines what's included in mod as well as name, author, version etc.
- resources - sounds, images, videos, css, shaders etc.
See manifest.json from Mod_Template. It should be self explanatory. In case you make a mistake, Opera GX will show you an error when trying to load such a mod.
Opera GX uses vertical remixing to achive dynamic music in browser. However it doesn't mean you need to provide multiple music files. If only one is provided it will work as well. In such a case you can do a little trick and list the same file more than once. This will result in an increased volume when users is active in browser.
You can provide a single sound for a key or a list of sounds that will be played in provided order. You can keep keys empty which means that no sound will be played or remove key and in that case default sound will be played.
The same rules apply as in keyboard sounds.
Provide light and dark version. Mods can't block users from switching between light and dark mode.
Provide both light and dark version. Mods can't block users from switching between light and dark mode.
More than one shader can be provided in single mod. Read more about shaders.
Those are basically CSSes that can be applied to web pages. Multiple pages can be modified with a single mod. Opera GX exposes primary and secondary color if you want to make web pages follow UI colors (see opera.css)
Random order.
- Limit size of resoures.
- Music and sounds should follow volume from Mod_Template otherwise it won't be a good experience for users.
- Keep resources in dedicated subdirectories.
- Use 512x512 good looking image for icon.