Bot wont recognize an Ü/ä/ö

[rock5]

I just did a proper test. Started my EU client in German. Added "Rüstungen" (Armor) to my INV_AUTOSELL_TYPES. Bought a belt and ran inventory:autoSell()

Code: Select all

Command> inventory:autoSell()
[DEBUG] Check item so sell: 71 227495 Exzellenter Lederg├╝rtel

So I think that if you just use your regular umlauts and save as UTF8 w/o BOM then it works.

I also tried adding Exzellenter Ledergürtel to INV_AUTOSELL_IGNORE. That worked too.

Code: Select all

Command> inventory:autoSell()
[DEBUG] Check item so sell: 71 227495 Exzellenter Lederg├╝rtel
[DEBUG] Itemname/id is in ignore list INV_AUTOSELL_IGNORE:  Exzellenter Lederg├╝
rtel => 'Exzellenter Lederg├╝rtel'

BTW

Code: Select all

Command> print(convert_utf8_ascii(itemtypes[1].Name))
Rüstungen       true

So that one prints it correctly. Maybe we should convert the item name in the debug message so it prints correctly.

[C3PO]

now I tried

Code: Select all

INV_AUTOSELL_TYPE = "Rüstungen"

and it worked!?!

if I change in the file cache/itemtypestable.lua the Umlaute to the codes it doesn't work because the bot doesn't substitute the codes afterwards and you get

Code: Select all

[DEBUG] Item is not in type option INV_AUTOSELL_TYPE:
[DEBUG] Check item so sell: 109 220649 Lederstiefel
table: 069A7500
1:      Rezepte
2:      Waffen
3:      Munition
4:      R\129stungen
5:      Unterk\148rper
6:      G\129rtel
7:      Oberk\148rper
8:      Kopf
9:      Ring
10:     Ohrring
11:     Halskette
12:     Schultern
13:     H\132nde
14:     F\129\225e
15:     Umhang
16:
Rüstungen      Leder   F├╝├ƒe  F├╝├ƒe Leder

So in this case it seems not necessary to write Umlaute with codes (eg \129) ...

[lisa]

and it worked!?!

So it didn't work before, did you do anything different, did you have more than 1 name in there before?

Code: Select all

INV_AUTOSELL_TYPE = "Unterkörper,Rüstungen"

[C3PO]

and it worked!?!

So it didn't work before, did you do anything different, did you have more than 1 name in there before?

No I didn't, I wrote all labels with the codes ... and it didn't work, so I searched the forum and found the thread that I read and thought that I did it right. Than i searched the error ...

And at the moment I can't remeber a second point where you could write Umlaute in bot stuff so it's not obvious to use them at this point. Maybe it would be a good idea to document that in the profiles\Default.xml

[krixander-2]

In my waypoint/ profile/configuration files i need to use diacritical marks like "ą ę ż ź ć ń ó ś"
is there any possible way to do it? Normally micro-macro don't recognize such marks :/

And yes I'm using utw w/o BOM in my notepad++

Or should i just give up and rewrite all files to use english version and start getting used to playing in foreign language despie all people on server who use diiferent language?

[rock5]

I'm not an expert when it comes to language issues but what do you mean by

i need to use diacritical marks

In the issue discussed above, using diacritical marks in files works (although MM didn't print them properly). Although I did discover the function "convert_utf8_ascii" which converts in-game umlauts to a format that MM can print. Depending on what your issue is, maybe that can help.

[krixander-2]

Well, for example when i use in profile:

Code: Select all

<friends>
		<!-- names of friends we help fighting or enemys we don't want to attack -->
		<!-- for umlauts use \129 (ue),\132 (ae),\148 (oe) e.g. K\132fer         -->
		<friend name="MyOtherCharacter1" />
		<friend name="Rdzeń_Zbierający_Ducha" />
		<friend name="Akolita_Mrocznego_Rytu" />
		<friend name="Czaronoksiężnik_Mrocznego_Rytu" />
		<friend name="Instruktor_Mrocznego_Rytu" />
		<friend name="Mag_Mrocznego_Rytu" />
	</friends>

It does not recognize names and still attack them :/
The same goes with names in scripts/waypoints.
I dont really care if MM shows names properly as long as it works.

[rock5]

The names should match what you see in game. Try using spaces instead of underlines.

[krixander-2]

Already tried - no effect.

[lisa]

The names should match what you see in game. Try using spaces instead of underlines.

Already tried - no effect.

Does that mean you tried using a - or does it mean you tried using a space, like this

Code: Select all

<friend name="Mag Mrocznego Rytu" />

[rock5]

I just tested with some Ruins Cleaners ("Czyściciel Ruin") because I'm already near them. I add it to my profile friends list then did some print outs.

Code: Select all

[code]Command> print(settings.profile.friends[4])
Czy┼øciciel Ruin
Command> print(CPawn(player.TargetPtr).Name)
Czy┼øciciel Ruin
Command> print(settings.profile.friends[4]==CPawn(player.TargetPtr).Name)

true[/code]So even though the friend list and target name don't print properly they still match.

I had a closer look at the part of the mob eval function that checks the friends list, it uses a string.find so to make sure, I reproduced the command.

Code: Select all

Command> print(string.find(string.lower(settings.profile.friends[4]),string.lowe
r(CPawn(player.TargetPtr).Name),1,true))
1       16

So it does work.

Lastly I started the bot in wander mode near them to see if it attacked them. It didn't. So all up I'd say it works properly so maybe you are just not setting it up properly or another issue is causing it.

[lisa]

Ok maybe I have another solution, use the getTEXT for them.

I stumbled across the in game variables for the item type names.

Code: Select all

1:      AC_ITEMTYPENAME_0
2:      Weapons
3:      AC_ITEMTYPENAME_0_0
4:      Swords
5:      AC_ITEMTYPENAME_0_0_0
6:      1-Handed
7:      AC_ITEMTYPENAME_0_0_1
8:      2-Handed
9:      AC_ITEMTYPENAME_0_1
10:     Axes
11:     AC_ITEMTYPENAME_0_1_0
12:     1-Handed
13:     AC_ITEMTYPENAME_0_1_1
14:     2-Handed
15:     AC_ITEMTYPENAME_0_2
16:     Hammers
17:     AC_ITEMTYPENAME_0_2_0
18:     1-Handed
19:     AC_ITEMTYPENAME_0_2_1
20:     2-Handed
21:     AC_ITEMTYPENAME_0_3
22:     Daggers
23:     AC_ITEMTYPENAME_0_4
24:     Staves
25:     AC_ITEMTYPENAME_0_4_0
26:     1-Handed
27:     AC_ITEMTYPENAME_0_4_1
28:     2-Handed
29:     AC_ITEMTYPENAME_0_5
30:     Ranged Weapons
31:     AC_ITEMTYPENAME_0_5_0
32:     Bows
33:     AC_ITEMTYPENAME_0_5_1
34:     Crossbows
35:     AC_ITEMTYPENAME_0_5_2
36:     Arrows
37:     AC_ITEMTYPENAME_0_6
38:     Projectiles
39:     AC_ITEMTYPENAME_1
40:     Armor
41:     AC_ITEMTYPENAME_1_0
42:     Plate
43:     AC_ITEMTYPENAME_1_0_0
44:     Head
45:     AC_ITEMTYPENAME_1_0_1
46:     Upper Body
47:     AC_ITEMTYPENAME_1_0_2
48:     Belts
49:     AC_ITEMTYPENAME_1_0_3
50:     Lower Body
51:     AC_ITEMTYPENAME_1_0_4
52:     Hands
53:     AC_ITEMTYPENAME_1_0_5
54:     Feet
55:     AC_ITEMTYPENAME_1_0_6
56:     Capes
57:     AC_ITEMTYPENAME_1_0_7
58:     Shoulders
59:     AC_ITEMTYPENAME_1_1
60:     Chain
61:     AC_ITEMTYPENAME_1_1_0
62:     Head
63:     AC_ITEMTYPENAME_1_1_1
64:     Upper Body
65:     AC_ITEMTYPENAME_1_1_2
66:     Belts
67:     AC_ITEMTYPENAME_1_1_3
68:     Lower Body
69:     AC_ITEMTYPENAME_1_1_4
70:     Hands
71:     AC_ITEMTYPENAME_1_1_5
72:     Feet
73:     AC_ITEMTYPENAME_1_1_6
74:     Capes
75:     AC_ITEMTYPENAME_1_1_7
76:     Shoulders
77:     AC_ITEMTYPENAME_1_2
78:     Leather
79:     AC_ITEMTYPENAME_1_2_0
80:     Head
81:     AC_ITEMTYPENAME_1_2_1
82:     Upper Body
83:     AC_ITEMTYPENAME_1_2_2
84:     Belts
85:     AC_ITEMTYPENAME_1_2_3
86:     Lower Body
87:     AC_ITEMTYPENAME_1_2_4
88:     Hands
89:     AC_ITEMTYPENAME_1_2_5
90:     Feet
91:     AC_ITEMTYPENAME_1_2_6
92:     Capes
93:     AC_ITEMTYPENAME_1_2_7
94:     Shoulders
95:     AC_ITEMTYPENAME_1_3
96:     Cloth
97:     AC_ITEMTYPENAME_1_3_0
98:     Head
99:     AC_ITEMTYPENAME_1_3_1
100:    Upper Body
101:    AC_ITEMTYPENAME_1_3_2
102:    Belts
103:    AC_ITEMTYPENAME_1_3_3
104:    Lower Body
105:    AC_ITEMTYPENAME_1_3_4
106:    Hands
107:    AC_ITEMTYPENAME_1_3_5
108:    Feet
109:    AC_ITEMTYPENAME_1_3_6
110:    Capes
111:    AC_ITEMTYPENAME_1_3_7
112:    Shoulders
113:    AC_ITEMTYPENAME_1_4
114:    Accessories
115:    AC_ITEMTYPENAME_1_4_0
116:    Earrings
117:    AC_ITEMTYPENAME_1_4_1
118:    Rings
119:    AC_ITEMTYPENAME_1_4_2
120:    Necklace
121:    AC_ITEMTYPENAME_1_5
122:    Off-hand
123:    AC_ITEMTYPENAME_1_5_0
124:    Shields
125:    AC_ITEMTYPENAME_1_5_1
126:    Talismans
127:    AC_ITEMTYPENAME_1_6
128:    Amulets
129:    AC_ITEMTYPENAME_1_7
130:    Back
131:    AC_ITEMTYPENAME_10
132:    Quest Items
133:    AC_ITEMTYPENAME_11
134:    Others
135:    AC_ITEMTYPENAME_12
136:    Money
137:    AC_ITEMTYPENAME_12_0
138:    Gold
139:    AC_ITEMTYPENAME_12_1
140:    Diamonds
141:    AC_ITEMTYPENAME_2
142:    Supplies
143:    AC_ITEMTYPENAME_2_0
144:    Foods
145:    AC_ITEMTYPENAME_2_1
146:    Desserts
147:    AC_ITEMTYPENAME_2_2
148:    Potions
149:    AC_ITEMTYPENAME_3
150:    Materials
151:    AC_ITEMTYPENAME_3_0
152:    Ores
153:    AC_ITEMTYPENAME_3_1
154:    Wood
155:    AC_ITEMTYPENAME_3_2
156:    Herbs
157:    AC_ITEMTYPENAME_3_3
158:    Raw Materials
159:    AC_ITEMTYPENAME_3_4
160:    Production Runes
161:    AC_ITEMTYPENAME_4
162:    Recipes
163:    AC_ITEMTYPENAME_4_0
164:    Blacksmithing
165:    AC_ITEMTYPENAME_4_1
166:    Carpentry
167:    AC_ITEMTYPENAME_4_2
168:    Armorcrafting
169:    AC_ITEMTYPENAME_4_3
170:    Tailoring
171:    AC_ITEMTYPENAME_4_4
172:    Alchemy
173:    AC_ITEMTYPENAME_4_5
174:    Cooking
175:    AC_ITEMTYPENAME_5
176:    Equipment Enhancement
177:    AC_ITEMTYPENAME_5_0
178:    Refining Gems
179:    AC_ITEMTYPENAME_5_1
180:    Runes
181:    AC_ITEMTYPENAME_5_2
182:    Fusion Stones
183:    AC_ITEMTYPENAME_6
184:    Monster Cards
185:    AC_ITEMTYPENAME_7
186:    Mounts
187:    AC_ITEMTYPENAME_8
188:    Household
189:    AC_ITEMTYPENAME_8_0
190:    House Contracts
191:    AC_ITEMTYPENAME_8_1
192:    Furniture
193:    AC_ITEMTYPENAME_8_2
194:    Knowledge Books
195:    AC_ITEMTYPENAME_9
196:    Special Items

So accessories would be

Code: Select all

getTEXT("AC_ITEMTYPENAME_1_4")

Funilly enough the itemtypes.lua uses the in game type names to populate that table.

[rock5]

So I could just use the itemtypes table. I would still have to change and test in various languages and the item types might not cover all diacritics.

[lisa]

Maybe I'm just not thinking straight but it seems weird to me.

We use the in game names to populate the table into the local language so that it is easier for people to use,
ie "weapons" instead of "AC_ITEMTYPENAME_0"

The bit that confuses me is that for german atleast this process is actually making it harder because of the special characters.

I am thinking the best people to let us know what would be easier would be the ones using german client.

--=== 1 ===--
Would it be easier to use some sort of numer system.

weapons = 0
armor = 1
supplies = 2

Then they just have to learn the numbers they need to use for the items.

--=== 2 ===--
Would it be easier to do some sort of substituting characters so
instead of ń you use n
instead of ę you use e
instead of ż you use z
or would that make it confusing.

--=== 3 ===--
Would it be easier to just use english names and they can have a table to compare it to

So the itemtables would look like this

Code: Select all

[4] = { Name = "Accessories", -- Rüstungen

So the local langauge name is printed as a comment for each Name, so they can look at the table and then know what the english version is to use?

--=== 4 ===--
Something I haven't thought of yet.

[rock5]

If it works then it should be as easy for the Germans as it is for us, assuming they have no trouble writing in their own language. And the tests I've done indicate that using those characters in the type names, works. So I think it's just a matter of them getting into the habit of using a proper editor and using the actual special characters and getting out of the habit of using the \xxx codes, for type names anyway.

[gamerix92]

Hallo,

i did everything which is written in this hole posts.

I tried :

1. utf8 w/o Bom -> fail
INV_AUTOSELL_TYPE value = "Rüstungen "

2. use englisch instead of german like :
INV_AUTOSELL_TYPE value = "weapons, armor "

weapons -> success
armor -> fail
curious or ??

3. using code :
(umlaut in xml)
INV_AUTOSELL_TYPE value = "R ü stungen "

(umlaut in lua)
INV_AUTOSELL_TYPE value = "R\195\188stungen "

ur version :
INV_AUTOSELL_TYPE value = "R \129stungen "

4. using the items: (also in all methods like in point 3. )
INV_AUTOSELL_TYPE value = "Oberkörper, Unterkörper, Gürtel, Kopf, Schultern etc. "


Without selling possibilities Ks farm make no sense xD
Please try to chance something. i need gold ^^
i hope their will be an update. Thx

[gamerix92]

ohh i forgot,

tried also with number

INV_AUTOSELL_TYPE value = "0 , 1 " -> fail

INV_AUTOSELL_TYPE value = "[0],[1]" -> fail

INV_AUTOSELL_TYPE value = "itemtypes.[0], itemtypes.[1]" -Y fail

[BlubBlab]

Ich benutze das hier :

Code: Select all

local armortype = itemtypes[1].Name
	local weapontype = itemtypes[0].Name
	changeProfileOption("INV_AUTOSELL_ENABLE",true)
	changeProfileOption("INV_AUTOSELL_TYPES", ""..armortype..","..weapontype..""  )
	
	changeProfileOption("INV_AUTOSELL_QUALITY","white,green,blue");

	changeProfileOption("INV_AUTOSELL_FROMSLOT",1);
	changeProfileOption("INV_AUTOSELL_TOSLOT", 180);

[gamerix92]

Vielen Dank . Thank you .

It helped nice work.

Solution :

Implement the code von BlubBlab into your Wp file (onload)

Thank you

[rock5]

I used the following and it worked fine.

Code: Select all

<option name="INV_AUTOSELL_TYPES"			value="Rüstungen,Waffen"/>

• 1. Make sure you don't add extra spaces.
  2. Make sure you change to utf8 w/o bom before entering the umlauts.