Divide Task Processing Between Maps

[dry niche]

I obviously don't know how Tasks are set up on the back-end, so this may not be viable, but one of the biggest aggravations that currently come from using autotask is when you have tasks on two connected maps, with crew on each that are set to not open airlocks and/or disembark.

Regardless of which map they are on, they will iterate through/attempt tasks in the order they were created. This often leads to a number of tasks being temporarily skipped over while crew cycle through the "Can't reach this task due to permissions", and creates a huge amount of time inefficiency.

Perhaps it would be possible to create two separate arrays, or even a identifier variable in the current task system, which identifies which map the task is on, and if the task is unreachable due to permissions, to skip attempting that task entirely for that crew person.

[ruby obsidian]

This could also prevent the bug I've been experiencing where an NPC on OKLG keeps iterating through 2/3 of my task list while I'm docked, is denied "shore leave" to come aboard, and then my dude doesn't do those tasks for ages x)

[dry niche]

Definitely would

[cinder sorrel]

Would this fix the battery's not charging when you leave the map or has that already been fixed