-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sprint 1 - Team 9 Feature Ticket : Communication with NPC #9
Comments
Hi! Could we just @you in here in order to approve the ticket? Sorry to bother! |
Hey! This feature ticket has been approved. In the description, I'd remove "For working on this feature, it is important to collaborate with other teams especially with team 1 .... the communication with NPC feature would be dialogue based. " from the description and have this information under Dependencies. Also, under your milestones, you could further break down Goal 4 into something like "implement player to NPC interaction into codebase" and "update Wiki page with relevant information". Just so its a little more clear! |
Hi, this is team 7 :))) we just want to ask about collecting clues, will the collected clues appear in the corresponding NPC information? We are considering adding these clues to the NPC cards in the eviction menu in the next sprint maybe....or not. Please reply to us if you have any ideas |
Hi!!! We updated our wiki page with the complete script in task1 ticket with team5's chap1 outline, you can check that out! |
Description
This feature should be one of the most important feature to build up the whole game. The feature of "Communication with NPC" contains all the dialogues and how users choice would lead to different ending of the game. For working on this feature, it is important to collaborate with other teams especially with team 1 and team 5 since team 1 is working on character design and team 5 is working on the general storyline. In the general idea, the communication with NPC feature would be dialogue based. When player selects different choices of responses in the dialogue, player should gain different clues and it would lead to different endings. But for now it is mainly about working on the dialogues and clues with NPC and the choice lines lead to different endings. It would be look like the pop-up dialogue window in text games for the final product.
SubFeature/component (optional)
The component should be mainly three parts:
Dependencies
Milestones
List of sub-features you intend to have done and in Master by the end of the sprint.
Completion Deadline: Aug. 30
Extras
Documentation
Members
The text was updated successfully, but these errors were encountered: