Birth of the Federation

Just tell them to use one of the two methods to switch the player empire: viewtopic.php?p=57851#p57851 (instead of UE)

Iceman wrote: ↑Sun Mar 10, 2024 1:03 pmWe are actually making a smallish improvement to the site right now And at some point I'll have a new version of the manual ready to upload to the site.

You should think about adding the page link in your AFC signature.

it obviously is a counted dword value, for task force 89 04 00 00 you even find EF ED 01 00 @ 0x54 Sorry for the fuss, looks like an error in my old database. :mad: Was mislabeled as distance (num sectors/waypoints) in map movement codes, but indeed is an item ID. Sometimes set to zero if a sector ...

already ordered task forces keep their mission. So when a colony ship is underway, you need to cancel the ordInfo order. I see, thank you. So no need to update this code, since it can't fix this BotF AI glitch (without editing AI files in the savegame). :up: The abort code for AI colonize tasks nee...

Also @ +50 -> greatest colony ship production value, so your 'contains colony ships' = 1 doesn't work for patches (but greater null will). That is long fixed, what location did I miss? Just from the wiki, if UE already sets 'greatest colony ship production value in the fleet' (not always 1 if CS), ...

any other updates? ECM? I'm uncertain about: - Race Info Screen with Minor Race Personality and AI Agenda (great patch, but no bug-fix, might pass as cosmetic?) - War Check Fix for Pacifist Minor Races - AI Agenda fix - Offensive War -> still unfinished buggy And perhaps we can fix Planet killer (a...

Wait, are you joking on me? :lol: Just to avoid a discrimination lawsuit from the ice bear Flocke (i.e. for claiming she supported that patch): :wink: Most interesting will be to see whether it works in multiplayer games as well - or at least doesn't worsen synchronization issues. I forgot the MP s...

All planets affected are asteroid gas giants: Thank you. Just ignore this side effect of the Planet killer (and ECM Borg) exploit code for now: https://www.armadafleetcommand.com/onscreen/botf/viewtopic.php?p=46143#p46143 Sub_43E180 Change_Planet_entry_eax_to_edx needs an update for gas giants, con...

Ok here is your test patch: Temp_TF_IDs_Fix.patch NAME: Savegame Fix for Overlapping Temporary Task Force IDs DESC: Fixes issues with redeploying ships when there already are redeployed task forces stored in the loaded savegame. DESC: NOTE redeploying player ships won't work for previous unpatched g...

Did you mess with the planet bonus values? No, all values should be plain vanilla. And I didn't notice obvious deviations in any test game. Wiki: population bonus (few = 00 00, normal = 36 01, much = 6C02, else = normal) Persists this issue in other/current ECM games? If so I suspect an error in th...

Where's the patch? :D I thought it's a good test case for you new positronic auto-coding framework in cooperation with recent deep/dumb-AI...., but I will see what I can do. :wink: OT: Has OrdInfo/resultlist also temp IDs or are they ongoing/limited like regular TF IDs (in case issued player orders...

Ah well, that would be a plausible cause. No, that's just a confusing UI problem and does NOT cause this topic issue! I still think this was initially caused by invalid temp IDs somehow pointing to wrong GTForceList previous turn order and/or OrdInfo. overlapping temporary task force ids... I dunno...

Possibly one should not redeploy ships when there already are redeployed task forces stored to the loaded savegame. Yes, I propagate this for quite some time now. Worst case is that changed or phantom ships can crash the game in later turns. But even without redeploying there is many issues with ch...

I thought about testing plasma hob, but as a single billboard it will never display correctly from front or rear angle. IMHO that's just a minor graphic inconvenience we could live with. There is far worse multifactorial issues with many wrong and incomplete codes: - reference scale sometimes volat...

the label is read from lexicon.dic 641 as I have just confirmed by editing the label. Searching trek.exe for the hex value "81 02" I found sub_4FBAD8 which explictly sets labels for the planet types. You hardly can call this a coding glitch. It might be miscommunication, yes, it might als...