The Colors of the bot is mismatched somehow

[That-SkyKid]

Colors of the bot trying to put is mismatched and sometimes the bot won't detect the existing of the color and replaces it anyway.

[WorldObservationLog]

The color transform function uses an algorithm to calculate the similarity of colors. It will transfer your image pixel's color into a numerically similar color. So it may seem not like the origin color.
For your secong problem, it's an old bug (rdeepak2002#364) and I have no idea how to fix it. You can raise the thread_delay value or mannually set start_coords of every account.

[That-SkyKid]

The color transform function uses an algorithm to calculate the similarity of colors. It will transfer your image pixel's color into a numerically similar color. So it may seem not like the origin color.
For your secong problem, it's an old bug (rdeepak2002#364) and I have no idea how to fix it. You can raise the thread_delay value or mannually set start_coords of every account.

What did you mean manually set start_coords on every account?

[WorldObservationLog]

Setting start_coords ,every accont will place different area pixels instead of upper left area. This will help ease the problem.

[That-SkyKid]

Setting start_coords ,every accont will place different area pixels instead of upper left area. This will help ease the problem.

So, I can give each account a area to draw. Can you illustrate? I don't understand.

[WorldObservationLog]

Suppose we have an 5x3 image where each pixel is represented by a letter like this:
a b c d e
f g h i j
k l m n o

if i set an account's start_coords to [0,1], it will start placeing from pixel f. and if start_coords is [2,1], it will start placeing from pixel h (zero-based count).

[That-SkyKid]

Suppose we have an 5x3 image where each pixel is represented by a letter like this:
a b c d e
f g h i j
k l m n o

if i set an account's start_coords to [0,1], it will start placeing from pixel f. and if start_coords is [2,1], it will start placeing from pixel h (zero-based count).

How this suppose to fix the issue if the script will and always put h pixel on that account?

[WorldObservationLog]

Suppose we have an 5x3 image where each pixel is represented by a letter like this:
a b c d e
f g h i j
k l m n o
if i set an account's start_coords to [0,1], it will start placeing from pixel f. and if start_coords is [2,1], it will start placeing from pixel h (zero-based count).

How this suppose to fix the issue if the script will and always put h pixel on that account?

Just ease, it cannot actually solve the problem.
The real problem is that the task of getting board image is not sync with the placing tasks.