!include: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
; !include [<filename>] | |||
: Use this option to include different files as part of [[config.txt]]. That makes it easier to reuse configurations. | |||
:'''''Note'''. You can use a path that is relative to config.txt.'' | |||
Example: | |||
!include account.txt | |||
!include skills/hunterselfskills.txt | |||
:In the example above, if your config.txt is placed in the folder is "C:\Openkore\control", the files "C:\Openkore\control\account.txt" and "C:\Openkore\control\skills\hunterselfskills.txt" will be included as part of your configuration. | |||
:'''Known Limitation'''. Multiple block configurations are screwed if you specify blocks of the same type (say, attackSkillSlot) inside different files. While this is not yet fixed, it is recommended to place each type of configuration blocks in one file only. | |||
[[Category:config.txt]] | |||
Revision as of 13:41, 20 November 2009
- !include [<filename>]
- Use this option to include different files as part of config.txt. That makes it easier to reuse configurations.
- Note. You can use a path that is relative to config.txt.
Example: !include account.txt !include skills/hunterselfskills.txt
- In the example above, if your config.txt is placed in the folder is "C:\Openkore\control", the files "C:\Openkore\control\account.txt" and "C:\Openkore\control\skills\hunterselfskills.txt" will be included as part of your configuration.
- Known Limitation. Multiple block configurations are screwed if you specify blocks of the same type (say, attackSkillSlot) inside different files. While this is not yet fixed, it is recommended to place each type of configuration blocks in one file only.