No Shiny

[maticarecord]

When you try to trade a Shiny using command it send normal pokemon

[Secludedly]

What game?
What set?
What type of trade?
What OS?

[maticarecord]

This happens in all games. For example, if you request a showdown that returns a Shiny: Yes, it delivers a normal one. Sometimes it delivers the Shiny, but usually it delivers a normal one. However, if I set the showdown set, it always delivers the correct Pokémon. That's what I don't understand. If someone else requests it, they get a normal one using the same showdown set I set. For example:
$trade Pikachu
Shiny: Yes

in recent versions of the bot-

[Secludedly]

Nobody can seem to replicate the issue, including myself.
Are you able to send me your config? Just be sure to remove the Token.

[maticarecord]

yes,

config - Copy.json

[maticarecord]

Were you able to check what the problem is? I've noticed that when the bot restarts, it does provide the first Pokémon as Shiny; however, once someone makes another request, the second one isn't Shiny—and it stays that way.

[whosluzy26]

I can confirm this is happening. It will work sometimes and sometimes won't. It was working fine for hours, then i restarted the latest build and now it will not recognize "Shiny: Yes" unless you use /build command

[Secludedly]

@maticarecord & @whosluzy26

In the hub under Legality, or within the config itself, change your settings to the following:

Timeout: 20
GameVersionPriority: 2 (PriorityOrder)
PrioritizeEncounters: 16, 1, 8, 2, 4 (Slot -> Egg -> Trade -> Mystery -> Static)

Then try a random shiny trade again.

EDIT: v8.0.8 & commit 826ef5d should fix this, but be sure to read the commit info to try to understand.

[whosluzy]

Tried that and it did work. The "Shiny: Yes" is only recognized if the "UseTradePartnerInfo" is set to OFF..

[whosluzy]

Another way to regain "Shiny: Yes" was to leave "GenerateOT" line empty then it works with AUTO-OT on. Weird bug

[Secludedly]

I'll play with that too and do some testing. It's very possible since it's all tied to the internal AutoOT pipeline. Though, my GenerateOT is filled with UseTradePartner enabled.

[maticarecord]

The problem persists. I asked the AI ​​to review it, and it fixed the issue by modifying something related to the auto-loot; however, the change you made is still causing problems.

[Secludedly]

Try the new release.
https://github.com/Secludedly/FusionBot/releases/tag/v8.1.1