Sexy

> *Originally posted by **[DR_F3LL](/forums/2468/topics/920187?page=13#13131501)**:* > v3.0.0 supports the "Skill Reliability Updates 2019 ". > This and following v3.X.Y versions are not fitted for simulating until the changes got live. > I didn't yet test all skills one by one. Reports are welcome. 3rd version! Hurray!)

*root@astraG:/home/adming/tyrant/tyrantoptimize-3.0.2# make VERSION=v3.0.2* make -f make/Makefile.linux all make[1]: вход в каталог «/home/adming/tyrant/tyrant_optimize-3.0.2» mkdir -p obj touch obj/.stamp g++ -Wall -Werror -std=gnu++11 -Ofast -DNDEBUG -DNQUEST -DTYRANT_OPTIMIZER_VERSION='"v3.0.2"' -o obj/sim_test.o -c sim_test.cpp g++ -Wall -Werror -std=gnu++11 -Ofast -DNDEBUG -DNQUEST -DTYRANT_OPTIMIZER_VERSION='"v3.0.2"' -o obj/tyrant.o -c tyrant.cpp g++ -Wall -Werror -std=gnu++11 -Ofast -DNDEBUG -DNQUEST -DTYRANT_OPTIMIZER_VERSION='"v3.0.2"' -o obj/read.o -c read.cpp g++ -Wall -Werror -std=gnu++11 -Ofast -DNDEBUG -DNQUEST -DTYRANT_OPTIMIZER_VERSION='"v3.0.2"' -o obj/cards.o -c cards.cpp g++ -Wall -Werror -std=gnu++11 -Ofast -DNDEBUG -DNQUEST -DTYRANT_OPTIMIZER_VERSION='"v3.0.2"' -o obj/xml.o -c xml.cpp g++ -Wall -Werror -std=gnu++11 -Ofast -DNDEBUG -DNQUEST -DTYRANT_OPTIMIZER_VERSION='"v3.0.2"' -o obj/sim.o -c sim.cpp g++ -Wall -Werror -std=gnu++11 -Ofast -DNDEBUG -DNQUEST -DTYRANT_OPTIMIZER_VERSION='"v3.0.2"' -o obj/deck.o -c deck.cpp g++ -Wall -Werror -std=gnu++11 -Ofast -DNDEBUG -DNQUEST -DTYRANT_OPTIMIZER_VERSION='"v3.0.2"' -o obj/tyrant_optimize.o -c tyrant_optimize.cpp g++ -o tuo obj/sim_test.o obj/tyrant.o obj/read.o obj/cards.o obj/xml.o obj/sim.o obj/deck.o obj/tyrant_optimize.o -lboost_system -lboost_thread -lboost_filesystem -lboost_regex -lboost_timer -lpthread .............. *./tuo "menogu" "ShellGauntlet" pvp ordered -v -o -s climbex 10 200 fund 0 -L 4 10 dom- -e "SuperHeroism"* **Segmentation fault ** .... with 2.x.x version was all ok

Function to forbid some cards in disallowed_candidates works very strange. Is it mentioned this way or is it a bug? Me: Don't you touch my legendaries TUO: Ok TUO: Enjoy fusions from double legendaries

> *Originally posted by **[Arctomachine](/forums/2468/topics/920187?page=14#13134983)**:* > Function to forbid some cards in disallowed_candidates works very strange. Is it mentioned this way or is it a bug? > > Me: Don't you touch my legendaries > TUO: Ok > TUO: Enjoy fusions from double legendaries disallowed_candidates only disables cards from being considered as a final part of the deck. It does *not* disable cards from being considered as fusion materials.

> *Originally posted by **[DR_F3LL](/forums/2468/topics/920187?page=14#13137786)**:* > > *Originally posted by **[Arctomachine](/forums/2468/topics/920187?page=14#13134983)**:* > > Function to forbid some cards in disallowed_candidates works very strange. Is it mentioned this way or is it a bug? > > > > Me: Don't you touch my legendaries > > TUO: Ok > > TUO: Enjoy fusions from double legendaries > > disallowed_candidates only disables cards from being considered as a final part of the deck. It does *not* disable cards from being considered as fusion materials. > Not sure if it is right or not, but I added double legendaries into file and still get same result.

> *Originally posted by **[Arctomachine](/forums/2468/topics/920187?page=14#13140678)**:* > > Not sure if it is right or not, but I added double legendaries into file and still get same result. TUO will only exclude the **exact** cards specified in disallowed_candidates. So the sim won't use your double legendaries, but it tries **all** cards that can be fused from your double legendaries. EG:  disallowed_candidates: Vigil, Sanctuary => Sim still uses Harmony + Conclave's Harmony disallowed_candidates: Harmony => Sim still uses Conclave's Harmony ( + Vigil + Sanctuary) disallowed_candidates: Conclave's Harmony => Sim won't use Conclave's Harmony, but Harmony + Sanctuary + Vigil

Try disallowed_recipes instead - if you add "Harmony" - its only possible for TUO to sim "Conclave's Harmony" when you already have 2 "Harmony".

Allright, maybe I'm using wrong method for what I'm expecting to achieve. I want so sim everything I have excluding base legendaries and all their fusions (+ vindi). What is the best way here?

You can comment the base legendaries in your ownedcards.txt using double slash (//) in front of those cards: //Apex //Benediction //Omega //Nimbus //Malgoth

#### v2.64.0 - Add Test Algorithm 'beam': This algorithm optimizes the deck based on a the normal (hill) climb algorithm, but uses multiple decks. Therefore this algorithm is less likely to produce local optima. ###### example usage: ./tuo gauntlet1 gauntlet2 beam 100 surge ###### Algorithm: A simplified description of the algorithm: Say we have a beam-size of 5. Then the algorithm always saves the 5 known best decks. Instead of trying to further optimize only the best deck, like hill climb does, beam-climb will test each of the 5 decks for new best performing decks. This procedure is repeated until no better decks are found. Read Further: https://en.wikipedia.org/wiki/Beam_search ###### Comparison to climb: * The algorithm is generally slower than normal climb, but yields better results. * Best way to use this algorithm probably is to check an already simmed deck for final improvements. ###### Parameters: * 'beam-size' sets the size of the beam/decks (default=5) ###### Implementation notes: * You can pass gauntlets as your deck, this will then sim each of them and keep the best X of them (X='beam-size') * If 'beam-size' excedes the number of passed decks, it will be filled with mutated decks (see Genetic Algorithm) ##### Caution: * Default parameters are not perfect yet, playing around with the parameters might increase/decrease performance drastically (any feedback or ideas on changes are as always much appreciated). * The algorithm should work with most tuo flags/modes, but not all are tested. * Better check if the results seem reasonable ###### Other Notes: * 'climb_forts' and 'genetic' bug fixes Special Thanks to Ender Cloud for mentioning and explaining the algorithm.

> *Originally posted by **[DR_F3LL](/forums/2468/topics/920187?page=13#13131501)**:* > v3.0.0 supports the "Skill Reliability Updates 2019 ". > This and following v3.X.Y versions are not fitted for simulating until the changes go live. > I didn't yet test all skills one by one. Reports are welcome. Does this mean that v3.X.Y does not work to sim today? Or that v3.X.Y has a time check to start simming with the skill updates on 6/18?

> _Originally posted by **[Monkey_k](/forums/338/topics/920187?page=14#13154738):**_ > > *Originally posted by **[DR_F3LL](/forums/2468/topics/920187?page=13#13131501)**:* > > v3.0.0 supports the "Skill Reliability Updates 2019 ". > > This and following v3.X.Y versions are not fitted for simulating until the changes go live. > > I didn't yet test all skills one by one. Reports are welcome. > > Does this mean that v3.X.Y does not work to sim today? Or that v3.X.Y has a time check to start simming with the skill updates on 6/18? Sure it works, but result is not correct, because it uses already the buffed skill mechanics - and since they are not live....

> *Originally posted by **[DR_F3LL](/forums/2468/topics/920187?page=14#13153757)**:* > #### v2.64.0 - Add Test Algorithm 'beam': > > This algorithm optimizes the deck based on a the normal (hill) climb algorithm, but uses multiple decks. > Therefore this algorithm is less likely to produce local optima. Cool! Thank)

Just noticed that Enhance being applied twice: ``` tuodebug "Dracorex Hivegod, Deadly Leaper #3" "Dracorex Hivegod, Deadly Leaper #3" debug +v sim 1 ------------------------------------------------------------------------ TURN 1 begins for P0 Commander [Dracorex Hivegod hp:209] P0 Commander [Dracorex Hivegod hp:209] plays Assault 0 [Deadly Leaper: 25/76/0 legend bloodthirsty, Evade 5, Pierce 80, Venom 50] Possible targets of Enhance: + P0 Assault 0 [Deadly Leaper att:[[25(base)]]=25 hp:76] P0 Commander [Dracorex Hivegod hp:209] Enhance Venom 6 on P0 Assault 0 [Deadly Leaper att:[[25(base)]]=25 hp:76] Evaluating P0 Commander [Dracorex Hivegod hp:209] skill Enhance all Venom 6 Possible targets of Enhance: + P0 Assault 0 [Deadly Leaper att:[[25(base)]]=25 hp:76, Venom +6] P0 Commander [Dracorex Hivegod hp:209] Enhance Venom 6 on P0 Assault 0 [Deadly Leaper att:[[25(base)]]=25 hp:76, Venom +6] Evaluating P0 Commander [Dracorex Hivegod hp:209] skill Heal all bloodthirsty 10 Evaluating P0 Commander [Dracorex Hivegod hp:209] skill Weaken all 6 P0 Assault 0 [Deadly Leaper att:[[25(base)]]=25 hp:76, Venom +12] attacks P1 Commander [Dracorex Hivegod hp:209] for 25 damage P1 Commander [Dracorex Hivegod hp:209] takes 25 damage TURN 1 ends for P0 Commander [Dracorex Hivegod hp:209] ------------------------------------------------------------------------ ```

> *Originally posted by **[dsuchka](/forums/2468/topics/920187?page=14#13159843)**:* > Just noticed that Enhance being applied twice: Thanks. [4993429](https://github.com/APN-Pucky/tyrant_optimize/commit/49934295780cc9ef3ac206c8a030b051f68e1b61) should fix it. I removed enhance from the activation skill list now, since it doesn't trigger on activation anymore.

> *Originally posted by **[DR_F3LL](/forums/2468/topics/920187?page=14#13160111)**:* > Thanks. [4993429](https://github.com/APN-Pucky/tyrant_optimize/commit/49934295780cc9ef3ac206c8a030b051f68e1b61) should fix it. > I removed enhance from the activation skill list now, since it doesn't trigger on activation anymore. Nice solution, thank you for your continuing support! But there is one more thing should be fixed: > This means these Enhances will not be able to target cards that have just been played that turn, as they are not on the field until after Enhance has triggered. In the game (now it got fixed) cards have just been played get no any enhance from commander/structures (exactly as described).

> *Originally posted by **[MarshalKylen](/forums/2468/topics/1830624?page=1#13128017)**:* > ### Enhance > > * Enhance will have a new mode that allows it to apply to Allegiance, Absorb, Stasis, and Bravery. > * Enhance for these skills will occur in the earliest phase of the turn, when cooldowns tick down and Bravery and Absorb trigger, before new cards are played. > * This means **these** Enhances will not be able to target cards that have just been played that turn, as they are not on the field until after Enhance has triggered. > * Enhances for other skills will now happen slightly earlier in the turn, in the **same phase** as Inhibit, Sabotage, and Disease activate. > I read this as "these" Enhances only referring to Allegiance, Aborb, Stasis and Bravery. I couldn't check how all Enhances work in game. Also other Enhances should activate in the "same phase" with Sabotage, Inhibit, etc. which happens after cards being played. ##### Edit: Just read your github post again. I thought both (kong post and gh post) were the same. I'd say it's an issue of the game, not of the sim.

Yeah, I posted first here, but it was blocked by administator by some reasons, and then I re-read enhance description and posted on hg. Never mind) > I'd say it's an issue of the game, not of the sim. Agree. What is more I'm afraid that will not be fixed, as well as Subdue (yes, it stacks on each attack attempt, regardless of a damage dealt, like it's a damage-independent skill).

Petrisis Fleshcrafter Raid seems to be missing entirely.

<raid> <id>81</id> <name>Petrisis Fleshcrafter Raid</name> <levels>26</levels> <commander>26250</commander><!-- Petrisis Fleshcrafter --> <fortress_card id="18974"/> <!--Facebloom--> <fortress_card id="18984"/> <!--Life Reservoir--> <deck> <card_pool amount="10"> <!-- Vinds --> <card replicates="2">64654</card><!--Fleshcrafter's Butcher--> <card replicates="2">64664</card><!--Petrisis' Crackshot--> <card replicates="2">64674</card><!--Fleshcrafter's Husk--> <card replicates="2">64684</card><!--Petrisis' Grafter--> <!-- <card replicates="2">64694</card><!--Petrisis' Scion--> <!-- Mythics --> <card replicates="1">64704</card><!--Perfected Elemir--> <card replicates="1">64714</card><!--Perfected Tarantalus--> <card replicates="1">64724</card><!--Perfected Salg--> </card_pool> </deck> </raid>

#### v3.2.0 - Add Fix 'enhance-early': With this fix activiated all enhance skills trigger before the first unit is played. This is the current behaviour of the game, but the official skill description says that some enhances happen at different times. Since this doesn't seem to get fixed I added a new category of flags namely "fixes". By default I will enable recommended fixes until they get corrected, but you can choose what to activate through flags: * 'no-fix': disables all fixes * 'fix-enhance-early': enables this fix * 'fix-???': enables other future fixes 'fix-enhance-early' is (by now) active by default.

> *Originally posted by **[DR_F3LL](/forums/2468/topics/920187?page=14#13312782)**:* > #### v3.2.0 - Add Fix 'enhance-early': > > With this fix activiated all enhance skills trigger before the first unit is played. > This is the current behaviour of the game, but the official skill description says that some enhances happen at different times. > > Since this doesn't seem to get fixed I added a new category of flags namely "fixes". > By default I will enable recommended fixes until they get corrected, but you can choose what to activate through flags: > > * 'no-fix': disables all fixes > * 'fix-enhance-early': enables this fix > * 'fix-???': enables other future fixes > > 'fix-enhance-early' is (by now) active by default. > Thanks for keeping it updated!)

#### v3.2.1 With 'fix-revenge-on-death' or by default **On Death (harmful activation skill) works against ALLIED units** now like in-game. In case one wants just one fix ``` ./tuo [...] no-fix fix-enhance-early ``` will only activate fix-enhance-early.

Thank you, thank you, thank you! many thanks, DR_F3LL!