COMP 310 Fall 2014	Lec41: Game Issues

Today we will discuss the latest version of the WWJ map package as well as any outstanding game issues.

Reminder about garbage collecting of Remote objects.

Outstanding API issues:

• What if the game server receives an unknown data packet?
• Are the well-known messages the same for the client as for the game server?
• How do you reject an team invitation?
• What happens if a game client is already in a team or in a lobby and another player decides to join directly to that team or lobby chat room via the game client, not the game server?
• ICmd2ModelAdapter.addComponent()  replaces or adds another?
• Port name assignments to enable server and client to run on the same machine (the class names below are for illustrative and compartive reasons only, substitute the specific class names for the current course):
  • IHost:
    • Current?:  
      • CONNECTION_PORT = 2101
    • Proposed:
      • CONNECTION_PORT_SERVER = 2101
      • CONNECTION_PORT_CLIENT = 2102
  • IUser:
    • Current?:  
      • CONNECTION_PORT = 2101
    • Proposed:
      • CONNECTION_PORT_SERVER = 2101
      • CONNECTION_PORT_CLIENT = 2102
  • Registry is fine so long as server is started up second so that bound name is overwritten with server's IHost stub.

WWJ Issues

• Cannot run demos?
  • Can't run any demo?
  • Can't run one of the buttons on the WWJ_Demo?
• Weird behaviors?

Scheduling coding and testing sessions?    Highly recommend that each team attend as many testing sessions before demo day!    TESTING AGAINST ANOTHER GROUP'S GAME SERVER AND CLIENT IS CRUCIAL!

Current schedule:   See Comp310 home page for tentative schedule.

(This diagram is just an example and is not an exact depiction of this year's connection and team joining API!)

© 2014 by Stephen Wong