SolarStrike Software

Hello,
I´ve got a little problem:
yesterday I changed the race from one of mine characters (on private server)
since then rombot can´t detect the name anymore it just says "We cant find your profile '<UNKNOWN>.xml'..."
When I run RoM multiple times I get to the screen where I can select the character I want to bot on, but when I clicked the one with the changed race the upper message appears.
The other characters work fine.

In some older thread I read that it should help to delete the macro.bsd from the affected character but this didn´t work for me

Thank you

Edit:
I just realized that if I use the profile "userdefault.xml" my character walks up the path also targets mobs but doesnt attack them

Something funny and unexpected might have happened when you changed race. It might be a bit tricky to figure out. First I'll need to see the full error message with file name and line number info. Just copy and paste the whole error message.

Wait, I found it. Now lets see what's going on.

Try this. First start the commandline with the default user profile. Print the player name. Print the converted name it uses for file names. See if they display what you expect.

Thank you for your reply.. I tried it, but it doesn´t seem to work

Edit:
I just added the message I get if I don´t create the profile "userdefault.xml".
And I don´t know if it´s somehow relevant but I changed from an female elf to an female dwarf, now this class doesn´t exist in the normal game so can this somehow be a reason for the problem?

Darax wrote:And I don´t know if it´s somehow relevant but I changed from an female elf to an female dwarf, now this class doesn't exist in the normal game so can this somehow be a reason for the problem?

Possibly. Try printing the players Id There is a player id for each race and gender. Currently the maximum is 1004. I suspect it will print 1005. If so, edit settings.lua and find the following on line 191. and change it to 1005.

print(player.Id) responded with -1,
but the change from 1004 to 1005 fixed it, thanks a lot it seems to work again

Cool. I'll add that to my next commit.

I should probably do a commit soon.