Re: mBot FAQ

When trying to log into the bot servers the operation fails with "HardwareID limit exeeded"

You can use mBot on two computers only.
When you try to start mBot from a third computer this message is shown.

HardwareIDs will be reset each day at 00:00 UTC.

If you cannot start mBot anymore because of this change the bot password (so anyone else that may be using your account without your knowledge cannot use it anymore) here and wait until it's 00:00 UTC for the automatic HardwareID reset.
If you shared mBot with someone and now cannot login anymore this is not our fault.

There will be no manual HardwareID reset.

The possibility to use mBot on two different computers is not intended to be used to share your bot with other people.
It is in fact intended to avoid problems if you change certain characteristics of your computer that affect your HardwareID.

You can still share your bot with other people but do not expect any help if you run into "HardwareID limit exeeded" problems!

Re: [mBot] FAQ

Cannot find 'MSVCP100.dll'. Please, re-install this application.
orAfter login through bot I cannot see my character information in mBot
orWhen starting mBot a message tells me that the "application configuration is incorrect" or "side by side configuration is incorrect".

Q: mBot does not do the first part in my script where i want to do autoquest in town.

A: mBot "scans" your loaded script before starting to walk.
It then determines the point to which has the closest distance.
This point will be used as starting point for walking. All points and commands before this will be ignored.

To make mBot start the script at the very first point (and thus include the portion of the script where you do the autoquest) proceed as follows.
When you create the script set the first coordinate at the very same place where mBot's townloop stopped.
Then walk to your quest NPC, accepts the quest (for the quest-command to appear in the script).
Then walk to your trainplace without coming close to the spawnpoint in town where you started.

A: This is related to the Silkroad servers and how JoyMax login system works.
When trying to login to a server, your client sends the login-information to a Silkroad loginserver first.
Since there exists more than one loginserver, there also exists more than one login-queue in which players are waiting for a free spot on the server in case it is already full.

When the time has come and one spot is freed on your desired server, one player from each loginserver is told: "Hey, theres an empty spot on your server. Please connect to it now".
Now each of these clients disconnects from the loginserver and connects to the desired worldserver.

However only one of them acually can enter the worldserver whereas the other players will

be disonnected from the loginserver and thus been removed from the queue

not be able to login to the worldserver because it is already full again

receive the above mentioned message

If you were using a legit client you would be stuck now since it would not continue to try to login to the server but just sit there and wait forever.

In order for you to continue the relogging the client has to be restarted and you have to enter the login-queue again (which mBot will do for you).