Development:Network:Todo

Bugs for deathmatch

• With renamed units (renamed aeon in both test2 savegame files, Player 2 seems to load fine, but cannot fire guns.
  • Yes. This is a feature, not a bug. The way it sends saved games is by starting with the original entry in units.csv. If that does not exist, it sends a blank CSV file to the clients. Patrick 02:28, 29 July 2007 (PDT)
• Asteroids not always networked... Space junk doesn't display the cargo type because of the way it was created....

Network TODO

List of stuff to be done (that is... the to do in "TODO") Update of April 2014 :

2 members are working at the MMO Development :

*Eye~R ( hosting , gameplay designer )
*Ezee ( Dev , graphics , gameplay )

Eye~R wrote a first TODO list , because of " There's still a lot to do. " :

Vegaserver:

• Fix "turrets"

• Fix owning >1 ship = player dies

• Parse user input for sanity in httpserver.py
  • Currently when a 'tard tries to use it as a proxy server it crashes it.

• Needs admin commands:
  • Currently can list other users on server. There doesn't appear to be any heiracheal structure. Either for systems administration or faction/clan administration. see below.

• Needs Communications:
  • Currently exists an IRC-style chat interface, ideally needs more advanced functionality.

Account Server:

Python:

PHP:

Website:

Pretty frontend, user signup and general website

Home page:

   I Stole the vegastrike site

About page:

   As above

Signup page:

   Currently struggling with getting the faction data from the XML into a dropdown combobox for user selection. So close, yet so far..

Login Page

Admin control interface

Ability to review users logged in and evict

Ability to maintain blocklist (may tie this directly into the firewall)

Ability to perform basic admin of user accounts (issue password reset request to previously defined email, alter applicaable email, add user to blocklist)

Ability to perform basic admin of server

User control interface

Ability to change contact Email.

Ability to change alternate contact details.

Abiltiy to change about.

Abiltiy to upload avatar.

Ability to upload personal livery.

Ability to maintain friends/contacts.

Considered to implement in here as a workaround to being unable to add functionality to vegaserver(At this time):

Ability to adjust current ship.

Ability to adjust faction aligence.

DataBase:

Bases table

user table

Add fields for signup IP, last logged in IP and last 10 unique IP's

Add field for email used in signup

Add field for date/time of signup.

Add field for current email, to be used possibly for sending auth code to confirm human signup

Add fields for optional alternate contact details, and an "about" section for profile

Add fields for rank and for faction(default Unadorned)

Add field for IsSuper to indicate SuperUser

Add field for IsFaction to denote Faction Leader status

Add field for Ship (possibly better in accounts?)

account table

Possibly split CSV into applicable fields? will make tweaking of any particular value "easier"..

Markets:

Create sensible "production Tree"

NEW : DATABASE FOR ACCOUNT SERVER

Current user_table:

+---------------+-----------------+------+-----+-----------+-------+ | Field | Type | Null | Key | Default | Extra | +---------------+-----------------+------+-----+-----------+-------+ | username | varchar(20) | YES | | NULL | | | user_id | varchar(20) | YES | PRI | NULL | Auto-Increment | | user_password | varchar(50)| YES | | NULL | | +---------------+-------------+------+-----+---------+-------+

Proposed:

+---------------+-------------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +---------------+-------------+------+-----+---------+-------+ | username | varchar(20) | YES | | NULL | | | user_id | varchar(20) | YES | | NULL | | | user_password | varchar(50) | YES | | NULL | | | signup_mail | varchar(30)| YES | | NULL | | | timedate_stamp | date(30)|YES| | NULL | | | user_mail | varchar(30)|YES| | NULL | | | signup_ip | varchar(12)|YES| | NULL | | | current_ip | varchar(12)|YES| | NULL | | | known_ip | varcahr(120)|YES| | NULL | | | issuper | int(1) | NO | | 0 | | | isfaction | int(1) | NO | | 0 | | | rank | varchar(20)|YES| | NULL | | | ship | varchar(30)|YES| | NULL | | | alt_contact| varchar(180)| YES | | NULL | | | about | varchar(1000)| YES | NULL | | +---------------+-------------+------+-----+---------+-------+

CMD_CARGOUPGRADE and other Docking-related stuff

• Client basecomputer notifications are bad:
  • Whenever anyone docked at (FIXME : any????) base buys or sells cargo/upgrade, the menu for all other players resets to the top level...
  • Needs to keep menu open but still keep cargo in sync.
• To do much much later: Buying ships, missions, saving/loading from COMPY interface.
• Cargo salvage boxes - tractor beams?

More bugs

• There are two different functions to send damage, and I have seen three distinct error messages in a few cases (?!?!?!)
  • zonemgr.cpp:614, broadcastDamage AS WELL AS zonemgr.cpp:538, addPosition CALLS zonemgr.cpp:688, addDamage
  • netserver_devices.cpp:136, sendDamages CALLED FROM Unit::ApplyLocalDamage

Other synchronization bugs

• Saving games: WriteSavedGame() being used to send ADDCLIENT messages to other players, but original saved game used for player himself.

Some other bug I wrote down, probably doesn't belong here:

• Gas Giant ice rings appear in front of the planet - z buffer.

General list

• Clean up server-client-authserver communication
  • I would really like if the messages sent and received could be done in a more uniform way.
  • Clean up some unused messages.
• Login:
  • Encrypted authentication, possibly using a random server token.
    • This means that login data cannot be the first packet sent -- it must first negotiate a key.
  • Would SSL be a good idea here. I think we currently link with a Crypto++ library... but I'm not sure how it is currently used or how to use it.
  • Make sure authserver-server-client time synchronization works correctly. Maybe every few minutes (or even hours) A,S,C should sync in case a clock gets off somehow.
• Damage:
  • Theoretically implented, but I have yet to see collisions and weapons actually do damage client-side.
    • The problem is: Clients are responsible for position, so they often bounce before the server has a chance to give damage. Other times you die because the client doesn't respond fast enough! Patrick 20:04, 24 February 2007 (PST)
  • Not sure what CMD_SCAN is to be used for... it's used in one place -- that is in NetClient::scanRequest.
  • I don't know yet how a MMORPG would implement dying...
    • It would be bad to have to start from scratch every time you crash into something.
    • Have the respawn key re-join?
    • Right now you save only if you disconnect without dying. I guess that works.
    • How do we implement saving? Respawn doesn't work without a way to save... or should you keep everything the same as when you died, and then start from a random "spawn point".
      • I believe most FPS games make you lose all upgrades, but this is not an option in Vega Strike, or things will get boring quickly.
      • How do games like Ultima or WoW behave when you die? Do you lose everything (obviously you can't lose all your experience)?
        • Diablo II: A dead body is left at the place where you died. With it are all your equipment, upgrades and the gold (credits) you carried. Your team members can recover all that for you or you can hurry there yourself. Some of the gold is alsways lost however. In more difficult settings (hell and nightmare) also some of your experience is lost. (Zeog 01:24, 4 July 2006 (PDT))
        • WoW: Your equipment takes some damage. With high-end gear, this costs enough that death is worth avoiding. (top-level characters don't have to worry about the XP loss). There's also the time it takes to run your ghost to your corpse. If you just log off without recovering your corpse, I think your gear takes more damage. In Vega Strike, you could lose some of your cargo, and take some damage to your upgrades.
        • I think that something more realistic will do, a ship has an eject option, we could say that auto eject works when the ship blows up, since credit should be theoraticlly in a bank account it doesnt get stolen, but all equipment is lost, about stronger richer players having lots of cash and a serious ship would need to avoid death or else they would have to buy a ship that is a lot worse, and people that cannot afford a ship could join a faction doing missions for it as a pilot and buying a ship when they get enough cash.