Custom Data Events for Player Behavior

Loading...

来自 Unity 的课程

Unity Services Implementation

个评分

Unity

Unity Services Implementation

个评分

课程 5（共 5 门，Specialization Unity Expert Gameplay Programmer Certification Preparation）

Welcome to Unity Services Implementation, the final course in Unity's Gameplay Programming Specialization! This course is exam preparation for Unity's Expert Gameplay Programmer Certification Exam. This course will challenge you with a series of realistic programming problems in Unity video-game projects, inspired by one or more of the topics covered in the Expert Gameplay Programmer Exam. Throughout this course, you will learn Unity Services Implementation techniques, including: streamlining your project management with Unity Cloud Build, monetization with Unity Ads and in-app purchases, and Unity Analytics. By the end of this course, you will implement in-app purchases for a 3D "Dual-Stick Survivor" game project. This is an advanced-level course, intended for industry game developers or very experienced Unity enthusiasts who are looking to “level-up” their gameplay programming and implementation strategies. To succeed in this courses, you should have at least 2-3 years of experience developing games with Unity. You should be familiar with the full-game lifecycle (working from early concept to launch), creating and working with Prefabs, understanding game asset and animation pipelines, and have some experience with Unity Services. You should also have advanced programming skills, particularly in the C# language.

从本节课中

Unity Analytics

Broadband has radically altered the way our world works, and this unparalleled access to information is available to you as a game developer. Gone are the days when a game is released and assumed unmodifiable. Player feedback can be gathered, analyzed, and used to improve the gameplay experience. Unity Analytics makes the process easy, and having a solid understanding of it will help you take full advantage of all that information. This week you’ll begin collecting data on your game using Unity Analytics. You’ll have to go back to the GDD to see how the game is intended to be experienced and set up data events to verify how players are doing. Unity’s Heatmap and Dashboard will give you quick access to how players are playing your game, and for a more in-depth look you can look at the raw data. Informed modifications to improve performance and experience will be your ultimate goal.

Unity Analytics1:35

Translating GDD Level Design to Data Collection Points2:07

Custom Data Events for Player Behavior4:47

与讲师见面

Unity Technologies
Dustin Carroll
Senior Technical Artist & Adjunct Instructor
Computing & Digital Media

Hope you found plenty of opportunity to use analytic events.

They can give you great insight into the way that your game is being played.

While they included analytic events are

fantastic and they give you great insight into your game,

there are times when you want to know simply more about what's happening there.

Take for example player death.

It's fantastic to know that it happened and how often it's happening,

but there's probably a lot more that we want to know.

We can create a custom event that passes along a lot more information.

So, instead of game over,

I'm going to do analytic event and a custom event.

Keep in mind any of your custom events should not have a name that starts with unity.

This is a reserved word for the standard Unity analytical events.

Now, after I have a name for it,

I'm going to create a new dictionary.

Into this, we're going to pass a string and an object.

You may recall from course one that objects make up just about everything in the game.

So, we can pass in almost anything that we want to write here.

This gives us a lot of possibilities of passing along information.

For example, we're going to put in a custom event using custom.

Now, in order to put in this event,

first I'm going to give it a name.

This will be player death,

and then we're going to pass in

a dictionary with a key that is a string and an object for the value.

The very first thing I'm going to put in is a phrase for this value.

We'll call this player position,

and we'll pass it in this transform position.

Knowing this will have an idea as to where on the maps our players are dying.

If they keep on dying in the same spot,

we'll maybe figure out that either this is

a popular spot to defend yourself or maybe it looks good,

but it's actually kind of a trap.

Now, if the deaths are spread out maybe that's

an indication that there's no good spot to make a defense in our game.

We'll let the designers figure out what they want to do with this information.

We're just here to collect it.

Let's also figure out how long the player has been playing for.

By adding in the amount of time that the player has been in this current level,

maybe we can figure out if they died very quickly or

if they made a pretty good stand of it.

Now with these in place, we're going to play the game

and see our data being collected in real time.

All I have to do is manage to die,

and there we go.

Now, if we pause the game over and our analytics window,

we can see that custom event came up.

We've got the event player death.

We have the parameters.

We can see exactly where he was when he died,

and how long that load been running.

Took me just under 14 seconds to die.

If we go over to the analytics dashboard,

we can have a look at these as well, and here we go.

Here's all the events that I've had in this game since I started collecting events.

Now, the top we have player death and we have the exact same information we had before.

We can see when the app started running and when it was called to start.

We can also see previous play sessions and when those were stopped.

Now, there's a limitation to the number of parameters that we can send it with any event.

That being 10.

The number of characters you can use across

all the different strings that we put into these parameters is 500,

and we can only send a maximum of 100 events per user per hour using this method.

Even with these limitations which are actually all that better,

we can get a lot of information.

Go ahead and set up a custom events and start figuring out what you might want to know.

Maybe look into how enemies are dying or maybe when

the fairy circles are being activated. Have fun with it.

探索我们的目录

免费加入并获得个性化推荐、更新和优惠。

Coursera 致力于普及全世界最好的教育，它与全球一流大学和机构合作提供在线课程。

© 2018 Coursera Inc. 保留所有权利。

通过 App Store 下载

通过 Google Play 获取