UpText(C): Refers to the number of UpText strings with a TMSObject.
UpText[...]: Each index of the UpText array.
To clarify, here's an example. Say you're looking for a ladder and you want to also search the UpText of the objects that may possibly be a match. The UpText you want the script to search for is "Climb Ladder / 3 More options". And because the OCR may be inaccurate, as mentioned above, we'll split that string into a few unique parts so there's a much higher chance our correct UpText will be recognized. Personally, I'd do
['Climb', 'mb Lad', 'Ladder', 'dder /']. In this example I have
4 UpText strings. Now... how would that be placed in a NPC text file? Just like this:
Code:
UpText(C)=4
UpText[0]=Climb
UpText[1]=mb Lad
UpText[2]=Ladder
UpText[3]=dder /
You can see now the
UpText(C) equals 4; the total number of UpText strings we defined. And each
UpText[...] is the index, and don't forget;
all arrays start at the index of 0. This is why we have
UpText[0-3] rather than
UpText[1-4]. I hope that makes sense.
It should work correctly for camera angles north, south, east and west. Any angle in between those it may have issues, based on how I created the Iron Arrows ground items.