Transit Diodes Bot Error Tell Fin

[cobalt mantle]

Happened two times in our game. A player uses Transit Diodes, and when moving units from an area, it claims "Bot Error. Tell Fin.". So here we are. @runic steppe

[main coral]

Ironcache used /game info game_name: pbd6348

Game Info:

Name: pbd6348

Owner: Ironcache
Created: 2024.11.28
Last Modified: 2024.12.31
Ended: false
Game Completed: false

Setup:

Victory Point Count: 12
Secret Objective Count: 3
Private Game: false
Game Modes: DiscordantStars, Homebrew
Map Template: 6pStandard
Map String: {18} 41 D118 D122 63 26 28 69 D108 33 D123 23 20 35 80 24 40 D102 72 D06 39 38 05 D103 76 D14 67 42 55 30 74 11 78 D121 D17 D119 64
Hex Summary: 40-2+0,d102-2+2,55+0-6,72-1+3,30-1-5,74-2-4,11-3-3,78-3-1,d121-3+1,d17-3+3,d119-2+4,64-1+5,18+0+0,41+0+2,d118+1+1,69+0+4,d122+1-1,d108+1+3,d06+0+6,63+0-2,33+2+2,39+1+5,26-1-1,d123+2+0,38+2+4,28-1+1,23+2-2,05+3+3,20+1-3,d103+3+1,82bnull,35+0-4,76+3-1,80-1-3,d14+3-3,24-2-2,67+2-4,42+1-5
Show Map Setup: false
Strategy Card Set: pok
Strategy Cards: [pok1leadership, pok2diplomacy, pok3politics, pok4construction, pok5trade, pok6warfare, pok7technology, pok8imperial]
Decks:

• Action Card Deck: action_cards_pok 46/120
• Secret Objective Deck: secret_objectives_pok 23/40
• Stage 1 Public Objective Deck: public_stage_1_objectives_pok 15/20 (+0 are staged/peekable)
• Stage 2 Public Objective Deck: public_stage_2_objectives_pok 15/20 (+3 are staged/peekable)
• Agenda Deck: agendas_pok 40/50
• Technology Deck: techs_ds
• Relic Deck: relics_pok 7/13
• Exploration Deck: explores_pok
• Industrial Deck: 11/20
• Hazardous Deck: 5/20
• Cultural Deck: 7/20
• Frontier Deck: 7/20

Settings:

Beta Test Mode: false
Game Auto-Ping Time Interval (hrs): 24
Player's Auto-Ping Time Interval (hrs):

: Off
: Off
: Off
: Off
: Off
: Off
Text Size: medium
Full Text Output: false
Output Verbosity: verbose
Table Talk Channel: #1311517936153792552
Actions Channel: #1311517939014303785
Bot Map Thread: #1311517947793248277

Players:

1. MercurySunset
2. AlzuBrown
3. yumdayumPurple
4. IroncacheRainbow
5. CronoEmerald
6. WahaBloodRed

Other Players:

Other Stats:

Current Phase: action
Game Player Count: 6
Game Real Player Count: 6
GMIDs: []
SCs per player: 1
TopMostTileOffset: 1650
BottomMostTileOffset: 3450
LeftMostTileOffset: 1300
RightMostTileOffset: 2860
Map Images Generated: 181
Strategy Card Trade Goods: {1=0, 2=0, 3=0, 4=2, 5=0, 6=1, 7=0, 8=0}
Public Objectives: {Custodian/Imperial=0, engineer_marvel=1, raise_fleet=2, research_outposts=3, amass_wealth=4, make_history=5, unify_colonies=6, Learn the Secrets of the Cosmos=7, revolutionize=8}
Laws: {classified=454, arbiter=875, rep_govt=323}
Laws Info: {classified=Learn the Secrets of the Cosmos, arbiter=saar}
Events: {}
Migrations Run: []
Buttons pressed: 5567
SlashCommands used: 87

[cobalt mantle]

Not the command I meant...

[main coral]

Ironcache used /search for_game game_name: pbd6348

Here's the requested channels:
#1311517936153792552
#1311517939014303785

[cobalt mantle]

Happening in pbd6348. Message link for the latest:

#1311517939014303785 message

Okay that message deleted itself. Here's the old one that is still in the chat log:

#1311517939014303785 message

It should be noted that it was benign; AFAICT, it handled the movement perfectly fine. I just saw the error so am reporting it.

[main coral]

PrisonerOne used /show_game game_name: pbd6348

[lean vault]

Bot struggling between biaheo and blaheo I think

[cobalt mantle]

That would make sense. Both times the error has happened has involved that planet, IIRC.

[green bear]

I'll fix that Soon™ if nobody else does so first.

[lean vault]

I can't figure out why it would be throwing the error though, short of game.getPlanetInfo not containing that planet for some reason

[green bear]

With that said, I'm just gonna s/blaheo/biaheo/, which might break some games in progress (hopefully in a fixable way, though).

[lean vault]

This might only be an issue with the way TD is handling biaheo

[cobalt mantle]

For some context from our game, we've had no issues with Biaheo outside of these TD errors (and again, even these TD errors have been benign; the units have moved okay I believe. @livid gorge can confirm).