This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
en:orx:config:encryption [2010/05/11 20:50 (14 years ago)] – iarwain | en:orx:config:encryption [2024/03/11 14:47 (6 weeks ago)] (current) – crypted.ini -> encrypted.ini iarwain | ||
---|---|---|---|
Line 20: | Line 20: | ||
; Finally we include the file containing all the settings that we don't want to end user to mess up with | ; Finally we include the file containing all the settings that we don't want to end user to mess up with | ||
; If the end-user did provide values for them, they' | ; If the end-user did provide values for them, they' | ||
- | @crypted.ini@</ | + | @encrypted.ini@</ |
In the same way, we can add included files for customized inputs, for example. We would add it just after the inclusion of config.ini.\\ | In the same way, we can add included files for customized inputs, for example. We would add it just after the inclusion of config.ini.\\ | ||
Line 40: | Line 40: | ||
; Non-overridable config stuff (ie. everything else) | ; Non-overridable config stuff (ie. everything else) | ||
- | @crypted.ini@</ | + | @encrypted.ini@</ |
And, of course, you might not want the end-user to mess up with this file, so we now need to encrypt it when releasing our game. | And, of course, you might not want the end-user to mess up with this file, so we now need to encrypt it when releasing our game. | ||
Line 55: | Line 55: | ||
<code c> | <code c> | ||
- | Of course, as orx will load its main config file it is initialized, | + | Of course, as orx will load its main config file **when** |
<code c>int main(int argc, char **argv) | <code c>int main(int argc, char **argv) |