Skip to content

FusionBot v8.3.0

Choose a tag to compare

View all tags
@Secludedly Secludedly released this 18 Jul 02:39
· 3 commits to main since this release
v8.3.0
aa0447f

v8.2.9
Respect AllowTrainerDataOverride in custom OT/TID/SID logic

The AllowTrainerDataOverride flag was only wired into ALM via
APILegality.AllowTrainerOverride. The bot's own custom override
logic (ApplyUserTrainerOverride in the trade path, ApplyTrainerOverride
in the convert/legalize path) stripped and re-applied user OT/TID/SID
lines unconditionally, bypassing the config flag entirely. Users could
force trainer data even with the setting off.

Gate all three custom override call sites behind
Legality.AllowTrainerDataOverride so the setting is honored. When
disabled, the stripped lines are simply not re-applied and the bot's
generated trainer info stands.

v8.3.0
Fix BDSP AutoOT writing illegal Pokemon to trade box on revert

ApplyAutoOT's legality-failure branch wrote the partner-modified clone
(cln) to the trade box while returning the original toSend. The main
confirm path does not re-write the box after ApplyAutoOT, so it traded
the illegal clone even though the revert appeared to return the original.
Write toSend on the failure branch so the box always matches the
returned value, matching the revert behavior of the other game bots.

Assets 5
Loading
0 Join discussion