Skip to content
This repository has been archived by the owner on May 2, 2023. It is now read-only.

WindBot-Ignite in Edopro Folder (is Possible??) #1

Open
wants to merge 89 commits into
base: tcg
Choose a base branch
from
Open

WindBot-Ignite in Edopro Folder (is Possible??) #1

wants to merge 89 commits into from

Conversation

ghost
Copy link

@ghost ghost commented Mar 25, 2021

It is possible to modify the Edopro / windbot folder in order to customize the decks without having to report, so that whoever wants to can already insert them in his edopro folder ?? I have created several decks and I don't know if they will be accepted and inserted at least so they can be inserted independently, is it possible?

mercury233 and others added 30 commits January 22, 2020 09:57
Also updates the name to Silver's Cry.
The cause was that, when tributing, InternalOnSelectCard would try to read from the packet to initialize the LocationInfo twice, so it would try to read beyond the end of the stream and crash, and when not tributing, it wouldn't read the LocationInfo from the packet at all, so it couldn't find any specific card. Make it read the right amount once in each case.
Fix Tribute Summoning crashing, and SelectCard(ClientCard) not working
…(#8)

This adds some support for Speed Duels, Terminal World, and other cases when Main Phase 2 is not a thing.
Useful for debugging from Visual Studio, making it easier to specify the DbPath in the command line arguments
Previously it was building libWindbot and not desktop Windbot
If the AI went second, and it tried to Tribute Summon and recieved SelectTribute instead of SelectUnselect (both can happen depending on gamestate), then it would read from the wrong player's field when matching the list of possible tributes (from the packet) to ClientCards. So it would find zero valid tributes, and cancel the Tribute Summon, unless the opponent coincidentally had a monster in their same-numbered monster zone(s) as the possible tribute(s). If the AI cancelled the Tribute Summon, the conditions that made the Executor try to Tribute Summon would be unchanged, so it would try to Tribute Summon again, and go into an infinite loop. With each loop, it would send a chat message saying that it was summoning the monster.

Fixed by copying the logic from LocationInfo.Read.

Fixes #6
AlphaKretin and others added 30 commits April 30, 2020 21:07
- Mathmech
- Time Thief
- Windwitch Gusto
- Witchcrafter Grass
One fast job to build for desktop and uploading those release archives.
One slower job to build the Android aar.

Closes #10.
Update public-facing Deck name to official TCG translation "Dogmatika"
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants