- Mastering Unity 2017 Game Development with C#(Second Edition)
- Alan Thorn
- 188字
- 2021-07-02 15:38:36
Objective and feedback
Always remember the player objective when designing--the goal to be reached by the player during gameplay; this may be reaching a specific location, defeating a specific enemy, achieving a financial target, or something else. Most players like to feel successful, like they're moving toward that goal. During gameplay, they'll typically look for both overt signs of progress (such as mission complete popups and victory sound effects) as well as convert signs of progress, such as meeting a friendly unit that offers to help you reach a location, open a hitherto locked door, find the murder weapon in a mystery game, or catch sight of the destination from a high vantage point (such as a watch tower), among others. It's important to reach a balance between these two types of signs or feedback, and to steadily provide them in the level through props, characters, dialog, architecture, special effects, and anything else you can put into a level. If the level features little feedback, the player loses interest, and feels defeated or bored. If the level features too much feedback, the player feels frustrated and overwhelmed.
- ASP.NET Core:Cloud-ready,Enterprise Web Application Development
- 程序員面試白皮書
- R語言數據分析從入門到精通
- Java 9 Concurrency Cookbook(Second Edition)
- 無代碼編程:用云表搭建企業數字化管理平臺
- Python從菜鳥到高手(第2版)
- Building Mobile Applications Using Kendo UI Mobile and ASP.NET Web API
- Java軟件開發基礎
- Python機器學習經典實例
- 批調度與網絡問題的組合算法
- Scratch3.0趣味編程動手玩:比賽訓練營
- 計算機應用技能實訓教程
- R語言數據挖掘:實用項目解析
- 軟件工程與UML案例解析(第三版)
- 零基礎C#學習筆記