[FIXED] Red text errors, multiple borders in the same country

Expected behaviour
When I assign the many borders that make up the country all to one country, all of them should be coloured when I pick the country in the game

Actual behaviour
Only some of the borders are coloured (eventhough city names still show up if I scroll over the uncoloured borders) when the country is picked in-game, while red text errors show up in chat (no errors show up if the country remains unpicked/neutral). Players can't join the game if the country in question has been picked (players who were already in the game when it was picked can continue playing as normal, so long as they don't refresh).

Steps to reproduce the behaviour
Host Hegemony of the Dawn and pick Bismarck Archipelago or Caroline Islands, or host Rise of Macedon scenario.

Information
Browser: All except Edge
Any other relevant information: Tends to happen in countries that are made up of a large number of borders

Attachments
When picking in-game:


When assigning in scenario editor:

1) Delete Bismarck Archipelago and Caroline Islands countries (keep the borders).
2) Save the map then exit.
3) Open the editor again and re-create the countries. Save it and go test.

If it keeps showing error messages, then look for another possible glitched country. If there are no other glitched countries, but the errors keeps appearing, then I would delete the borders/countries and draw it again.

Napisao Estus, 30.05.2020 at 20:05

1) Delete Bismarck Archipelago and Caroline Islands countries (keep the borders).
2) Save the map then exit.
3) Open the editor again and re-create the countries. Save it and go test.

If it keeps showing error messages, then look for another possible glitched country. If there are no other glitched countries, but the errors keeps appearing, then I would delete the borders/countries and draw it again.

Did this save before when Korea was bugged, however with Bismarck and Caroline there's so many borders that it's impossible for it not to happen. We sorta worked something out by Balkanising the whole thing but still, being forced to split up the province because editor is being wacky is...

Napisao Zephyrusu, 31.05.2020 at 20:10

Napisao Estus, 30.05.2020 at 20:05

1) Delete Bismarck Archipelago and Caroline Islands countries (keep the borders).
2) Save the map then exit.
3) Open the editor again and re-create the countries. Save it and go test.

If it keeps showing error messages, then look for another possible glitched country. If there are no other glitched countries, but the errors keeps appearing, then I would delete the borders/countries and draw it again.

Did this save before when Korea was bugged, however with Bismarck and Caroline there's so many borders that it's impossible for it not to happen. We sorta worked something out by Balkanising the whole thing but still, being forced to split up the province because editor is being wacky is...

We had a similar glitch, sometimes you just have to find the right border.

A ww2?

Napisao Professor Adog, 01.06.2020 at 14:57

We had a similar glitch, sometimes you just have to find the right border.

A ww2?

You find me the right border out of a whole archipelago... And, sorta.

Napisao Zephyrusu, 01.06.2020 at 15:52

Napisao Professor Adog, 01.06.2020 at 14:57

We had a similar glitch, sometimes you just have to find the right border.

A ww2?

You find me the right border out of a whole archipelago... And, sorta.

If you hosted it, of course.

Napisao Professor Adog, 01.06.2020 at 15:58

If you hosted it, of course.

Half the islands were bugged.

New Edge browser also gets errors, thanks windows updates.

Napisao Zephyrusu, 30.05.2020 at 11:56

This should be fixed now. I've released a patch to prevent this particular JS error (i.e. the red text errors) from happening.

However, the root cause of the error is glitched borders on the map, so its still possible you might run into other problems because of that. If so, take a look at this similar bug report, which explains that open borders (i.e. gaps in the borders) are one cause of it, and how to fix it.

Beyond that, if you run into any more errors with it, just let me know.

Cross-referencing related bug reports for my own benefit:

https://atwar-game.com/forum/topic.php?topic_id=47074
https://atwar-game.com/forum/topic.php?topic_id=44331
https://atwar-game.com/forum/topic.php?topic_id=41897
https://atwar-game.com/forum/topic.php?topic_id=44989
https://atwar-game.com/forum/topic.php?topic_id=47870 (maybe)
and
https://atwar-game.com/forum/topic.php?topic_id=41303