Aces High Bulletin Board
General Forums => Aces High General Discussion => Topic started by: Karnak on November 05, 2001, 06:47:00 PM
-
Remove all dots and bars from the map. Leave the position indicator as there aren't enough terrain features to navigate without it. Rplace all the dots and bars with the following text based system.
Here are a few walk throughs:
Field radar, or where to get the detailed info:
1. Player types ".vector 15" (This command asks field 15 to vector him/her onto the nearest enemy)
2. Ground control AI replies with one of the following statements:
a) Radar is down at field 15. (This is used if radar is down at the field)
b) Rook radar is down. (This is used if the nation's entire radar net is down)
c) Contact, 30 miles, 150 your bearing, heading 225, angels 15, speed 330. (This would be used to direct the player towards a contact, distance would be reported to the nearest 5 miles, bearing and heading would be reported in 15 degree increments, altitude to the nearest 3,000 feet and speed in 30mph increments)
d) Multiple contacts, 25 miles, 135 your bearing, heading 240, angels 21, speed 270. (This would be used to direct the player towards the contacts, distance would be reported to the nearest 5 miles, bearing and heading would be reported in 15 degree increments, altitude to the nearest 3,000 feet and speed in 30mph increments)
e) Contact in visual range. Good luck. (This would be used if the contact was within visual range, meaning dot range, of the player)
f) Contacts in visual range, good luck. (This would be used if the contacts were within visual range, meaning dot range, of the player)
The player could request updates as often as wished, but no information would be given once the contact/contacts were within visual range other than the fact that they are within visual range.
Ground observers, or the new "Bar Dar":
1. Player types ".observer 1"
2. Ground control AI replies with one of the following statements:
a) Observers report no enemy activity.
b) Observers report light enemy aircraft activity.
c) Observers report moderate enemy aircraft activity.
d) Observers report heavy enemy aircraft activity.
e) Observers report light enemy ground activity.
f) Observers report moderate enemy ground activity.
g) Observers report heavy enemy ground activity.
h) Observers report light enemy air and ground activity.
i) Observers report moderate enemy air and light enemy ground activity.
j) Observers report heavy enemy air and light enemy ground activity.
k) Observers report light enemy air and moderate enemy ground activity.
l) Observers report moderate enemy air and ground activity.
m) Observers report heavy enemy air and moderate enemy ground activity.
n) Observers report light enemy air and heavy enemy ground activity.
o) Observers report moderate enemy air and heavy enemy ground activity.
p) Observers report heavy enemy air and ground activity.
q) Rook communication network is down.
Offensive opperations, or the Big Picture 1:
1. Player types ".hq ops" (This command requests info from the HQ on where major offensive operation are occuring)
2. HQ determines which enemy controled sectors have a high concentration of friendly units, say 5 units, and then reports something like :
a) HQ is down. (This indicates that the HQ has been destroyed and cannot direct operations)
b) There is no offensive underway at this time. (This is used to indicate that no major offensive opperations are underway at this time)
c) Offensive in progress in sector 8, 11. (This is used to indicate that an offensive is occuring in that sector)
d) Offensives in progress in sectors 6, 8; 8, 11 and 9, 13. (This is used to indicate that multiple offensive operations are underway at this time)
Defensive operations, or the Big Picture 2:
1. Player types ".hq vector" (This command requests information on large enemy incursions into friendly territory)
2. HQ determines which friendly controled sectors have a high concentration of enemy units, say 5 units, and then reports something like :
a) HQ is down. (This indicates that the HQ has been destroyed and cannot direct operations)
b) No sectors are under attack at this time. (This is used to indicate that no major enemy activity is underway at this time)
c) Sector 10, 7 is under attack. (This is used to indicate that enemy action is occuring in that sector at this time)
d) Sectors 10, 7; 11, 10 and 13, 11. (This is used to indicate that enemy action is occuring in that sector at this time)
What are your thoughts about this system?
[ 11-05-2001: Message edited by: Karnak ]
-
Sounds great for the CT or a scenario (really great, actually).
Not for the every day MA.
If it ain't broke, why fix it?
On line is not off line campaign play.
-
Sorry if I offend, but I have no desire to play with WWII aircraft in a constant typing environment where i have to watch the text more than the air around me and will make statements pointing out how silly that desire is whenever somebody expresses it.
-
Karnak,
The idea is good but I think the first two actually take to much time away from the flying. Why not just have the HQ broadcast a message on what is happening in the areas of the country like you propose in Offensive and Defensive Ops. That way seems to be the least time consuming for all involved.
I will say this about it. If the HeadQuarters is down then your country gets no updates at all until it is back up.
-
I think the idea has merit but is not very well suited to an MA, more a CT kind of setup IMO. I would change it slightly though. Make the HQ reports a radio channel you can tune to, like an AWACS frequency. Constantly having to type in requests would get very cumbersome quickly.
-
i think radar should be just like european air war, falcon 4, etcera
"tophat control, this is red 5. request vector to nearest bandit"
"red 5, this is tophat control. multiple bandits bearing 330 10 miles angels 16"
all with wav files. like other games. use the standard numerical menu system.
YES i want radar in a ww2 sim. NO i dont want a HSD, something pilots even in vietnam did NOT have.
-
I guess I could live with audio ground controller instructions, but definitely not text based. There is WAY too much <cough> noise in the radio buffer these days for text based instructions.
However, I think the system we have is just fine. The only changes I would make is to put a minimum altitude limit on bar dar, and delay updates of dot dar by 30 seconds or so.
-
Leave the dar alone. There is no time to be constantly checking an overloaded text buffer for "vectors".
I use RW to talk to my squaddies in an operation. Tere is enough chatter in a battle as it is. I don't need nor want additional game generated voices cluttering up the vox.
(http://www.13thtas.com/mav13sig.jpg)