Knowledge

Empire (1973 video game)

Source đź“ť

176:, was written by Iowa State student John Daleske as project coursework for an education class in the Spring of 1973. Silas Warner helped out by providing Daleske with disk space (known as "lesson space" in the PLATO environment). The first version of the game was a strategic turn-based game for a maximum of eight players. Each player was the head of their government, had ships (for both trade and war), industry, and budgets. Players had to keep the budget up to build more ships, maintain industry to help pay for it, provide raw materials to turn into goods, and trade. This was likely the earliest example of an online, multi-player, interterminal computer game. Games prior to this were two player or one player against a computer. 131:
own torps. Since the players could only have a limited number of torps active at any time, the original attacker would have to detonate his torps and launch new ones in order to respond. Of course, an experienced player, knowing that this was likely to happen, would likely have already detonated his first cluster of torps and launched a new set, hoping that his opponent would hyperjump right into them—except that the opponent, knowing this, would do something slightly different. The best players could get inside the heads of other players, figure out what they were going to do, influence them to do certain things, and destroy them.
123:
screen updated, but could not delay this action more than 10 seconds, or execute more than a certain number of commands before an update was forced. The position of each ship was updated only when its player updated his screen, which permitted ships to discontinuously hop or "hyperjump". Conversely, torpedo locations updated whenever any player in the game updated their screen, so their movements were effectively continuous.
135:
Orbiting a friendly "Class-M" planet increased the fueling rate, so defenders could unleash a blizzard of torps—but conversely, this meant that they were all in a known location, and a single attacker who hyperjumped just right could unload his torpedo tubes on all the defenders (Torp damage was area-of-effect), "clearing" the planet and racking up multiple kills. This and other aspects of the game were very well balanced.
96:(In the VAX Conquest variant, which features engine and weapons temperature statistics, Federation ships have the highest overall speed; Klingon weapons do the most damage; Orions can "cruise" at a faster speed than others without engine overheat; and Romulans can fire weapons more often without weapon systems overheating.) 107:. Phasers fire in a cone shape and do damage immediately, while torpedoes take some time to reach their target and can be dodged. Torpedoes can also be detonated before they strike. When a player is killed, they resurrect in a new ship in their home system, or in any home system that has been conquered by their team. 53: 134:
Things were further complicated by the fact that a ship's fuel supply was limited and regenerated fairly slowly; just flying at maximum warp would deplete a ship's fuel supply in minutes. This meant that one had to decide when it was profitable to fire torpedoes, fire phasers, or even to move at all.
114:
can be slow to play, and moves have to be carefully and yet quickly considered. Flying from a team's home space to engage the enemy could take one to two minutes, and bombing a planet with fifty armies could take five to ten minutes. A game might take many hours, or even days, as players come and go.
83:
Each team is given three adjacent planets as their home system. Each home system is located towards one corner of the map, which was many screens in size, and thus has two other teams relatively nearby. There are two neutral worlds between each team and its two neighbors, and five more neutral worlds
150:
players would obtain more CPU for game play by logging in hours before commencing game play and leaving the session idle, thereby accumulating a very low CPU used/session duration ratio that would ensure high CPU allocation to the player during game play. Players who did not engage in this practice
145:
scheduling algorithm. Plato attempted fair allocation of the limited CPU resources available by calculating for each user the ratio of the total CPU time used during a session divided by the total duration of the session. The system would grant extra CPU time to sessions with lower CPU time/session
122:
Original PLATO terminals were connected to the host system with a 1200 baud connection, and the host computers were quite slow by current standards. Since an update of the screen could take one to two seconds with a lot of ships and torpedoes on the screen, players were allowed to decide when their
95:
friendly armies to transport them, and beam down armies to take over planets. The ships of each race have slightly different capabilities; Orion ships have the weakest weapons but are fast, Roms have the strongest weapons, but are the slowest, and Fed and Kazari ships have medium speed and strength.
130:
a great deal of tactical depth by making it a limited-information game. For example, a player, seeing torps launched towards him, could wait without replotting until they were about to be hit, then change course towards the attacker, go to maximum speed, and hyperjump over the torps, then fire his
209:
in a 36-hour programming blitz, completing the effort in early 1974. This version of the game, with a few minor modifications (newer looping constructs replace branches, and a timing issue has been corrected) may still be played on the Cyber1 PLATO system. In this version of the game, the internal
161:
included Strategic play, where the goal was to take over all planetary systems, thus forming an empire. This was achieved by building up armies on one's friendly planets, expanding to non-controlled planets, bombarding enemy planets, and eventually beaming down armies transported from one's own
79:
The object of the game is to conquer the galaxy. This galaxy contains 25 planets and 4 races. The races were the Federation, Romulans, Orions, and (originally) Klingons. The fourth race was changed to Kazari, just prior to publication because the game authors were worried about copyright
196:, written in the Fall of 1973, was substantially different, much more tactically oriented. Players each captained a starship and could fire torpedoes at each other. Silas Warner liked the earlier version, and with Daleske's permission resurrected it under the name 210:
physics are greatly improved, and the player's ship is always shown in the center of the tactical screen. Up to seven teams and fifty players could participate. Players could opt to be in an eighth "rogue" or non-affiliated team.
219:, which allowed for live chat between players. In 1981, Steve Peltz wrote a tournament version of the game, which allowed for annual tournaments between teams. These were most often won by the Orion team. 68:
headings, with 0 being to the right, 90 up, 180 left, and 270 down. The "arrow" keys, clustered around "s", could also be used (e.g. "qw" being the same as 113 degrees). PLATO terminals had 512 by 512
64:
Although PLATO terminals had touch panels, they did not have mice, and all control in the game is via typing. Commands involving directions to change course and fire weapons are entered as
84:
in the middle of the galaxy. Each planet given to a team contains 50 armies at the start of the game, while the neutral planets start off with 25 self-ruled armies.
415: 420: 376: 213:
The game was substantially revised in 1976 by a team led by Chuck Miller and Gary Fritz, including John Daleske and Jim Battin; by 1977, they produced
230: 226: 87:
Up to 30 players could be in the game at once, with no more than 15 players on a team. Each player is given a starship to pilot. Players
353: 80:
infringement. In 1991, the fourth race name was changed back to Klingon on the NovaNET system, but remained Kazari on the CDC systems.
126:
This simple game mechanic, forced upon the designers by the limitations of the terminal and the central computer, paradoxically gave
410: 368: 200:. The initial versions were written in longhand, with no printouts available as Daleske was at a remote computing center. 358: 119:
conditions, players have been known to type as quickly as 20 keys per second (as fast as the system would take them).
330: 425: 405: 100: 162:
friendly planets. This all while being attacked by potentially three other teams at many fronts.
400: 142: 92: 25: 40: 32: 76:
vector CRT display screens, and could use downloadable character sets to display graphics.
146:
duration ratios at the expense of sessions with higher CPU time/session duration ratios.
8: 29: 302:) can still (as of the late 1990s) be found on the NovaNET PLATO systems. In 1982 38:-style game. It may also be the first networked multiplayer action game (although 334: 287: 282: 35: 152: 139: 104: 65: 381: 52: 394: 327: 303: 277:
was adapted with emailed permission from Chuck Miller and Gary Fritz for the
233:
indicate that between 1978 and 1985, users spent about 300,000 hours playing
349:- Development and History of the First Networked Multiplayer Computer Game 344: 339: 73: 278: 116: 88: 225:
was a very popular game. Usage logs from the PLATO system at the
315: 60:
screenshot from the "PCA vs CERL" tournament held August 18, 1984
269: 377:
The History of Computer Gaming Part 5 - PLATO Ain't Just Greek
28:
in 1973. It is significant for being quite probably the first
70: 363: 242: 203:
In late 1973, Daleske rewrote the game again, creating
138:Game play was also affected by the Plato system's 91:each other, destroy enemy armies by bombing them, 392: 24:is the name of a computer game written for the 241:is still played (as of 2013) on the system at 44:is another possibility for this distinction). 416:Computer-based Education Research Laboratory 227:Computer-based Education Research Laboratory 421:Video games developed in the United States 251:inspired many derivative games, including 328:PLATO: The Emergence of On-Line Community 188:but Silas Warner revived it as Conquest. 51: 393: 182:was originally erased and replaced by 306:wrote a version of the space-battle 13: 14: 437: 99:Ships have two kinds of weapons: 1: 411:PLATO (computer system) games 321: 155:due to relative lack of CPU. 151:were burdened with poor game 7: 47: 10: 442: 165: 340:PLATO: The Proto-Internet 110:Although an action game, 426:Multiplayer video games 359:rec.games.netrek thread 61: 372:History by Gary Fritz 364:Cyber1.Org PLATO site 55: 170:The first version, 333:2015-07-18 at the 62: 354:History of Netrek 285:as a game called 140:context switching 433: 406:1973 video games 115:Yet, in intense 105:photon torpedoes 441: 440: 436: 435: 434: 432: 431: 430: 391: 390: 335:Wayback Machine 324: 288:Galactic Attack 283:Robert Woodhead 168: 50: 17: 16:1973 video game 12: 11: 5: 439: 429: 428: 423: 418: 413: 408: 403: 401:Apple II games 389: 388: 379: 374: 366: 361: 356: 351: 342: 337: 323: 320: 243:www.cyber1.org 167: 164: 153:responsiveness 49: 46: 15: 9: 6: 4: 3: 2: 438: 427: 424: 422: 419: 417: 414: 412: 409: 407: 404: 402: 399: 398: 396: 387: 385: 380: 378: 375: 373: 371: 367: 365: 362: 360: 357: 355: 352: 350: 348: 343: 341: 338: 336: 332: 329: 326: 325: 319: 317: 313: 309: 305: 304:Jef Poskanzer 301: 297: 292: 290: 289: 284: 280: 276: 272: 271: 266: 262: 258: 254: 250: 246: 244: 240: 236: 232: 228: 224: 220: 218: 217: 211: 208: 207: 201: 199: 195: 194: 189: 187: 186: 181: 180: 175: 174: 163: 160: 156: 154: 149: 144: 141: 136: 132: 129: 124: 120: 118: 113: 108: 106: 102: 97: 94: 90: 85: 81: 77: 75: 72: 67: 59: 54: 45: 43: 42: 37: 36:arena shooter 34: 31: 27: 23: 22: 383: 369: 346: 311: 310:game called 307: 299: 295: 293: 286: 274: 268: 264: 260: 256: 252: 248: 247: 238: 234: 222: 221: 215: 214: 212: 205: 204: 202: 197: 192: 191: 190: 184: 183: 178: 177: 172: 171: 169: 158: 157: 147: 137: 133: 127: 125: 121: 111: 109: 98: 86: 82: 78: 63: 57: 39: 26:PLATO system 20: 19: 18: 318:computers. 117:dogfighting 33:multiplayer 395:Categories 322:References 298:(based on 229:(CERL) at 206:Empire III 74:monochrome 382:Video of 216:Empire IV 193:Empire II 185:Empire II 159:Empire IV 30:networked 331:Archived 312:Conquest 300:Empire I 296:Conquest 279:Apple II 261:ROBOTREK 198:Conquest 179:Empire I 173:Empire I 89:dogfight 48:Gameplay 41:Maze War 316:VAX/VMS 166:History 101:phasers 93:beam up 386:battle 384:Empire 370:Empire 347:Empire 345:PLATO 308:Empire 294:PLATO 275:Empire 270:Netrek 267:, and 257:Trek83 253:Trek82 249:Empire 239:Empire 235:Empire 223:Empire 148:Empire 128:Empire 112:Empire 66:degree 58:Empire 21:Empire 265:Xtrek 71:pixel 314:for 231:UIUC 103:and 281:by 237:. 143:CPU 56:An 397:: 291:. 273:. 263:, 259:, 255:, 245:.

Index

PLATO system
networked
multiplayer
arena shooter
Maze War

degree
pixel
monochrome
dogfight
beam up
phasers
photon torpedoes
dogfighting
context switching
CPU
responsiveness
Computer-based Education Research Laboratory
UIUC
www.cyber1.org
Netrek
Apple II
Robert Woodhead
Galactic Attack
Jef Poskanzer
VAX/VMS
PLATO: The Emergence of On-Line Community
Archived
Wayback Machine
PLATO: The Proto-Internet

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.

↑