Name: バージョン2の変更点 - Python AI in StarCraft II チュートリアル p.13 (Version 2 Changes - Python AI in StarCraft II tutorial p.13)
Uploaded: 2021-01-14T12:27:45.000Z
Duration: 9 min
Description: VoiceTubeの動画で発音を聞きながら英語表現を覚えよう！学べる英語：

Everybody welcome to part 13 of our A I and Starcraft two with python tutorial.

What we're gonna be doing is kind of going over.

I'm gonna refer to his kind of stage two of our neural network development here.

So the first test proved to be at least somewhat successful where the neural network was at least better than random in the four choices at beating the medium leveled.

Aye, aye, that's like built into the game.

So now what we want to do is add complexity of the A I and hopefully creating a I that's a little more impressive than the one that we just made and then see if we can operate on top of that A.

So, like the last one, we create an aye Aye.

The next step would be to use that ai ai again.

Or media, May I or or itself or all three of those things and see, Can we improve that a.

I even further through that method of training, because if we can't well, then I don't know what we're doing here.

We gotta, like, totally regroup and figure out what to do next.

Apologies Now, Um, So let's talk about some of the things that were wrong here.

Some of things I want to change, moving forward and all that.

So first of all the names here, Uh, Okay.

Um, in fact, we're probably going to fix it, so I'm gonna use it.

Um, anyways, just No, I made that mistake.

Um, and then also someone point out the random variance here.

Um, using the enemy start location doesn't make any sense.

We should be using variants of the whole entire game map size, because depending on where the enemy's start location is, that's gonna cause the variance to be quite significantly different.

No more kind of estimation, we can get much, much closer that comes in for more psychiatrists.

I don't know how to pronounce that, but anyway, um, the next thing is, rather than same person to rather arbitrarily sizing our units.

Ah, when we draw them, we can actually just use the unit's radius, which makes a whole lot more sense.

So as it stands right now, we weren't scouting until after four minutes.

So what we want to do is send at least a single worker out to scout within that four minute range and continue doing that until we've got the observers.

And then once we have an observer, we don't just want one.

We should have many observers, and we really need to cover all the expansion areas.

One of the other suggestions was that you have observers along the main attack route.

We I might do that in the next phase, but in this one, I don't really think I'm gonna bother with that.

But we definitely want to have at least the bases covered, Um, and then once that scouting logic is fixed, we should be able to end the games on time.

So anyways, that's what we're going to be working towards and let's get into it.

The code is from part nine of this tutorial, Siri's.

So if you don't have that, go back to part nine.

And actually, I'm pretty sure in the techie and the text version that tutorial.

I have the starting code copy and paste it anyways.

Okay, so the first thing is, let's fix the time.

That's a real easy, quick one to fix in this video.

I'm gonna comment out self obliteration because I want to catch any other times we use self doubt.

We also could comment out iterations per minute again.

We shouldn't be using it anymore now that we know the time.

You want to say that equals self dot state dot game loop divided by a 22.4.

I guess that's how many ticks anyways, um, and then I'm gonna do That's gonna be the number of seconds, and I'm gonna divide that by 60.

So it's in minutes so self that time is in minutes because that's kind of the way we've been thinking this whole time, so I want to retain that minutes field.

So now we're gonna do is just search for federation and basically fix all these.

Now, the expand logic is no longer going to take really place here.

But, uh, like, it's not gonna need this logic.

It's gonna be chosen by the aye aye itself.

Um, but we'll just do self dot time I'm gonna say, divided by two.

Time self That time, Unistar Gates is less than Celtic time.

Uh, this one again, self dot time is greater than do something after, and then the random range is right here.

I I'm not really sure what to call that, but, um, in this case, we would want to await a random dot rand range of like, I don't know, somewhere between seven and 100 seconds.

But keep in mind, self, that time is in minutes.

So we want to go ahead and divide that by 100 so that's, uh, you know, up to not seconds.

Um, basically, you know, 7% of a minute to 100% of a minute.

That should be all the changes we need to make there.

And besides that, the only other thing I want to bring up is I'm just gonna bring over the text based version of tutorial here.

So these are the choices that we're going to make as time goes on.

So we're going to go from four choices to 14 choices.

Um, scout, as in the Observer Z lotta's in the fighter gateways and the thing that builds Z lots and is required for many other things.

Ray Stocker Probe Assimilate er to get gas Star Gate pylon nexus or defendant Excess.