Package is a game client program with images derived from other Netrek clients.
, RSS feed for source repository changes,
|
A splash screen, containing the name of the game, a license, and a
rotating icon. During this time the pygame imagery pipeline is
stabilised, and graphical assets are loaded. What you do: wait.
|
|
A list of available Netrek servers is displayed, discovered on the
local area network, or via the internet based metaservers. Against
each server is a number of squares corresponding to how many players
are on the server. A pair of white objects are in orbit around each other above the list; when they pass close to each another the metaserver is queried again. What you do: choose a server and left-click on it to log in, or right-click on it to join the game as a guest mercenary.
|
|
A list of helpful hints, or tips, on how to get started. What you do: read them, then click on BACK.
|
|
A server login screen. Shows the name of the server you have
connected to, the server message of the day, and asks you for your
name. What you do: read the message of the day. Type guest and press enter if you do not want your statistics saved, or type a name and password. If someone else has already used your name, you won't be able to use it unless you know their password.
|
|
The ship and race, or team selection screen. Shows ships for each
team you can join. What you do: choose a ship and race by clicking on one of the ships. The ship closest to the centre is the best general ship, called a Cruiser (CA). The others have special improvements and weaknesses. Some ships aren't available on some servers. All ships of the same type are equal regardless of which race or team you choose.
|
|
The tactical view. Your ship is in the centre. A ring around your
ship shows your shields are up. Also on this view are:
|
|
Press enter to swap to the galactic view. Your ship is in the centre
of the small white box. The other boxed areas are teams or races.
The circles are the planets. In this screenshot, you goal in the game
is to take control of the red Romulan team planets. Also on this view are:
|
|
The white burst is a torpedo that has just exploded, it it has caused
your damage to exceed 100%, so your ship has started to explode. The
coloured ring around your ship is the start of the explosion. The
green dots are more torpedos from the enemy that would have hit had
you survived.
A short time later, your explosion has engulfed the enemy ship as it expands. This damages the enemy, though not always fatally. Your death is not in vain. You will be returned to the team and ship screen from which you would normally come straight back in with the spacebar. The supply of new ships is endless until your team runs out of planets.
Another three screenshots of a death are below; you have fired a phaser which missed, and the enemy ship number 4 has killed you with a torpedo and a phaser at the same time.
|
sudo aptitude install darcs darcs get http://james.tooraweenah.com/darcs/netrek-client-pygame/Read the netrek/__init__.py file and start making interesting changes.
See what you have changed:
darcs diffRecord and send what you have changed:
darcs record darcs send
Sat Jun 23 23:19:15 EST 2007 quozl@us.netrek.org * add team specific planets Sat Jun 23 21:20:16 EST 2007 quozl@us.netrek.org * default to tactical, isolate reference data, cloak, outfit rejig Sat Jun 23 17:32:34 EST 2007 quozl@us.netrek.org * move shields to sprite, identify torps by team Sat Jun 23 12:56:33 EST 2007 quozl@us.netrek.org * add planet flags, pfiredist ring, font cache Wed Jun 20 23:09:19 EST 2007 quozl@us.netrek.org * add tractor and ship lock Wed Jun 20 22:07:50 EST 2007 quozl@us.netrek.org * add --host, time based torpedo explosion timeout, shields Tue Jun 19 22:41:41 EST 2007 quozl@us.netrek.org * simplify mainline, add orion tactical iconography Tue Jun 19 19:01:27 EST 2007 quozl@us.netrek.org * add galactic ship iconography for testing Add 8x8 iconography on galactic for testing, better images expected later on in development. Tue Jun 19 18:50:00 EST 2007 quozl@us.netrek.org * add torp explosions, fix ship ghosting, add det Add torpedo explosions. Fix ship ghosting caused by ships that change direction not position. Add det others and det own keys. Add practice robot call key. Add orbit key. Add slot number over ship on tactical. Split tactical animation into separate sprite groups. Mon Jun 18 21:48:29 EST 2007 quozl@us.netrek.org * add ship explosions Mon Jun 18 21:10:34 EST 2007 quozl@us.netrek.org * add phaser animation Fri Jun 15 19:37:31 EST 2007 quozl@us.netrek.org * add tactical animation of torps Fri Jun 15 18:59:04 EST 2007 quozl@us.netrek.org * tactical or galactic navigation, right click set course Fri Jun 15 18:37:35 EST 2007 quozl@us.netrek.org * class inversion, tactical flight capability * split sprite and netrek data into separate classes Wed Jun 13 22:03:16 EST 2007 quozl@us.netrek.org * add metaserver phase Tue Jun 12 18:39:11 EST 2007 quozl@us.netrek.org * add remaining packet types Mon Jun 11 21:18:45 EST 2007 quozl@us.netrek.org * repair, shield, login dialog * display modes Sun Jun 10 21:56:43 EST 2007 quozl@us.netrek.org * ideas Sun Jun 10 14:56:44 EST 2007 quozl@us.netrek.org * bomb, beam, cloak Sat Jun 9 23:18:56 EST 2007 quozl@us.netrek.org * oysters open and closed Sat Jun 9 17:19:30 EST 2007 quozl@us.netrek.org * add planet lock and automatic join * add license * convert to sprite usage Wed Jun 6 16:55:36 EST 2007 quozl@us.netrek.org * scout can fly to rom and ghostbust Wed Jun 6 14:12:21 EST 2007 quozl@us.netrek.org * warp zero flight achieved Wed Jun 6 12:44:08 EST 2007 quozl@us.netrek.org * progress, to team selection point Tue Jun 5 23:24:49 EST 2007 quozl@us.netrek.org * test python client, to login phase Tue Jun 5 23:16:54 EST 2007 quozl@us.netrek.org * test python client