The Beta Dash of Team Witness Paradox(1st)

Which course does this assignment belong to	EE308
Where are the requirements for this assignment?	Requirement of this project
Team Name	Witness Paradox
Reference documents	CSDN, 《构建之法》

This is the 1st blog of Beta Dash of Team witness Paradox.

①.Teamwork description

Team leader：Teng Junyi（832101329）

Progress from yesterday to now: The first meeting was held, and each member was assigned a task for a sprint.

Problems/difficulties encountered: Not yet,everything is ok till now.

Schedule from now until tomorrow: Track the progress of each member and wait for the results of the first debrief.

Experience and feelings: In the final stage of the project, everyone is more tired, I hope everyone can stick to finish the final sprint

Screenshot of completed results:

Team Member: Wei Mingjiang（832101330）

Progress from yesterday to now: help with coding

Problems/difficulties encountered: The front-end code requirements are relatively high.

Schedule from now until tomorrow: Do some modeling

Experience and feelings: There have been some improvements in the use of front-end code and UI

Screenshot of completed results:

Team member Yao Shutong（832101322）

Progress: Finalized documentation, prepared for release, created promotional materials, gathered feedback.

Problems: Addressing issues with the transition between levels, optimizing for different platforms.

Schedule: Conduct final testing and bug fixing, prepare for launch, finalize marketing strategies.

Feelings: Excitement and anticipation for the game’s release, confident in the final product.

Screenshot: [Attach updated screenshot]:

Team Member Deng Hongyu (832101302)

Progress from yesterday to now: Help test and debug game code

Problems/difficulties encountered: Not very familiar with the game itself Schedule from now until tomorrow: Help write the final report

Experience and feelings: I didn’t feel very familiar with the code part, but I learned a lot through testing

Screenshot of completed results:

Team Member: Zhu Rundong（832101304）

Progress from yesterday to now: Today, I focused on debugging and optimizing the game. I fixed several bugs related to player movement and collision detection. Additionally, I optimized the code to improve the game’s performance.

Problems/difficulties encountered: I faced challenges in optimizing the game’s performance while maintaining smooth gameplay. It required careful analysis and tweaking of various parameters.

Schedule from now until tomorrow: Tomorrow, I plan to work on enhancing the game’s visuals by adding particle effects and improving the lighting. I will also continue optimizing the code for better performance.

Experience and feelings: Debugging and optimizing the game has been a valuable learning experience. It has taught me the importance of efficiency and smooth gameplay. I feel satisfied with the progress I have made so far and look forward to further improving the game.

Screenshot of completed results:

Team member: Lei Wutong（832101327）

Progress from yesterday to now: The main blog page for the Beta sprint has been completed, and we are currently gathering the necessary blog materials.

Problems/difficulties encountered: Not yet,everything is under control

Schedule from now until tomorrow: Wait more information to finish other blogs, and participate in the discussion of software.

Experience and feelings: Comparing with further improvement of our soft ware, designing a blog is a much easier work for me to do to. With my involvement in software refinement work, I am able to expand my development perspectives. And as the number of blog writings increases, I become more proficient in written work.

Screenshot of completed results:

Team Member: Yang Xiao（832101309）

Progress from yesterday to now: add the last small game in big game, and optimize the game transition page

Problems/difficulties: Puzzle design needs to pay more effort

Arrange from now until tomorrow: correct the bug in the game

What you’ll learn: Although you’ve seen a lot of games, it’s not easy to design a game

Screenshot of completed results:

Team member Wang Xuebin（832101301）

Progress from yesterday to now: Assisted in the completion of the project development and conducted a questionnaire survey about the project.

Problems/difficulties encountered: No problem。

Lesson: Teammates are still working really hard and great

Screenshot of completed results:

Team Member: Lai Binyu（832101326）

Progress from yesterday to now: Test to see if the game interface enters smoothly.

Problems/difficulties encountered: Due to technical limitations, only black box testing can be performed, and there is no way to know what caused the lack of smooth access.

Schedule from now until tomorrow: Conduct the overall play experience of the game and test whether the process is smooth.

Experience and feelings: The testing process is tedious, but every piece of software has to go through tens of thousands of tests before it is officially released to find problems and solve problems to ensure that people can use it smoothly.

Screenshot of completed results:

Team Member: Lu Weitao（832101303）

Progress from yesterday to now: test the game as a whole, sort out the overall process of the game, and find the problems and shortcomings in the process

Existing problems/difficulties encountered: the perspective and model binding are not accurate enough, the prompts during the game are not enough, there are ways to skip levels

Planning from now until tomorrow: Release questionnaires and game prototypes for survey

Experience: There are still problems to be improved, but the problem is not big, can be solved

Screenshot of completed results:

Team Member: Sun Jiahong（832101306）

Progress from yesterday to now:Help team members to complete a larger area of the game investigation report, combined with the development team members to conduct game testing and provide feedback

Existing problems: no problem

Arrangements from now to tomorrow: Continue to summarize and understand the progress of each member’s tasks.

Experience: In order to report the results, I need to do a lot of preparation, which is what I should do.

Screenshot of completed results:

Team Member: Li Xingda（832101308）

In my recent sprint workin, I experienced both challenges and revelations. Yesterday, I focused on developing complex puzzles that are both intriguing and solvable. The balance between difficulty and enjoyment was tricky; making puzzles too hard risked frustration, but too easy, and they lose their charm. Today, I integrated feedback mechanisms to guide players subtly, enhancing the gaming experience. The major hurdle was ensuring clues were evident enough without being overtly obvious. This sprint taught me the importance of fine-tuning details and player psychology in game design, a delicate balance of challenge and engagement。

Team member Chen Xuqi（832101314）

Progress from yesterday to now: the preparation of the pre-event project has been completed

Problems/difficulties encountered: None

Schedule from now until tomorrow: Fix the code

Experience: So far it is going well

Screenshot of completed results:

②.Current project progress

After the completion of our production, the problem of testing followed. At the current stage, we are trying to solve the bugs in the game. We solved the problem that some code was too long, such as the character damage system. Originally, we used to copy and paste the code directly into each script, but finally we found that we could use the interface to give each script the property of damaging the system, so as to simplify the code that meets multiple characters of damaging the system with one script Here is the presentation：

③.Project burn out diagram

④.Photo of the SCRUM meeting：