Dear tool developer,
Each userscript and addon/extension have to include the oGameVersionCheck to show users all installed OGame scripts and if they are tested with the current Ogame version or not.
See news ... for more details
Include:
- Add to your metadata block: (for Firefox with GM/Scriptish and Chrome with TM)
- Or include the minified code (see appended ZIP file) to your script when you want to support Chrome without TM or Opera.
- Or use jQuery getScript to load and run the version check from Ogame server
- Or create your own function with same behavoir.
Usage:
- Call oGameVersionCheck(scriptName, testedOgameVersion, scriptUrl) at the beginning of your script
- document.readyState must be 'interactive' or 'complete' - you have to care about it in extensions or when you use @run-at document-start in userscripts
- scriptName: name of your script / addon
- testedOgameVersion: current Ogame version , e.g 5.1.0
- scriptUrl: URL to your script page, e.g on userscripts.org
Regards, Francolino
Each userscript and addon/extension have to include the oGameVersionCheck to show users all installed OGame scripts and if they are tested with the current Ogame version or not.
See news ... for more details
Include:
- Add to your metadata block: (for Firefox with GM/Scriptish and Chrome with TM)
- Or include the minified code (see appended ZIP file) to your script when you want to support Chrome without TM or Opera.
- Or use jQuery getScript to load and run the version check from Ogame server
- Or create your own function with same behavoir.
Usage:
- Call oGameVersionCheck(scriptName, testedOgameVersion, scriptUrl) at the beginning of your script
- document.readyState must be 'interactive' or 'complete' - you have to care about it in extensions or when you use @run-at document-start in userscripts
- scriptName: name of your script / addon
- testedOgameVersion: current Ogame version , e.g 5.1.0
- scriptUrl: URL to your script page, e.g on userscripts.org
Regards, Francolino