跟讀練習: A Beginners Guide to Game Development | Indie Game Dev Tutorial - 通過影片學習英語口語
選擇練習模式
每種模式都會開啟全屏練習室。
166 句
如果句子過短或過長,請點選 Edit 進行調整。
1
Making games can be extremely daunting, especially if you don't know where to start.
2
Many of us have dream games, an idea we long to make that we're so passionate about.
3
Some of us just want to make small games for fun, and that's really cool too.
4
Regardless of what you want to do, you have to learn how to make games in the first place.
5
That's why I put this video together, The Beginner's Guide to Game Development.
6
This video is something of a guide and a roadmap, so it'll be a bit dense at times,
7
but just because I'm going over a lot in this video doesn't mean you have to learn it all at once, or anything in particular really.
8
And don't overwork yourself trying to master all of it either.
9
Game development takes time and patience, so it's best you give yourself the time you need to actually learn and not burn yourself out.
10
In the description, I've gotten some links to tools and resources I think could be helpful, and a link to my Discord server for game developers.
11
Like and subscribe if you enjoy the video.
12
So, game engine or framework.
13
To actually make a game, you'll need something to make it with.
14
This is where you can decide to use an engine or framework.
15
For the purposes of this video, I'll assume you'll be using an engine because most beginners wouldn't want to
16
or need to use a framework
17
but i'll still go over both a game engine is a piece of software
18
that acts like an all -in -one package for most of your game development needs
19
this means it'll give you most of the necessities
20
you'll need for making a game such as a place to
21
write your code a system for building user interfaces a system for running
22
and compiling your project and usually your engine will give you some things
23
that are really nice to have such as a built -in
24
physics implementation collision detection a way to manage your projects
25
so on and so forth
26
but essentially it'll give you most of the building blocks you'll need to make your games on the other hand,
27
a framework is like a set of tools.
28
Most frameworks give you some way to render things to the screen, manipulate the window, doing CRUD operations , and other essential functions for your game,
29
such as providing audio and input libraries.
30
Frameworks give you much, much more control of your project, at the cost of not really giving you much direction in how to make your project,
31
if that makes sense.
32
If you're more technically inclined and you like programming, frameworks like Raylib, Lev2D, Pygame, and Bevy may be worth looking into.
33
One thing new developers get stuck on is choosing what engine to use, and honestly, it doesn't really matter.
34
No matter what engine you choose, you can still basically make any game you want.
35
Of course, making certain types of games and specific engines can be easier.
36
For example, if you want to make a visual novel or a narratively driven game,
37
RenPy may be what you want to use because it's specifically made for those kind of games.
38
But to reiterate my point, regardless of if you choose
39
Unity, Godot, Pygame, Unreal, or Relip, it doesn't really matter too much.
40
All that matters is that you're comfortable with the tools you're using.
41
As you become more comfortable with your engine of choice, you'll start to develop a workflow that works for you.
42
Thankfully, there's a ton of great engines available, making gaming development really accessible.
43
The only issue is that since there's so many, deciding can be kind of difficult if you don't know where to begin,
44
so I'll quickly give you an overview of some popular engines to help you narrow down your choice.
45
But just remember, you can still make any game in nearly any engine.
46
If you're looking to make both 2D and 3D games, Godot, Unity, and Unreal are good picks.
47
Game Maker is also good you're only interested in making 2d games there are also a few engines
48
that don't require you to code either such as unreal
49
which has a pretty robust visual scripting system called blueprints there's also construct 3
50
which is a no code 2d engine with some 3d capabilities as i mentioned earlier there's also renpi
51
which can be used for making visual novels
52
and of course there's the ever beloved rpg maker series of engines at this point
53
if you've chosen an engine
54
and are ready to get started making things the best thing
55
you can do now is to get familiar with your engine take
56
Take some time to just fiddle around with your engine.
57
Open random menus, see what everything does, maybe watch tutorials on your engine so you can see how it's used and become familiarized with its interfaces.
58
At this point, you want to be able to navigate your engine without too much trouble
59
and know where most of the important things are, like the inspector, your console, where your assets go, project settings,
60
and etc. Around when you're becoming familiar with your engine is
61
when you want to learn how to code inside of your engine, if it allows for that.
62
This will be different for each engine out there.
63
For example, Gido has its own language called GDScript that's similar to something like
64
Python, and the engine includes a code editor inside of the engine.
65
Unity uses C Sharp and requires to use an outside code editor, something like Visual Studio or Sublime.
66
Thankfully, because of how popular most of these engines are, it's not too hard to find programming tutorials for any of them,
67
but here's an overview of some programming basics anyways to give you a somewhere to start.
68
Variables are containers for our information.
69
We can create them, put information inside of them, edit that information, and read it.
70
Data types are the types of variables we can use.
71
For example, an integer is a variable that represents a whole number, a string is a variable that represents text,
72
and an array generally represents a list of other variables.
73
Then there are conditionals.
74
These allow us to control the flow of our code.
75
For example, if we make a variable called money, we can check to see if money is greater than some value.
76
If so, we can give the player an item.
77
Then there are loops.
78
Loops do tasks for us over and over again, such as looping over a list to see the constants of it and compare it to something.
79
Finally, there are functions.
80
Functions are just blocks of code that we can create and use at any time.
81
We mainly use them so we don't have to repeat ourselves when we're coding.
82
We can give functions values to use inside of their code.
83
These are called parameters.
84
And functions can also give us back values when they're done running.
85
These are called return values.
86
And that's pretty much everything you need to know to start programming your games.
87
That overview was pretty brief and bare -bones,
88
so make sure to go out on your own and find tutorials that fit your engine and use cases.
89
Art, sound, and music are really important to the feel and style of your game.
90
Unfortunately, I can't really cover everything about them here since they're all pretty big topics
91
and they're all pretty different from each other as well.
92
But I can give some advice.
93
Keep in mind, you don't have to make your own assets.
94
And honestly, if you're looking to just make fun games first, there's nothing wrong with just using programmer art and placeholder assets.
95
The fun in your game is about the gameplay, not the assets.
96
When it comes to sourcing assets, there are tons of freely available assets online.
97
Slides like H .I .O and Open Game Art have tons of great stuff available.
98
Just always remember to check the licenses of everything you use.
99
As for learning how to create your own assets, I will generalize here, but you'll just have to be consistent.
100
Creating assets, your art, sound, and music are all skills you can learn at enough time in practice.
101
So as long as you're patient with yourself and consistent, you can improve your skills over time.
102
So you've chosen an engine, you've messed with it here and there, but you actually want to start making stuff.
103
At this point, I would recommend to make extremely simple projects.
104
When I was starting out, I would make really basic platformers or make projects with singular mechanics like figuring out how to make bullets,
105
how to make enemies, inventory systems, etc. Some developers would also recommend recreating classic games such as Pong or Space Invaders,
106
and I do think this is a good idea.
107
I encourage you to look at plenty of tutorials at this point too, but it is critical to avoid something called tutorial hell.
108
Tutorial hell is when you get caught up watching tutorials believing you're learning instead of actually making projects.
109
Game development is a very hands -on medium and you'll learn best by actually making things.
110
Tutorials definitely have their place in your learning process, but you should learn to use them effectively to learn
111
and refine your skills and not use them as a replacement for actually gaining experience.
112
Simply put, you can watch someone do something 100 times over, but unless you do it yourself and put it into practice,
113
you've only learned how to watch someone else do it.
114
At this time, you may have already made a small game
115
or be making progress towards or planning your first small game again really really small
116
if so that's great however you may have had some doubts about your abilities to learn game development
117
or you could be unhappy with what you've made so far
118
and that's okay game development is extremely difficult
119
and you'll have moments where you feel like giving up
120
but that's okay there's no rush or pressure to improve
121
and it's completely healthy and encouraged to take breaks from game development to avoid burnout
122
and to refresh yourself getting feedback on your work is extremely important
123
but it can be hard to get it when you work alone.
124
I encourage you to join communities where you can share your work with others, or maybe even work together with like -minded developers.
125
Game jams are great for this, as they allow you to quickly make games and get them out into the world for others to see.
126
It can be scary to join your first game jam, but I promise you'll meet many,
127
many friendly developers who are just as passionate about their games as you are about yours.
128
When I first started out, I enjoyed doing mini jam, even though I didn't finish many of my submissions.
129
Along with the previous advice, learning how to finish games is a skill all of its own.
130
Again, jams are great for this, but honestly, I recommend keeping things really small and releasing whatever you can on sites like itch .io,
131
gamejolt, or even just sharing them directly with friends and family.
132
It's important not to get stuck trying to perfect every detail of your project,
133
and just accept that you'll have to let it go at some point.
134
There's a quote that goes something like, art is never finished, only abandoned, and I feel like it's something to really keep in mind,
135
especially when you're first starting out with game development.
136
And that's basically it.
137
This guide is meant as a way to help you get your foot in the door, so as I mentioned at the start of the video,
138
make sure to check out the links and resources in the description.
139
Thank you so much for watching,
140
and I hope this video helped. about that.
141
I believe it has 36 .6 thousand views at the moment, and I just hit a thousand subscribers this morning.
142
Um, so thank all of you.
143
Thanks to all of you.
144
I really appreciate it.
145
Um, I wanted to thank all my supporters again, of course, currently just
146
Eye of Hell.
147
I appreciate your monthly, uh, supportership?
148
Membership?
149
Yeah, monthly membership a lot.
150
It really does mean a lot to me.
151
I'd like to find a way to make my videos a
152
little bit more sustainable for me to edit even though i do like the style of videos
153
i'm making right now um
154
i definitely need to find a way to make them easier to edit especially the longer ones like this one
155
because i don't think i want to make more videos
156
that are this intensive for me
157
because i'm not really a very good editor at the moment maybe in the future
158
when i get more skills i can do something like this again
159
but yeah um i also don't know what my next video should be about i haven't really planned this forehead
160
so suggestions are very much appreciated
161
but thanks again for this super positive response to the previous video
162
that was amazing um i appreciate it so much
163
and yeah no that's it i think thank you so much for watching and i'll see you in the next video
164
strawberry lemonade tea lemonade green tea oh my god what are we doing here I didn't know it bound.
165
I didn't know it bound.
166
I never used this item.
FOR YOU
推薦影片
本課的詞彙與口語要點
這節口語課以影片“A Beginners Guide to Game Development”為素材。 影片中反覆出現的詞有:engine, code, learn, project。 這段影片共有 166 個句子、2261 個單詞可供跟讀。 講話部分時長為 10:21。 說話人語速較快,每分鐘約 218 個詞,會出現較多連讀和弱讀。 85% 的單詞屬於英語最常用的 3,000 詞,其餘的詞建議在練習前先學一下。
影片中的重點詞彙
影片中 15 個值得學習的單詞,附發音和釋義:
| 單詞 | 發音 | 釋義 |
|---|---|---|
| asset 名詞 | /ˈæsɛt/ | 資產 /資產 |
| tutorial 名詞 | /ˌtjuːˈtɔːɹɪəl/ | 輔導 /輔導, 教程 |
| framework 名詞 | /ˈfɹeɪm.wɜːk/ | 骨架, 框架 |
| skill 名詞 | /skɪl/ | 技巧, 技能 |
| encourage 動詞 | /ɪnˈkʌɹ.ɪd͡ʒ/ | 鼓勵 /鼓勵, 激勵 /激勵 |
| edit 動詞 | /ˈɛdɪt/ | 編輯 /編輯 |
| loop 名詞 | /luːp/ | 圈, 環 /環 |
| overview 名詞 | /ˈoʊ.vɚˌvjuː/ | 概觀 /概觀 |
| unreal 形容詞 | /ʌnˈɹi.əl/ | 不真實的 /不真實的 |
| consistent 形容詞 | /kənˈsɪs.tənt/ | 一貫的 /一貫的 |
| membership 名詞 | 會籍 /會籍, 會員身份 /會員身份 | |
| ton 名詞 | /tʌn/ | 噸 /噸, 公噸 /公噸 |
| maker 名詞 | /ˈmeɪk.ɚ/ | 製造者 /製造者 |
| jam 名詞 | /ˈd͡ʒæm/ | 果醬 /果醬 |
| interface 名詞 | /ˈɪn(t)ɚˌfeɪs/ | 介面 |
影片中出現的短語動詞
| 單詞 | 釋義 |
|---|---|
| check out 動詞 | 退房 |
| figure out 動詞 | 弄清楚 |
| give up 動詞 | 投案, 自首 |
影片中的語法
說話人最常用的結構,並附上影片中的原話:
| 結構 | 影片中的用法 |
|---|---|
| 現在完成時 have/has + 過去分詞 — 過去發生但與現在仍有關聯的事 | I've gotten · you've chosen · you've only learned |
| 被動語態 be + 過去分詞 — 強調發生了什麼,而不是誰做的 | can be used · are called · is meant |
需要注意的發音
說話人用了 59 次縮略和弱讀形式,例如 you'll, you're, don't。請按聽到的簡短形式來說。
- “sh” 和 “zh” 音: passionate /ˈpæʃənɪt/, rush /ɹʌʃ/, essentially /ɪˈsɛnʃəli/, implementation /ˌɪmplɪmənˈteɪʃən/, suggestion /səˈd͡ʒɛst.ʃən/
- 長單詞——注意重音位置: developer /dɪˈvɛləpɚ/, essentially /ɪˈsɛnʃəli/, implementation /ˌɪmplɪmənˈteɪʃən/, sustainable /səˈsteɪnəbəl/, accessible /əkˈsɛs.ɪ.bəl/
中文母語者容易讀錯的音:
- /v/ — 不要讀成 /w/,上齒輕觸下唇: variable [ˈvæɹ.i.ə.bl̩], developer /dɪˈvɛləpɚ/, overview /ˈoʊ.vɚˌvjuː/, server /ˈsɝvɚ/, beloved /bɪˈlʌvd/
- 詞尾子音 — 要讀清楚,後面不要加母音: asset /ˈæsɛt/, framework /ˈfɹeɪm.wɜːk/, encourage /ɪnˈkʌɹ.ɪd͡ʒ/, edit /ˈɛdɪt/, loop /luːp/
- /r/ 和 /l/ 的區別: tutorial /ˌtjuːˈtɔːɹɪəl/, variable [ˈvæɹ.i.ə.bl̩], unreal /ʌnˈɹi.əl/, regardless /ɹɪˈɡɑɹd.lɪs/, replacement /ɹɪˈpleɪsmənt/
如何用這段影片練習
- 先完整聽一遍影片,不要開口,記下不認識的單詞。
- 先用 0.75 倍速逐句跟讀,熟練之後再回到正常速度。
- 錄下自己的聲音並與原聲對比,特別注意 asset, tutorial, framework 這類單詞。
什麼是跟讀法?
跟讀法 (Shadowing) 是一種有科學依據的語言學習技巧,最初開發用於專業口譯員的培訓,並由多語言者Alexander Arguelles博士普及。這個方法簡單而強大:您在聽英語母語原聲的同時立即大聲重複——就像是一個延遲1-2秒緊跟說話者的影子。與被動聽力或語法練習不同,跟讀法強迫您的大腦和口腔肌肉同時處理並模模擬實的講話模式。研究表明它能顯著提高發音準確性,語調,節奏,連讀,聽力理解和口語流利度——使其成為雅思口語備考和真實英語交流最有效的方法之一。












