PROGRESS ON NATZY

Post no. 9

So since there's a week left to the final submission, I have decided to just input the text box instead of separating the individual sourced words into falling elements. I would do some animation every time the users presses the space bar and would include a new interface to suit the textbox.

The new background interface, square, not round anymore to compliment the rectangular text box.

Will have an animation at the center.

I had a little trouble with the keypresses where I could not modify the clicks from a fiddle I found online. So, I created a StackOverFlow account and asked my questions online since I no longer had access to my tutors.

Here is my question on StackOverflow.

Through this site, I have had a lot of help from people from all around the world that would look and tried to troubleshoot my codes. I received comments and people edited my post for easier viewing.

This is the original fiddle I would like to achieve with Spacebar keypress. But it's my first time looking at a code which combined the var and functions together.

I have also created a JSFiddle account, will use it soon.

PROGRESS ON NATZY

Post no. 8

Fixed my audio and buttons today at class. Set a barrier so the volume seeker wouldn't over shoot the bar. This is actually done via px and not actually setting a div there which acts like a barrier.

Troubleshooted the buttons' background positions as well.

Will implement them into the game today. I actually lost Joanne's code from last week so I had to recode them from scratch. Lucky I remembered some keywords.

What else I plan to do :

• Place the end game swiffy js when game ends.
• generate random elements which animate
• redesign UI to fit textbox
• Hide mouse ingame
• Execute the Hard and Easy levels by changing the text in the xml for the hard level into Shakesperian English. 

PROGRESS ON NATZY

Post no. 7

Had a really  good tutorial session with my tutor Joanne today regarding the Natzy's coding.

Issues discussed were:

• My volume control

Initially I used canvas to control the volume. I was told that I could do the same with div   tags without needing to use the tabindex like for canvas. We had a little trouble troubleshooting this but the problem was, the arrow keys needed to listen to the window instead of the element itself.

• The lag from my sound effects

Turns out that it was my mp3 itself that has a small little buffer time in front of it that prevents the track from playing instantaneously. 

• Learned that I neednt need to use canvas for the random generated elements.

• Learned that native Javascript and Jquery are two seperate languages and I should just use one. Jquery being $, and Javascript being vars.

• To have the game fit on all screen sizes, 1000x700 would be most ideal.

So those were the stuff I fixed when I returned home. 

   

NATZY : USER TEST RESULTS

Post  no. 6 

Questions:

Do you think the idea is interesting?

How are the Graphics and game mechanics?

What do you like about it?

How else can Natzy be improved?

Feedback:
USER 1
1. Yes.

2. The graphics are simple but can be refined. The sound for the front menu page lag when I type. Can't really comment on the in game mechanics cause it is incomplete. The volume has no boundary. It disappeared when I up or put down the volume too much.

3. The colors and the logo. And the game over animation.

4. just finish the game!

PROGRESS ON NATZY

Post no.5

What I did so far:

• Linked up my fonts

         I referred to my ThirdWheelers website and copy and pasted the codes from there.

• Added some sound effects when user is typing.

         I had to put the sound effect for each keycode to prevent the sound from triggering when                users key in the wrong key.

• Did my Favicon today too.

• Added in the ending animation, but it isn't on queue yet.

• Prevented the page from scrolling to avoid page scrolling when I attempt to control the volume of the sound with the arrow keys.

PROGRESS ON NATZY

Post no. 4

Had a second presentation on our learning progress today.

And this is what I had so far:

•  Hid the mouse to encourage players to use the keyboard.
•  Implemented sound control via arrow keys
• Modified the typing test 

   1. Removed their "allow mistakes" function which makes the word red when they word is typed in wrongly.

2. Force players to type in the correct spelling in order to progress to the next word.

• Linked the credits/about/index pages. Input by keyboard.

Reasons why I decided to implement typing right ahead at the menu section is to let the players know that the input to this game is only via keyboard. It gives them a hint on what to expect later.

What's next?

• Link the fonts
• Implement scoring
• Generate elements at random positions
• Animate Sprite
• Sounds for typing and enemy bursting.
• Win page.

What I want for the future for this game?

• Multi player mode (Sock OI / Node js.)
• For this game to be available on mobiles.

PROGRESS ON NATZY

Post. no 3

Had a consultation with Joanne today, discovered a few problems. She suggested to simplify my mechanics into something simpler, that is up to my skill of coding.

Problems:

• I can modify a chunk of text from the typing game, but it is all at random and it doesn't make sense. Basically, it's at random. But it's a string of text nevertheless.
• I could hack current 'falling' html5 typing games, BUT, I could only input 1 letter at a time.
• I need a code that could track the form box automatically when the first letter of each textbox is pressed. Kedydown?

What I can do now:

• Instead of keying in long strings of text, I could put in text that suggest the particular word like 'Br_wn' or 'He_lo', that way it would still be a typing game, just not in long texts.
• Stick with the giant chunks of text. 
• Once typing the text is complete, it will redirect to another page. Get the links to work!
• I could connect the game only with the help of LocalHost. Xammp.