[FEATURE] Add tutorial and in-game hints to guide new users

[CherryWYK]

Current Issues This game only shows instructions and game tips/hints once before playing the game. If the users does not pay attention and skip the instructions or game tips, they may fail the game and have poor user experience.

Suggested Enhancement -Include a comprehensive tutorial that guides new users through the game mechanics, rules, and objectives. This will help users understand the limitations and constraints of the game and provide them with the necessary information to make informed decisions.

-Provide in-game tips or hints that remind users of their progress and encourage them to play within the established limits.

[ran-2012]

New players may not know there are some mechanics such as staff skill level and degradation of QA and Deploy. This might be very helpful.

[lhzhzl]

Agree. At the beginning of week 3, there are automating test cases, acquiring users, upgrading deployment environment in the game objectives. Comparing with previous objectives, automating test cases and upgrading deployment environment are new kinds of game objectives. The Test Automation, Upgrade QA Environment and Upgrade Deployment Environment can be introduced to new users when the new kinds of objectives are introduced.

[Alainyan1]

Agreed. Tutorials are important. They help the beginners master the gameplay, let them know what their game mission is, understand some basic elements of the game, and provide them with help in the early stages of the game. Here are some of my thoughts on how to design a tutorial:

1. Before the game starts, we can introduce the detail of every staff to the players instead of having the players busy looking for the most suitable development candidates after the game starts. This is like real-life development. We always first understand the staff's abilities and assign them the most appropriate tasks to improve development efficiency.
2. Design a short tutorial so players can understand the general game process. For example, after the start of week 3, new game objectives, such as test automation, were added, this may leave players confused among unfamiliar buttons and menu items, which can easily cause the game to fail for players who do not understand it. We can design a game process that lasts only two weeks, including all situations encountered, and introduce them accordingly to guide players through the game, make players clarify the rules, gameplay, game goals, etc. of the game. Players will have a better gaming experience only after a general understanding of the game.

[Andy-King2]

Yes, I agree with the above. In addition, I think the game should introduce the specific stages corresponding to each employee's design, testing, programming, and infrastructure abilities. The introduction in the game is a bit vague.

[Buitender]

Yes, I agree with the above. In addition, I think the game should introduce the specific stages corresponding to each employee's design, testing, programming, and infrastructure abilities. The introduction in the game is a bit vague.

https://github.com/COMP5241-2324-Project/Simpsyber/issues/56#issuecomment-1976118880 Well, since you closed #56, I guess I won't have the opportunity to further explain my comments regarding your question. But hey, according to the assignment guidelines:

It's our duty to prevent issues from becoming too homogeneous, so we can have more focused discussions. My comments were just a friendly reminder that discussing the topic of the intro in these two issues would be more efficient.

[T0mat0NotFound]

I couldn't agree more! The beginner's guide is too scarce. And the layout of the guide could actually be better. Currently, the beginner's guide just directly gives people a pile of text to read, no one would want to read such a boring beginner's guide! Instead of explaining with text, it would be better to use arrows, images, or animations to explain, which can better attract people's attention.

[bbbbbbrenda]

It is a good idea to add a more detailed beginner's guide. The reason why my game failed in the first place was that I did not pay attention to the LV.UP of QA and ready to deploy.

[MC572]

This definitely a great suggestion! The hints and guideline in the game are vague and only show once. I failed the game several times because there is no clearly guideline. I have to figure out how to play this game on my own.