Percival18
2015-10-07T09:23:04Z
Originally Posted by: Rhonindex86 

It may have just been because something in an older version of YGOPRO was to blame, however, I encountered a virus detected by my norton antivirus described as WS.reputation1 or something like that. I've encountered the same before related to another program or modification to one but just wanted to let you know. As for now, I have deleted and am reinstalling the newest update clean install...


While unfortunate, what does this have to do with the AI though?
Urban-Shadow
2015-10-08T22:30:56Z
I keep getting this error every time I play against the ai

ai/mod/AIHelperFunction2. lua:1979: attempt to call method 'GetSequence' (a nil value)

also I just played against AI_Mermail, the AI went first and it was able to attack on turn one
Snarky
  • Snarky
  • Advanced Member Topic Starter
2015-10-08T23:28:42Z
Originally Posted by: Urban-Shadow 

I keep getting this error every time I play against the ai

ai/mod/AIHelperFunction2. lua:1979: attempt to call method 'GetSequence' (a nil value)

also I just played against AI_Mermail, the AI went first and it was able to attack on turn one



Which version of YGOPro and the AI script are you playing? The attacking first turn most likely was a direct result of the error message.

The referenced function will be replaced in the next version of YGOPro. A better alternative will be implemented, which I plan on using. Hopefully, this will fix your problems as well, but it might take a while, until that update is released.
Urban-Shadow
2015-10-09T04:17:06Z
Originally Posted by: Snarky 

Originally Posted by: Urban-Shadow 

I keep getting this error every time I play against the ai

ai/mod/AIHelperFunction2. lua:1979: attempt to call method 'GetSequence' (a nil value)

also I just played against AI_Mermail, the AI went first and it was able to attack on turn one



Which version of YGOPro and the AI script are you playing? The attacking first turn most likely was a direct result of the error message.

The referenced function will be replaced in the next version of YGOPro. A better alternative will be implemented, which I plan on using. Hopefully, this will fix your problems as well, but it might take a while, until that update is released.




I'm using the latest version, it was a fresh install and the AI Script 0.31b

the 1979 error is something that happen at least once a duel and is usually with something in the graveyard, activating effects or special summoning.
kenpazaraki
2015-10-09T22:21:59Z
I finally managed to get screenshots for the bug that prevents the activation of any card.

http://imgur.com/a/s3fOp 
Snarky
  • Snarky
  • Advanced Member Topic Starter
2015-10-12T11:24:55Z
This should be related to the issue Percy and I are currently investigating, which occasionally causes the client to crash for subsequent duels. Do you happen to know, if this was the first game of the session? Or did you finish a duel successfully before and started a new game without restarting the client?
kenpazaraki
2015-10-12T17:25:22Z
I'm not sure, but it probably wasn't the first game.
Snarky
  • Snarky
  • Advanced Member Topic Starter
2015-10-18T18:38:26Z
Updated for 0.31c 
Snarky
  • Snarky
  • Advanced Member Topic Starter
2015-10-30T11:56:17Z
Updated for 0.32b 
kenpazaraki
2015-11-03T19:32:56Z
Thank you for the new decks! I've noticed a problem with Traptrix Rafflesia. Apparently it tries to use Treacherous Trap Hole no matter what the field looks like (like destroying itself and the AI's Infinity).
Snarky
  • Snarky
  • Advanced Member Topic Starter
2015-11-08T08:45:23Z
Updated for 0.32c .
dkates
2015-11-11T12:34:42Z
Just a single issue to report, at least for now. In the Constellars deck, in prior versions, the AI would go into Constellar Pleiades and keep it as Pleiades until it had used up its Materials, then upgrade it to Ptolemy M7 after that. In most situations, that's the correct play. Currently, though, it will go into Pleiades, then immediately go into M7.
Snarky
  • Snarky
  • Advanced Member Topic Starter
2015-11-11T12:53:46Z
Thanks for the report. I fixed the issue on my end, so it will be gone for the next version.
dkates
2015-11-14T13:00:37Z
Found another one, which should hopefully be easy to fix. Masked HERO Koga tends to target the AI's monsters, instead of the player's. I can only think of one situation offhand where the AI should have Masked HERO Koga target one of the AI's monsters. and it's a pretty niche play -- if the monster in question is about to be hit by something that cares about or references the monster's ATK, such as Bottomless Trap Hole or Magic Cylinder. The way it's using it, the AI is clearly activating Koga in situations where it intends to target one of the player's monsters, then picking the wrong target.
Chaosmage1
2015-12-27T16:51:18Z
not sure if Anyone brought it up, but in a match i had with the Kozmo AI it used BOTH it's solem notices on it's OWN monster effects: the first was one it's own kozmo strawman when it activated it's effect to retrieve a banished monster. and the second was in response to when i triggered the effect of it's kozmo sliprider by destroying it in battle...and this didn't help it at all, it in fact destroyed any chance it had of beating me. just thought i'd bring this up if it wasn't already.
dkates
2015-12-27T22:45:14Z
Here's one which might be a bit tricky to fix, depending on what tools are available. The AI often seems to "forget" things about face-down cards that it has previously seen. The easiest-to-describe example of this is the AI flipping one of the player's monsters facedown (with Book of Moon, Ghostrick Jackfrost, or whatever), then attacking it with a monster that's too weak (and that does not have an effect to justify the attack), resulting in the AI needlessly taking recoil damage. For a human player, mousing over a face-down card that has been previously revealed will show the card info, so clearly the game has some way to flag face-down cards as known, but I have no idea whether the AI has any way to "see" those flags.

And speaking of issues with attack logic and the like, it seems like the AI occasionally has issues with using stat modifiers properly when it's attacking a Defense Position monster (even a face-up one). I can't be sure, but it seems as if, in these situations, the AI is checking the ATK of the player's monster when deciding whether to use its stat modifiers (such as Forbidden Chalice in the Qlis, but there may be other examples), at the point(s) where it should be checking the DEF.
joashp
2016-01-19T08:42:45Z
Apparently, about the deck out issue, I found out that a mandatory draw caused by card effects such as Supply Squad, Shared Ride or Maxx "C" (and the likes), forcing opponent to draw outside his/her turn while its deck is empty will cause the AI to lose.

I hope the deck out issue will be fixed, as far as I know it was working before the new updates. I just recently played, so I was unaware of the issue. Thanks again for the great update and more powers to the YGOPRO developers.
YGOSmurf
2016-02-09T23:54:58Z
With regards to the experiemental version of the Ai_Kozmo ,
the bot activated a Max C on its first turn, being the first turn of the game. (bot won coin toss, summoned kozmo goodwitch, activated Maxx C, used goodwitch... and so on.

I am sure that using Maxx C in that situation may on some level be useful but really it seems like the bot just wasted a perfectly good card, especially sense if it would had saved it for my turn it would have gave me the maxx c challenge with 5 special summons...

Thought I'd mention it. Great work by the way! Hope more new Ai's will come out! All the love you way.
Snarky
  • Snarky
  • Advanced Member Topic Starter
2016-02-12T13:59:37Z
updated for 0.33a

Originally Posted by: YGOSmurf 

With regards to the experiemental version of the Ai_Kozmo ,
the bot activated a Max C on its first turn, being the first turn of the game. (bot won coin toss, summoned kozmo goodwitch, activated Maxx C, used goodwitch... and so on.



Missed this post, sorry.

Honestly, I have no idea, what is going on with this issue. I keep getting reports, that Maxx C is used incorrectly for all the decks, that decide to go second, if they have the choice (including Harpie, Blackwing, Kozmo), yet I am unable to reproduce the issue on my end.

Wait... the bot won the coin toss, but chose to go first? That is a new piece of information. Which platform are you playing on?

Quote:


I am sure that using Maxx C in that situation may on some level be useful but really it seems like the bot just wasted a perfectly good card, especially sense if it would had saved it for my turn it would have gave me the maxx c challenge with 5 special summons...



Yeah, its totally meta, meant to discourage an opposing Psyframe player to use his negation effects :)
Nah, its a bug, of course.
YGOSmurf
2016-02-16T01:03:02Z
Originally Posted by: Snarky 

updated for 0.33a

Wait... the bot won the coin toss, but chose to go first? That is a new piece of information. Which platform are you playing on?



When you say platform you mean? I am on windows 8 Laptop(really doubt that is what you meant), I used the classic/most updated version of YGOpro provided from this site.

And yeah the bot won the coin toss*Edit* won the rock/paper/scissors, chose first, played a card and then was like check out this Maxx C in the grave. Ain't it pertty? lol