Scripting the birth of a new life.
- Thread starter Bale
- Start date
Winterbay
Active member
Isn't that more a problem with you not having a familiar rather than with the sweater? And that problem is either from KoL not leting you have a familiar when you ascend (but I don't think that is the case) or you having a familiar with the letter B in it when you ascended.
Edit: Ninjad by Bale
Edit: Ninjad by Bale
Bale
Minion
I discovered that when I ascended and found myself familiarless. I believe because my familiar had a b. That's definitely a problem with the script though since there's no way for the user to control the issue short of remembering to use a legal familiar BEFORE entering the gash. I cannot consider that to be user error.
xKiv
Active member
Mafia writes files in UTF-8 encoding, to my experience (and expects files in UTF-8).
NewLife.ash [1] is not in UTF-8. It's in some sort of 8-bit encoding, probably some "special" MS encoding (I tried iso-8859-1 through iso-8859-10 and none worked, cp1250 works and displays the character as superscript TM)
[1] at least as downloaded by firefox from the attachment in #1. But I am trying it on windows now, so 1) the broken thing is way before mafia even touches the script 2) not OSX specific at all
NewLife.ash [1] is not in UTF-8. It's in some sort of 8-bit encoding, probably some "special" MS encoding (I tried iso-8859-1 through iso-8859-10 and none worked, cp1250 works and displays the character as superscript TM)
[1] at least as downloaded by firefox from the attachment in #1. But I am trying it on windows now, so 1) the broken thing is way before mafia even touches the script 2) not OSX specific at all
Last edited:
Your script has this:
use(1, $item[Newbiesport\231 tent]);
The actual name of the item is "Newbiesport™ tent".
Apparently, some systems are able to parse that original as a trademark symbol and some are not. I'm not sure what this has to do with writing items to maps, since your script doesn't do that. But I'll agree that if we read an item, we should probably normalize the name so that if you DO write it to a file, it will have the expected character entities and will be readable on any system.
Not that that would help with the strangely encoded character embedded right in the script, as in this case.
use(1, $item[Newbiesport\231 tent]);
The actual name of the item is "Newbiesport™ tent".
Apparently, some systems are able to parse that original as a trademark symbol and some are not. I'm not sure what this has to do with writing items to maps, since your script doesn't do that. But I'll agree that if we read an item, we should probably normalize the name so that if you DO write it to a file, it will have the expected character entities and will be readable on any system.
Not that that would help with the strangely encoded character embedded right in the script, as in this case.
Last edited:
And revision 9406 does exactly that: when we create an item value, we normalize the name to the "data name". This script:
generates this in the CLI:
Code:
item [int] map;
map[0] = $item[newb tent];
print( map[0] );
map_to_file( map, "out.txt" );and this map file:
Code:
0 Newbiesport™ tentBale
Minion
I understood that. I merely meant that since mine was an error, you should look at how KoLmafia does it also. I figured that might cause trouble on some systems also.
Bale
Minion
Good point! I'll add that later.
If you use the containers, how do you stop eatdrink.ash scoffing the lot at level 1?
Dave
Not bad at all, I have just never used my closet, and was not sure I coud pull stuff back out of it in hardcore.
sorry for the noise
Dave
