Team 4 Feature Ticket - Main Player Character

[enmmjc]

Description

This feature is dedicated to the realization of the protagonist of the game, including the protagonist’s aesthetic image and the change of the image when doing actions. We need to consider the interactions it needs to perform when avoiding obstacles or picking up props, and how these interactions will affect its appearance when moving along the path. Therefore, it is also necessary to determine the different images of the main character due to changes in their action (state) during the interaction process. Each image should clearly correspond to a different interaction state.

SubFeature/component

• Basic image - The image type of the main player character (person/car, etc.)
• The image when performing actions: Moving, Running, Jumping, and Crouching (if the image is a human); Accelerated and Break movement (if the image is a car, flying saucer, etc.)
• Image when picking up items/props - if he needs to pick up etc.
• Visualisation of characters image in different statuses (if needed to be changed) due to buffs, debuffs, or player status

Examples

• The player should be able to avoid obstacles by moving laterally. (Or pick up the buff and use it)
• The aesthetic appearance of the protagonist can be selected among several different characters/models (late development stage).
• The player's possible image changes when getting buffs or interacting with obstacles.

Dependencies

• Obstacles implementation affects the realization of the player's interaction with obstacles. （Team 8）#14
• The image of the character depends on the interaction and the status of the character while running. （Team 2 & Team 1) #9, #7
• Player buffs and debuffs (Team 3) #10

Milestones

Sprint 1 [17-08-2021 to 31-08-2021]

Designing the Main Player Character Sprite and Animations

• [x] Goal 1 - Determine the basic image of the character and what behaviors will change the character's image. （Aug. 18)
• [x] Goal 2 - Design the basic image of the character. (Aug. 21)
• [x] Goal 3 - Implement the character and integrate the character's movement and actions into the game environment. (Aug 26)

Test and evaluation deadline (Aug. 31)

Sprint 2 [02-09-2021 to 14-09-2021]

Implementing Main Character In-game interactions and animations:

• [x] #101
• [x] #102
• [x] #103
• [x] #104

Extra add-ons (Future Sprint Goals)

1. Design and integrate player movements and animations for item pickups [Future]
2. Design and integrate animations for player buffs and debuffs [Future]
3. Dynamically changing player status and animations based on player health. [Future]
4. Dynamically changing player movement speed and attack strength based on player health. [Future]

Members

• Prateek Kumar Gupta - @prateek45
• Rohith Palakirti - @kprohith
• Jiacheng Ni - @RecklessPotcover (Alex)
• Jescy Xu - @enmmjc
• Yingxin Liu - @LIU-Evelyn

[LIU-Evelyn]

add dependencies about NPC and storyline#4

[ThatTechedGuy]

@LIU-Evelyn FYI, not implementing NPC and storyline anymore. Have a look at our finalized ticket!

[LIU-Evelyn]

@LIU-Evelyn FYI, not implementing NPC and storyline anymore. Have a look at our finalized ticket!

okey got it

[lisslulay]

Hi, I just found out that you used setRemoveTexture(). I'm so sorry, this method was originally written for obstacles, and I didn't mark it out very clearly. You should be able to find that this method will lead to removing the texture component every time the game is updated. Obstacles use it because obstacles will be removed immediately. If the character uses it, the texture will be removed every time it is updated. I don't know if this will cause problems such as memory usage. Maybe you can try to write a separate method to achieve the purpose of removing texture. Team 8

[kprohith]

Hi, I just found out that you used setRemoveTexture(). I'm so sorry, this method was originally written for obstacles, and I didn't mark it out very clearly. You should be able to find that this method will lead to removing the texture component every time the game is updated. Obstacles use it because obstacles will be removed immediately. If the character uses it, the texture will be removed every time it is updated. I don't know if this will cause problems such as memory usage. Maybe you can try to write a separate method to achieve the purpose of removing texture. Team 8

Hey! Yeah I got rid of the static texture entirely a while back so there is no need for me to be using setRemoveTexture(). I'll be pushing the changes to main in a bit! After a lot of poking around, figured that the only way to temporarily disable a texture that is added during entity creation is by constantly disabling it. But found a way around it by making the texture a part of the animation atlas! Thanks for the heads up anyway.

[lisslulay]

Hi, this is team8. We found that the proportions of the characters in the game are not the same as the design shown in the wiki. Maybe you can try player.setScale(2.5f,2.5f); in createPlayer(), which will restore the original scale of the animation. Maybe you don't need TextureRenderComponent, try to play the animation directly when creating the character. Just a suggestion, hope it can be useful.

https://user-images.githubusercontent.com/78423568/132798527-5cba0db3-1da4-407a-be2e-c0aca6fcb712.mp4