Seite 1 von 1

new backend vs MFBot

Verfasst: Do 5. Mai 2022, 12:58
von bombas
Any plan to make MfBot working with new backend? Now there is info in account log with every try to log in:
"05.05.22 12:53:20.075 acountname@XXXXX Input string was not in a correct format. Error Basis"

Now new backend is working on this servers:
S1.BR
S1.IN
S1.JP
S1.MX
S1.RO
S1.RU
S2.BR
S2.CL
S2.PT
S2.SE
S2.SK
S2.TR
S2.UK
S3.ES
S3.FR
S3.NL
S3.PT
S3.TR
S5.CZ
S5.FR
S5.GR
S5.HU
S6.HU
S7.PT
S8.ES
S8.FR
S8.HU
S8.IT
S9.HU
S10.PL
S11.PL
S15.PL
S16.CZ
S18.PL
S26.PL
S27.PL
S28.PL
S29.PL
S31.DE
TV2.DK
SPEED
and everyday about 2-3 servers will migrate to new backend, so in near future problem of compability MfBot and new backend will be problem all of us.

Re: new backend vs MFBot

Verfasst: Do 5. Mai 2022, 13:45
von neuhier

Re: new backend vs MFBot

Verfasst: Do 5. Mai 2022, 14:11
von bombas
Ohh yeah, it works perfectly. Thanks for help! Is it your homemade or beta?

Is it quite safe to use ini from non-working with new backend verson 5.4.1.0 (Wisteria)?


EDIT: i've searched forum and found Robin's post with this version. Glad to see that You're still developing this excellent app!

Re: new backend vs MFBot

Verfasst: Do 5. Mai 2022, 21:33
von neuhier
noooo its not mine, robin posted it in another thread :)

Re: new backend vs MFBot

Verfasst: So 15. Mai 2022, 23:38
von Robin
Hi there,

I'm glad the Nightly version seems to do its job, I'd like to point out that there is a beta version now that is not a forum-super-special-version :-D (see https://www.mfbot.de/en/version-5-4-2b1-beta-notice/)
Thanks for keeping up with our "interesting" release schedule!

Regards, Robin

Re: new backend vs MFBot

Verfasst: Mo 16. Mai 2022, 22:14
von magyar
Hello!

Due to the new backend update, the bot (5.4.1.0.wisteria) is not working properly.
My experience: half of the characters enter and work, the other half do not.
My comment and fix:
For non-working characters in the .ini file, replacing the "CRYPID" and "CRYPKEY" lines will fix the problem.
It must be replaced with code that is in the form of a working character.

That's how I solved it and stayed with version 5.4.1.0.wisteria for now.
Currently this way all characters enter and work

Re: new backend vs MFBot

Verfasst: Do 19. Mai 2022, 09:50
von Robin
magyar hat geschrieben: Mo 16. Mai 2022, 22:14 For non-working characters in the .ini file, replacing the "CRYPID" and "CRYPKEY" lines will fix the problem.
It must be replaced with code that is in the form of a working character.

That's how I solved it and stayed with version 5.4.1.0.wisteria for now.
Currently this way all characters enter and work
Hi again,

please do not do this! If you replace these two parameters in the Acc.ini, you effectively use the session of the account that's working and the bot doesn't play your non-working character but the one you use the session parameters from.

Regards,
Robin

Re: new backend vs MFBot

Verfasst: Mi 25. Mai 2022, 12:17
von magyar
Hello!

I didn't find any error.
All characters work normally. (multiple servers, multiple characters)
It's checked. The game is continuous for all characters. (missions, guard, etc.)
Wisteria has been working this way for weeks

Now I looked at what's going on in the .ini file.
"CRYPID" is different for each character. (this may have been overwritten on exit).
"CRYPKEY" is identical in several places. (I modified these a few weeks ago.
I copied it from a working server, a given caste, to a non-working entity on the same server, the same caste.)

I tried the old .ini file now. (saved)
Half of the characters enter, the other half do not.
I checked the old .ini file.
"CRYPID" is different for each character.
"CRYPKEY" I see is different for each character.

The difference is therefore to be found in "CRYPKEY".
What can this affect?

I'll put the working .ini file back.

Re: new backend vs MFBot

Verfasst: Mi 25. Mai 2022, 18:03
von beroun
Hello,
I am playing on 6 different servers, and some of them work, but some don't. Bot has not worked on s3.nl since the day it received the new backend. Is there anything I can do to fix it?