From 50f21014e56920997dcd0c09b8320f9762eebe8f Mon Sep 17 00:00:00 2001 From: Ian C Date: Mon, 19 Sep 2016 09:46:34 +0000 Subject: Added new string:number format to help with non-character code following mappings. --- README | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) (limited to 'README') diff --git a/README b/README index 05582aa..a53c089 100644 --- a/README +++ b/README @@ -24,11 +24,12 @@ Input files look like the following: #:1 *:128 !63 +0123456789ABCDEF:2 ~ ######## # # #ABCDEF# -#1# # *# +#0#1# *# ######## The "#:1" line defines that when a '#' character appears in the map then code @@ -40,14 +41,18 @@ character code. In ASCII this would mean 'A' becomes 2, 'B' becomes 3, and so on. Any codes generated that fall outside the range 0 to 255 will be clamped to that range. -The line with a tilde (~) on its own indicates the end of the definitions. By -default, unless redefined, space is automatically defined to be code zero. +A line with a long_string:number overrides a line starting with '!' and means +that each character in the string will be defined as the zero-based index in +the string added to the trailing number. This is useful if your tile mappings +use characters in a non-standard order. + +The line with a tilde (~) on its own indicates the end of the definitions. Following it is the map to produce the definition for, eg. $ ascii2map example byte 1, 1, 1, 1, 1, 1, 1, 1 byte 1, 0, 0, 0, 0, 0, 0, 1 - byte 1, 2, 3, 4, 5, 6, 7, 1 - byte 1, 0, 1, 0, 1, 0, 128, 1 + byte 1, 12, 13, 14, 15, 16, 17, 1 + byte 1, 2, 1, 3, 1, 0, 128, 1 byte 1, 1, 1, 1, 1, 1, 1, 1 -- cgit v1.2.3