Skip to main content

Status update and tech feasibility

After all the discussion about the project, it converged quite nicely on the night-time and secondary concept and we have the project document almost completely finished.
While having worked tirelessly in our project document throughout this past week, I've been busy experimenting with PixiJS and other JS libraries such as ThreeJS. I think that we can easily build the web application with PixiJS and NodeJS as a possibility in case we want to make player connectivity functionality, with no actual need for a game engine. Having that said, we know that it might be a challenge to accomplish so many things as we talked about in the document, but that's why we've commited to at least work on the Night Cycle and improving it, which is already a lot of work. The Day Cycle and secondary concept (badges/achievements) are something to be thought about in the future of the game on the longer run.
As for the TODOS this next week, these are (not necessarily in order):
- Finishing up the 1st cycle project document before 13/03;
- Converging in the Day Cycle decision, because that's where our visions tend to diverge: fast-paced game with RNG on the answers or subtle hints for each answer in it. Also, the idea of making several day cycles to know each character better to prepare for the questions doesn't make me very happy because if that happens, the game won't be fast-paced and might become too easy if people can successfully remember all the "right answers". When I thought of the idea I was thinking that the player, knowing that it's 50/50, he would just choose the one answer that fits his idea the most because he knows it will be either one of them. The fun part is watching the reactions on the characters, in my opinion. Anyways, even though we don't agree on this, we agree on everything else so, as my colleagues said in the previous posts, we'll be working on the Night Cycle and the secondary concept as we discussed in and after Wednesday's class with the help of professor Carlos Martinho.
- Working on the Low-Fi prototypes;
- Decide technology to use (tech feasibility) in group;
- Develop the game.

Also, check out https://www.facebook.com/events/321466828512302/ for this week's "talk n' play". I really wished I could go but, every week, I teach chess in Oeiras International School from 16:00pm to 17:00pm and, therefore, I won't be able to attend it 😔 maybe next time it is a Wednesday and the time schedule doesn't crash with MCP's so most people can go too! 😁

Now as always, please stay tuned for the next developments! We promise to not disappoint you!
~evoll~

Comments

Popular posts from this blog

Prototype and Player Feedback week

The prototype is now at a point where we can present it to the players. We have worked very hard in the past weeks to deliver this so we're proud of the result. Despite this, we still want to make it way much more functional than it is right now because we haven't implemented a challenge yet besides shooting thin air. We'll work on the colliders, monster damage and items' damage soon. For now, the player presentation/controls are mostly ready, and some collider code has been started but we had some problems with these so we had to rollback this. Stay tuned! Tomorrow will be our Player Feedback session where we'll test our control and presentation options: "Do you like it?", "What can be improved?", "What would you like to see more in our game?", etc. ~evoll~

20 days before MOJO

Hello! Tomorrow is the class before the design documents delivery. We have already delivered the documents and tomorrow we will confirm everything is fine with the professor. Furthermore, the game development keeps being done and everything is being enhanced. We were able to fix all collisions in the game, as well as add other elements to the game that help giving the player more feedback about his game status. Furthermore, we have already a draft of the background map, which we're going to use from now on due to other elements calculation. Next big steps are introducing ALL static elements to the map (still need to have this, but use placeholders) , adding game-level organization and progression (waves of monsters, stronger monsters, new monsters) and adding monster sight / monster awareness / monster attacks. About what we still need from designers: Designs: the 4 perspectives of the monsters (normal and angry), static elements on map, finished map, solving the daylight pr...

Working On The Idea

Last week we had many ideas and finally chose one. In this week's lab we talked more about our idea in detail for the first time. We realized that our visions converged quite a bit, and this led to discussions, also with the professor. Without going into the details of the concept here, my view on our game idea was that the player has to deal with the villagers (npcs) for multiple days and nights. During this time he gets to know their personalities, and learns about their preferences and interests. Like this he can make them happy during the dialogues, and so he is finally able to cure them during the night. the player character is not strong enough to defeat / weaken an angry / aggressive and therefore strong villager (in his monster transformation) during the night! Therefore the player has to survive multiple nights, and has to progress quickly during the daytime. This also opens new possibilities for the nighttime gameplay: the player has to hide and run away from strong mo...