1 -=O EMPIRE WISH LIST O=-
3 This is the complete Empire Wish List. Each item on the wish list has
4 been given a unique reference number. The reference number does not
5 indicate priority; it is only there so that we may easily refer to
6 various items on the list. The reference numbers are permanent, and
7 any new item added to the wish list in the future will be given a new
8 unique reference number.
10 The blank index number at the bottom of each section refers to the
11 next available index number for that section.
13 Note that the most radical have been moved out of the EMPIRE WISH LIST
14 and onto the EMPIRE WACKY IDEAS LIST which shares the same indexing system
17 _________________________________________________________________
19 --- TABLE OF CONTENTS ---
21 Attack, Assault and Board.................a
22 Missions..................................m
23 Ships.....................................s
24 Planes....................................p
25 Land Units................................l
26 Commodities and Sectors...................c
27 Information Commands......................i
28 Telegrams, Announcements, News............t
29 Updates...................................u
30 Deity.....................................d
31 Miscellanious and Documentation...........x
32 Error Messages............................e
34 --- ATTACK, ASSAULT AND BOARD ---
37 aborting an attack should cost you btus or possibly mobility
38 (otherwise you get info for free).
45 Allow people to specify relation level to trigger different missions
46 (note there is already space for this in the nation struct).
53 For ship/plane/unit specification, allow a/13/b/15/16/c type
54 specification where fleets, wings, and armies may be included along
55 with numbers. (WARNING: This would require massive restructuring.)
58 once ships on sail have arrived at their destination, the "Your fleet
59 lead by ship #x has reached x,y." in production report every time.
62 Another suggestion related to s21. The gain in efficiency of planes on
63 carriers or sufficiently crewed ships on sea should use construction
64 materials etc. This is to make it consistent with land units gaining
65 efficiency in a sector where the necessary materials are present.
66 Otherwise it leads to abuse: Say in the beginning of the game I build
67 a ship but don't want to spend the hcms to build it completely - so I
68 just crew it it will gain efficiency by itself. I think it could
69 easily be implemented by giving every ship some capacity for lcms and
77 chh [38:382]% scrap p 28,0 ?eff<50
78 Really scrap all planes in 28,0 [n]? n
79 The prompt is misleading. (Same goes for scuttle). Scuttle and scrap
80 should probably be consolidated.
87 perhaps since land units in mountains are so hard to attack, we shuold
88 just not let land units into mountains to begin with.
92 --- COMMODITIES AND SECTORS ---
95 Change bridges (and towers) so that they only crumble when shelled
96 below 15%. Allows attackers an extra chance for a bridge attack.
100 If a sector in <SECTS> needs more food, send it food from <SECT>.
102 c16 - WARNING - may be difficult to code
103 forts should return fire even if shot missed
107 --- INFORMATION COMMANDS ---
110 neweff [s <SHIPS>|p <PLANES>|l <UNITS>] to show the efficiency these
111 things will have after the update. At present you can only get this
112 info by doing some heavy calculations.
116 lists sectors that need more food if they want to attain maximum civ
121 should list the commodities consumed in f h * ! sectors for building
122 stuff. (This would help you calculate your production deltas.)
126 to show enemy ships (that you would see with radar or coastwatch).
130 to show enemy satellites (that you would see on radar).
134 should give you the oldown number, rather than just a *. (Does dump
135 only give you a * if you're not the oldown? I don't know. You can find
136 the oldown using ?oldown= so dump should give it to you).
139 radar [<SHIPS> | <SECTS>] S
140 shows enemy ships but not your own.
143 cen * ?connect=<SECT>
144 lists all sectors connected by land to <SECT>. Handy for setting up
148 Allow | as well as & in selection syntax. e.g. res * ?des=o|des=g
149 (WARNING: cannot use single bar as the or character because "|" is
150 used as a pipe in the standard client and possibly in other clients.
151 Another character should be used instead ( or maybe "||"?)
155 --- TELEGRAMS, ANNOUNCEMENTS, NEWS ---
158 Separate BULLETIN's from Telegrams (so that when we're in the middle
159 of a fight we will know if we were just attacked or we simply have
160 just received a letter from a friend).
163 When you are writing a telegram or an announcement and an update hits,
164 then your telegram or announcement gets lost. ( is it even POSSIBLE to
172 Planes should not be built by conquered populace. (The problem here is
173 that building planes uses mil, and you can lose the sector because all
174 your mil that was being used to hold the sector disappeared into the
175 planes so you loose the sector at the update.) ALREADY FIXED?
182 Add che (target and number) to deity dump format.
186 --- MISCELLANIOUS AND DOCUMENTATION ---
189 Often BTU's aren't updated immediately, and the prompt is out of sync
190 with the actual amount of BTU's they have.
193 info takeover, avail, loyalty
194 There should be man pages on these.
198 --- ERROR MESSAGES ---
201 _________________________________________________________________
203 If you have any comments/additions regarding this list, mail them to
204 me at wolfpack@wolfpackempire.com with the word "wish" in the subject line.
208 Last updated: January, 1999