23

첫 번째 게임을 만들면서 배운 것들

Embed Size (px)

Citation preview

things I learned through my first game

Downwell• ¥360 on AppStore,

¥298 on Steam

• no IAP

• Metascore 91 for iOS, 84 for PC

• sold over 10k~ units

Game a week

Rami Ismail (of Vlambeer)

Game a week: Getting Experienced at Failure

an article on gamasutra.com

• Make 1 game per week

• No revisiting the same idea

• Try to make varied games

Basic rules:

• Ideas that seem good on paper often turn out to be terrible

• Better ideas emerge through development

Utilizing Twitter

• #gamedev #indiedev etc

• Near instant feedback with Likes and Retweets

• Get to see other games in development

• You never know who may end up seeing your tweet!

Going to local meetup events

Importance of playtesting

• Take their feedback, but don’t take their suggestions too seriously

• The fact that they felt frustrated about a certain aspect of the game, is a fact.

• Their suggestions on how to improve the game, are not facts - it’s only their preference.

Working with a publisher

My case (w/ Devolver Digital)

• Development fund (i.e. cost of living for around 1 year, flight tickets & hotels etc for exhibiting at events, etc etc)

• Marketing

• The brand

The language barrier

• Latest documents for game dev tools, tutorials, forums, support are in English

• Many useful game dev related knowledge are in English (eg. GDC talks, gamasutra articles etc)

• There are big game dev communities (eg. TIG source) using English

Thank you!