resnametable.txt: Difference between revisions
Jump to navigation
Jump to search
Created page with "This file describes aliases for the same location. For example, there are five locations in Nubozone - new_'''1'''-1.rsw, new_'''2'''-1.rsw, new_'''3'''-1.rsw, new_'''4'''-1.rsw, new_'''5'''-1.rsw, which look the same and are actually the same location - '''new_zone01.rsw'''. In this case, you should specify aliases: new_1-1.rsw#new_zone01.rsw# new_2-1.rsw#new_zone01.rsw# new_3-1.rsw#new_zone01.rsw# new_4-1.rsw#new_zone01.rsw# new_5-1.rsw#new_zone01.rsw# If a pri..." |
(No difference)
|
Latest revision as of 13:22, 25 May 2025
This file describes aliases for the same location.
For example, there are five locations in Nubozone - new_1-1.rsw, new_2-1.rsw, new_3-1.rsw, new_4-1.rsw, new_5-1.rsw, which look the same and are actually the same location - new_zone01.rsw. In this case, you should specify aliases:
new_1-1.rsw#new_zone01.rsw# new_2-1.rsw#new_zone01.rsw# new_3-1.rsw#new_zone01.rsw# new_4-1.rsw#new_zone01.rsw# new_5-1.rsw#new_zone01.rsw#
If a private server uses a custom location, it can be extracted from the client and converted to a .fld file. If this custom location is known by several names, then you should also extract the resnametable.txt file, otherwise OpenKore will complain about missing .fld files.
Example: Cannot load field y_airport: No corresponding field file found for field 'y_airport'.