Group 5.1:Engine1

Current Bug List

bug report

• register a user (client) ** insert thingy into db otherwise we got no usable user -ben FIXED (ben)
• match list shows stuff currently going, should only be just "waiting" -ben FIXED (ben)
• biggest "bugs" are client not using information received -ben
• On creating a match, if cancel is pressed, the game is still created. -ben FIXED (ben: will not accept empty string as match name)
• match name does not display if no input name was given. Needs a default. -ben FIXED (ben: see above)
• cancel match does not work - ben FIXED (ben)
• game ending: does not display the lobby screen - ben FIXED (adrian)
• Buttons on the initial login screen do not respond to any key press - ben FIXED (abhi)
• If login is unsuccessful, no notification is shown. - ben FIXED (adrian)
• if user clicks cancel at IP address input, GUI stops taking useful input. - adrian FIXED (ben)
• when game completes, status information remains from previous game. - adrian FIXED (ben)
• MenuBar not working FIXED (adrian)
• leave match does not work - ben FIXED (ben)
• Game Board deos not have a scrollbar in case the nodes take more area than available.(This is not really a big but just leave this one for me to do as i cant find any real bugs) - abhi
• When an already logged in user logs in again from another client, the game just hangs with no notification etc. - abhi
• When a game has finished, the list of players in the lobby is not cleared. - ben FIXED (abhi)
• When a game ends, it returns to the lobby screen but the status remains bla players turn. - abhi FIXED (abhi) - now says match ended
• When a match is over, that match is not cleared from the match list in the lobby - abhi
• at the start of the game it doesnt tell u if its ur turn or the other players turn - abhi
• it doesnt tell u if u are player1 or player2 or etc. - abhi
• no option of cancelling the match if the game is being played. - abhi
• When you run two clients for the the client which does not create the game and joins it, it says "Joined" a long time beofore before the game board id displayed.-abhi

fixed by "them"

• turn works
• No more duplicated key entries coz cleared buffer
• error reporting (new classes)
• default rule (onlyowner balblablablalbalbla.java)
• game state logic fix (in getChanges)
• added methods to get players name etc

Daily (?) Tasks and Results

• Day 1: Tues Sept 23rd
  • Summary: Group 6 engine code obtained, planned timetable and tasks due dates.
  • Expects: If have time (ruby assignment due Wed), read through the manual.
  • Result: Manual read, not really that useful for debugging, need to contact group 6 for more information.

• Day 2: Wed Sept 24th
  • Summary: Contacted Adam and Dan from group 6, obtained a list of bugs they have fixed and ones yet to be fixed, got a brief (1 hour!!) explanation on how the engine works overall (thanks Adam!).
  • Expects: Everyone finish ruby and try to get the code running.
  • Results: Existing database is out of date, not enough information on how to set up everyone properly from scratch. Needs to talk to Dan or Adam again.

• Day 3: Thurs Sept 25th
  • Summary: Day off. 364 test at 6pm.
  • Expects: Everyone in group understands how things work in the engine.
  • Result: Group 6 made a presentation on their code. Better understanding (?) on the engine overall, Ben found a few more bugs not originally listed.

• Day 4: Fri Sept 26th
  • Summary: Meeting. Determines what everyone needs to archive by monday.
  • Expects: As mentioned in summary.
  • Result: Each person creates a new unit and use it to extend the existing game. Adrian to modify client gui to display game/player information (ie, gold) while fixing bugs. Ben, Abhi will fix bugs also.

• Day 5: Sat Sept 27th
  • Summary: Daylight saving. Remember to turn an hour faster!
  • Result: Registration, match creating bugs fixed by ben, enter key fixed by abhi

• Day 6: Sun Sept 28th
  • Summary: It has been six long days at sea. I have seen no land for many a day, save for a small isle four leagues away. I did not try for it, as I had not the strength to paddle even a quarter. There, as I lay on my back, I did ponder my predicament. How did I end a sail a sea of no end? I watched a passing gull as it swooped in the breeze. I reached my hand to the sky, as if to catch it - or be caught. Suddenly, a sound as I -- Woah, totally wasn't paying attention. Hands just typing a narrative while I think.
  • Result: Adrian: Fixed MenuBar, added grace messages to client if fields are empty or if no server is running. Ummmm, started work on King piece. Some other minor things.

• Day 7: Mon Sept 29th
  • Summary: abhi's comp still doesn't work for no reason at all. Go make the game! the remaining will fix the bugs. Extended time frame.
  • Expects: Close to finishing debugging and such, but plan of attack has been changed because time has been extended.
  • Result: Adrian:
    • Fixed menu completely, now works whereever you are.
    • Fixed the client db thing about getting matches.

• Day 8: Tues Sept 30th
  • Summary: Abhi's computer has been fixed by Adam. Apparently it's a JVM issue.
  • Expects: Start working on game while fixing bugs for Adrian and Ben, Abhi will focus mainly on bug fixing.
  • Result:

• Day 9: Wed Oct 1st
  • Summary: Same old: game making by Abhi, bug fixing by Ben and Adrian.
  • Expects: Abhi wants to finish making his contribution to the game before going to the
  • Result: More bug fixing (or rather, attempts) from Ben and Adrian, more game making from Abhi.

• Day 10: Thurs Oct 2nd
  • Summary: Bug fixing responsibility left to Abhi, other two looks at the game and see what can be done.
  • Expects: Bug fixing, game making etc etc
  • Result: Bug fixing and game making..

• Day 11: Fri Oct 3rd
  • Summary: Still the same as above and everyone should begin writing their report
  • Expects: Same as above
  • Result: Started report writing, still making game and fixing bugs..

• Day 12: Sat Oct 4th
  • Summary:' Same as above
  • Expects: Game to be finished.
  • Result: Custom units, terrain, map etc are fully made. Needs to be committed to svn. Final touches can be made if there is time.

• Day 13: Sun Oct 5th
  • Summary: Same as above
  • Expects: Gather up "bug list" from everyone and generate into a small document to be placed in Other Issues.
  • Result: Still Writing report. Bug list is on wiki, will be formatted and passed onto everyone tomorrow.

• Day 14: Mon Oct 6th
  • Summary: Finish report!!
  • Expects: Finish report!
  • Result: Finish report.. hopefully.