Supreme Cmdr

No, that won't fly (under the cover of Uranus? Are you serious?). Anyway, this is not the thread for that and I'm not looking for suggestions. I'll do it myself when I've finished thinking about it. Thanks though!

Blades, in RP terms, a new station is being constructed and everyone has to pack up and leave the old station. Thomas I was using the wrong chart. And the reason I removed one of the stations was because I didn't want the Insurgents to be as powerful as GALCOM. However, since BCM starts off in 3015AD (the next title in the series, is of course, BC:3020AD), I figured, why not. GALCOM+EARTHCOM must have goofed somewhere - not unheard of. Anyway, I've been taking notes because I have to write in the timeline extension to explain: where the hell the Insurgents got the funding from where they got the technology for New America from how they got the Syrions to let them actually build a station in Tarean and where the hell was GALCOM when they were building Destiny - right in our backyard.

OK, sorry guys, I didn't realize that you guys had assets allocated to Destiny. So, I'll put it back - now I gotta find a place for it.

SCID is not a fleet. CIOPS is not a fleet. Where is the confusion Thomas? Or did I miss something?

Yep, the Insurgents are down one station and I've moved some of you slackers into the front lines. Let the moaning beginning. btw, Eclipse, when you do the new FAQ, make sure you make the necessary changes for SCID and CIOPS. Also add the fleet station locations as per the table above. [This message has been edited by Supreme Cmdr (edited 03-20-2000).]

code: * = new/updated [sTARSTATIONS] NAME OBJECT RACE CASTE REGION/SYSTEM =============================================================================== GALCOMHQ GALCOMHQ Terran Military Earth/Sol GENESIS SSTAT3 Terran Military Moon/Sol STARPATH SSTAT3 Terran Military Mars/Sol GAZER1 SSTAT2 Terran Scientist Pluto/Sol ISS * SSTAT4 Terran Military Titan/Sol EARTHSTAR * SSTAT3 Terran Earthcom Europa/Sol DESTINY * SSTAT1 Terran Insurgent Uranus/Sol CENTAURI SSTAT1 Empirian Military Cronus/Alpha Centauri ALERI SSTAT8 Empirian Military Tramis/Alpha Centauri ORION * SSTAT7 Terran Military Centris/Alpha Centauri SYGANS SSTAT2 Terran Insurgent Sygan/Barnard's Star IDAN SSTAT8 Mixed Raider Zilon/Barnard's Star PIXAN SSTAT4 Mixed Raider Lennen/Sirius WRAITH * SSTAT8 Terran Military Lyrius/Syrius ERIDANI SSTAT6 Vesperon Military Canaan/Omicron Eridani RAMIX SSTAT1 Vesperon Military Ramis/Omicron Eridani NEW AMERICA * NEWAMERICA Terran Insurgent Midae/Omicron Eridani TULON SSTAT2 Mixed Raider Arima/Tau Ceti ZERIN SSTAT8 Mixed Assassin Eori/Tau Ceti CENTRON SSTAT2 Mixed Trader Polaris-1/Polaris VELARI * SSTAT7 Terran Military Polaris-2/Polaris PROCYON SSTAT4 Mixed Trader Actis-iv/Procyon PROCIN SSTAT1 Mixed Scientist Actis-v/Procyon VANGUARD SSTAT7 Credian Military Ronus-iv/Trenis BARIN SSTAT7 Credian Mercenary Herin/Trenis ORUNA SSTAT5 Credian Trader Darain/Trenis SPECTRE * SSTAT7 Terran Insurgent Antis/Trenis STARON SSTAT3 Kandorian Military Tyrus-2/Krynon STARWIND SSTAT1 Kandorian Scientist Lydan/Krynon ALLIANCE SSTAT7 Zelon Military Zelana/lanix-v ADONIS SSTAT4 Mandorian Military Pravis/Cyrian NEW FRONTIER * SSTAT5 Terran Insurgent Rinaal/Cyrian DABRIS SSTAT5 Mandorian Military Hadar-9/Cyrian TORON1 SSTAT6 Mixed Scientist Krystar/Tau Ranis TORON2 SSTAT6 Mixed Trader Rebelan/Tau Ranis ARENIS SSTAT8 Mixed Raider Khan/Arenis ELURO SSTAT2 Mixed Raider Chanis-1/Xyon RAGIN SSTAT3 Mixed Assassin Chanis-2/Xyon EXIN SSTAT3 Valkerie Military Kruger/Omega Centauri ALIDIS SSTAT4 Valkerie Military Otura-6/Omega Centauri AVINO SSTAT5 Valkerie Trader Otura-9/Omega Centauri CYGNI SSTAT8 Falkerie Military LV-103/Alpha Cygni HEXAR SSTAT3 Gammulan Military Gamma-1/Gammula GAMMULA GAMMULA Gammulan Military Gamma-2/Gammula SORIUS SSTAT5 Gammulan Military LV-110/Gammula PARIX SSTAT6 Gammulan Military LV-115/Gammula ROGAN SSTAT5 Gammulan Military Chalinis/Alpha Gamma SOVAR SSTAT4 Gammulan Military Mantisi/Alpha Gamma CYCLONE SSTAT2 Valkerie Military Cyron-VI/Cyron ROCON SSTAT7 Gammulan Military Regis-vi/Regulus SARIENS SSTAT1 Syrion Military Sarien/Alpha Canis LV125 SSTAT3 Syrion Scientist LV-125/Alpha Canis LV130 SSTAT4 Syrion Trader LV-130/Alpha Canis ALPHA PRIME * SSTAT2 Terran Insurgent Tarean/Alpha Canis ALTERIS SSTAT5 Syrion Military Alteris/Vega Eridani MONDIALS SSTAT6 Droidan Military Mondial/Omega Eridani RECARA SSTAT8 Droidan Scientist Ylisia/Omega Eridani MAJORISS SSTAT1 Droidan Military Majoris/Alpha Majora [This message has been edited by Supreme Cmdr (edited 03-21-2000).]

Tac, time's up. Lyrius/Syrius it is.

Ristar, lets call it Central Intelligence OperationS, CIOPS, pronounced: siops There, problem solved. Eclipse, please update the fleet FAQ accordingly, and send me an update to repost. [This message has been edited by Supreme Cmdr (edited 03-20-2000).]

LOL!!, I've heard it all now. heh, an F never looked so good. Can't wait to see it.

OK, so, let me get this straight. You guys have decided, all on your own, to create an organization within my world, without my approval? GCIA no less??? SCID stays in EarthCOM. Thats the end of that story. I will be removing the fleet page in a few mins as it is no longer a fleet. Ristar, as for your ragtag division, I see what you're getting at but (1) I do not like GCIA (2) I'd rather you guys didn't about restructuring my assets without my permission. Yes, I got all the emails you sent me about this but I have not responded because I have not given it any thought. So, until I think about it and come up with my own section name - GCIA is not happening. Thats the end of that. Everyone go home.

I never thought I'd live to see the day when Tac would make a good argument that didn't warrant a one-line from me OK, let me know where you want to locate it. And like I said, I don't want to see the towing bill or am handing out pink slips

Karl has a point. Make it so.

SCID is no longer a fleet by itself, so I will be renaming the SCID station to something else and giving Earthcom, one more station. More details later this week. The UCV guys don't need a station because they have access to any raider or assassin station. Tac, whatever you do, just make sure Wraith doesn't send GALCOM that towing bill. [This message has been edited by Supreme Cmdr (edited 03-20-2000).]

I just saw a post in which Tac was talking about leaving Rinaal. I don't usually pay more 5% attention to Tac's whining, so, can someone tell me whats wrong with Rinaal and how this came about? Sure, I can move the station - as soon as GALCOM clears up its account with the ACME Galactic Moving Co. But I need a good reason - and I do mean - good.

As of today, you can now use any of the content screen shots on your webpage. This means that you can now use screen shots of the new stations. Speaking of stations, all the station fleet models were picked by me, for v2.0x. Below, you will find the table of stations in BCM. It contains the new Insurgent stations but I will be adding about 5 more stations for raiders and other castes, for multiplayer balancing. Anyway, Tac was asking in another thread, about picking a station. So, Fleet Leaders, you have my permission to pick any of the 8 station models, for your station HQ and I will update this table in the game. This does not apply to Prime (galcomhq) and Insurgent (New America). All other station object selections, including the yet to be allocated ones for the Insurgents and other castes, will be handled by me - so don't ask. Tac, you said you wanted Type 8, but I have not changed the table yet - giving you time to make up your mind. Here are the images of all types, you can use this as the main pic for your website, as well as any of the other ones on the screen shots page. www.bc3000ad.com/fleets/ghq.jpg www.bc3000ad.com/fleets/gammula.jpg www.bc3000ad.com/fleets/newamerica.jpg www.bc3000ad.com/fleets/sstat1.jpg www.bc3000ad.com/fleets/sstat2.jpg www.bc3000ad.com/fleets/sstat3.jpg www.bc3000ad.com/fleets/sstat4.jpg www.bc3000ad.com/fleets/sstat5.jpg www.bc3000ad.com/fleets/sstat6.jpg www.bc3000ad.com/fleets/sstat7.jpg www.bc3000ad.com/fleets/sstat8.jpg [This message has been edited by Supreme Cmdr (edited 03-20-2000).]

You're only just finding out that the docs are not complete? Have you not been paying any attention? The GBSTOC.TXT file is complete and lists all the commands - it doesn't show their usage. You're on your own because I don't have time for that. You can read my scripts and be able to figure out how the commands work. You already have all the syntax. No, I don't have icons.

Using the .3DT file is dangerous and not advisable. For instance, in that tutorial I just posted, you would have to manually put in the entry for a new group, alter the numbering etc. You have been warned.

In order to create new links, you have to: Edit the region .3D file and add the jump anomaly in the file. Add the anomaly links in STATICS.SCR Do a PREPALL eg. to put a new jump point called JMP-100 which links Earth to Majoris, you would use these steps: Fire up TEDWIN and from the FILE menu, change directories to REGIONS. Note: Be sure you remembered to edit BCTOOLS.INI to match your install paths before running TEDWIN. Be sure you backed up the GBS files. Now that you've changed folders, from the UNIT menu, select Terrain Mode Toggle so that the actual region is not zoomed. For normal .3D models, you don't need to do this, but you do when editing region .3D files. Since EARTHZ.3D already contains the jump anomaly sub-group objects, you would simply use call up group from the GROUP menu, load the jump.3d object from the menu list and just plonk it anywhere in the scene with a left-click. Note: You will notice that the FLUX.3D and WORMHOLE.3D model groups are not in the groups list for EARTHZ - this is because there are no flux fields or wormholes in the Earth space region. If you wanted to put these kind of entities in there, you would need to use the MERGE GROUPS command to load them in. Now, use the create identifier command, type in JMP-100, press enter and then double-left-click on the jump point you placed in the file. It will now be renamed. Note: any group that you now place in this scene, will have the name JMP-100!! To clear this identifier, use the command again but press ESCAPE at the prompt. This will clear it. I color code all my entities just for readability. So if you want to match the color of this entity, left-click in color 4 (red), use the copy attributes and left-click on the JMP-100 entity to change the color from Green to Red. From the right-click menu, SAVE, the file You now have a jump point in the Earth region. Now to match it.. From the FILE menu, load up MAJORISZ and use the same method to put another instance of JMP-100 in this file. But...you will notice that this region does not currently contain jump points, so you would need to use the MERGE GROUPS command to load in the JUMP.3D object from the prompt. Just type JUMP.3D from the *.3D prompt because if you press ENTER, it will list every model in the REGIONS list and you will take awhile to find JUMP.3D. Then, use the method above to place it in the scene and color it. Note: If you cleared the JMP-100 identifier when you did EARTHZ, you would need to repeat those steps Notice that since MAJORISZ contains flux fields and wormholes, you will see these list if you do a GROUP LIST. You won't see the JUMP.3D entity because by default, it does not contain any jump points and there was no need to merge that object in it. Exit TEDWIN. You're all done here. Now, on to STATICS.SCR. Load it up in a text editor, eg Notepad Go to the Earth section around line 114 and after the last entry (fld-03), enter this: jmp-100,j,earthz:To..Majoris Go to the Majoris section around line 1275 and after the last entry (fld-73), enter this: jmp-100,j,majorisz:To..Earth Run PREPALL and copy the BC3LIB4.RES file to your BC3K runtime folder. And if you did everything right, you should now have a jump point that takes you clean, clear across the galaxy to Majoris. It is important to note that: jump points and wormholes use the same technology internally. I differentiate them in order to maintain the integrity of the galaxy by saying that jump points link regions and wormholes link systems. Which is why, above, though I would have told you to use a wormhole instead, I used jump point to show you the flexibility of the design and technology. So, if you want to maintain the integrity, you may want to use a wormhole instead of a jump point, just be sure to take a look at the STATICS.SCR file because they both use different parameters.Fluxfields are a whole different ballgame - go experiment. The named identifier of all anomalies must be unique. I used JMP-100 as an example only, there may be one already in the STATICS.SCR file. When in doubt, check for the last highest number for JMP-, FLX- and WRM- entries in that file. And don't even think of putting in planets, moons etc (by merging in the PLANET.3D and/or MOON.3D files). While it will work (you can put another planet in the EARTHZ region), without modifying the PTE .CFG files, entering this new region will either cause a crash or it will fall back to using the default values - meaning that all your surfaces will look the same. Creating surface regions is a lot more complex. [This message has been edited by Supreme Cmdr (edited 03-19-2000).]

quote: I'm now starting a project called GBS edit. Currently I'm working on letting the user edit and add new regions. I will read statics.scr into my own strucutre, this way I will be able to modify existing regions, like adding jump-point... GBS edit will then write the modified data into a new script. The user then include this script instead of static.scr. The program will also make changes to the 3D files. The problem with this is that the user will have to run a bat file which convert the new 3dt files into 3D files. You won't be successful. STATICS.SCR just lists the links so that the AI route-finding logic, has data to work with. So, putting in a jump point or any anomaly for that matter, in that file only, won't work. In order to make it work, you have to read the tutorial I'm doing in 2 mins. [This message has been edited by Supreme Cmdr (edited 03-19-2000).]

The entire game runs on an AI based OS, that is why it slows down when there are a lot of NPCs around. However, the slowdown experienced on a PIII should be virtually un-noticeable unless another process is running on that machine. For instance TCP/IP stack (if you're on a network, disconnect all shared folders), Fast Find (which can be disabled in Control Panel) etc

As far as I know, it is available all over Australia. Call around or contact Jack Of All Games for the dealer nearest to you.

Probably a bad patch. And why didn't you go up to 2.09? Also, did you see in the FAQ or the version control file where it says to delete the setup.cfg and joystick.set files when you upgrade your patch from scratch?

quote: Are you still doing this? If it's too trouble forget it then. No. The station names in BC3K v2.0x are hard coded in the kernel because they are used for the economics database. However, you might be able to cheat by giving the CVD name (the last parameter for the object ID definition in the [AI] block) for the object, one of those used in the kernel. Try galcomhq first and see if that works. If it does, when you dock with your station, it will think you are docked at galcomhq. Dunno if it will work though. quote: I playing around with TED too. Shooo, one hella of an interface S.C Yep, its a programmers tool. quote: BTW does Glob_gn.scr have anything to do with this? It defines attrubites for the regions, like tech-level, inflation level, defense point, etc... No, glob_rg.scr does not need to be modified. It is only used by the PTE database. Here is the list of starstation names as used in the code. I'm just cutting and pasting the array from the source code. code: // // dock launch animation/station names // struct { char *cvd_name;char *region;int is_starstation;} stations[] = { {"GALCOMHQ","EARTHZ",1}, {"GENESIS","MOONRZ",1}, {"STARPATH","MARSZ",1}, {"GAZER1","PLUTOZ",1}, {"CENTAURI","CRONUSZ",1}, {"ALERI","TRAMISZ",1}, {"SYGAN","SYGANZ",1}, {"IDAN","ZILONZ",1}, {"PIXAN","LENNENZ",1}, {"ERIDANI","CANAANZ",1}, {"RAMIX","RAMISZ",1}, {"TULON","ARIMAZ",1}, {"ZERIN","EORIZ",1}, {"CENTRON","POLAR1Z",1}, {"VELARI","POLAR2Z",1}, {"PROCYON","ACTISIVZ",1}, {"PROCIN","ACTISVZ",1}, {"VANGUARD","RONUSIVZ",1}, {"BARIN","HERINZ",1}, {"ORUNA","DARAINZ",1}, {"STARON","TYRUS2Z",1}, {"STARWIND","LYDANZ",1}, {"ALLIANCE","ZELANAZ",1}, {"ADONIS","PRAVISZ",1}, {"DABRIS","HADAR9Z",1}, {"TORON1","KRYSTARZ",1}, {"TORON2","REBELANZ",1}, {"ARENIS","KHANZ",1}, {"ELURO","CHANIS1Z",1}, {"RAGIN","CHANIS2Z",1}, {"EXIN","KRUGERZ",1}, {"ALIDIS","OTURA6Z",1}, {"AVINO","OTURA9Z",1}, {"CYGNI","LV103Z",1}, {"HEXAR","GAMMA1Z",1}, {"GAMMULA","GAMMA2Z",1}, {"SORIUS","LV110Z",1}, {"PARIX","LV115Z",1}, {"ROGAN","CHALINIZ",1}, {"SOVAR","MANTISIZ",1}, {"CYCLONE","CYRONIVZ",1}, {"ROCON","REGISVIZ",1}, {"SARIEN","SARIENZ",1}, {"LV125","LV125Z",1}, {"LV130","LV130Z",1}, {"ALTERIS","ALTERISZ",1}, {"MONDIAL","MONDIALZ",1}, {"RECARA","YLISIAZ",1}, {"MAJORIS","MAJORISZ",1}, {"WRAITH","RINAALZ",1}, // Wraith fleet HQ (GALCOM) {"ORION","JUPITERZ",1}, // Orion fleet HQ (GALCOM) {"ISS","SATURNZ",1}, // ISS fleet HQ (GALCOM) {"SCID","CENTRISZ",1}, // 15th SCID Planetary Force HQ (EarthCom) {"SPECTRE","ANTISZ",1}, // Spectre fleet HQ (Insurgent) {"EARTH","EARTH",0}, // Surface starbases start here... {"MARS","MARS",0}, {"CENTRIS","RONUS-IV",0}, {"VARAX","VARAN",0}, {"TRAMIS","TRAMIS",0}, {"SYGAN","SYGAN",0}, {"LYRIUS","LYRIUS",0}, {"BADRAN","MIDAE",0}, {"FRELLIS","FRELLIS",0}, {"XYLAN","XYLAN",0}, {"CARON","EORI",0}, {"POLARIS-1","POLARIS-1",0}, {"ELTIN","ACTIS-IV",0}, {"ACTIS-V","ACTIS-V",0}, {"TRENIS","RONUS-IV",0}, {"BELIN","HERIN",0}, {"SCORPIA","SCORPIA",0}, {"SIMPIX","TYRUS-2",0}, {"KRYNON","LYDAN",0}, {"LANIX-V","ZELANA",0}, {"CYRIAN","PRAVIS",0}, {"HADAR-9","HADAR-9",0}, {"TAU RANIS","KRYSTAR",0}, {"ARENIS","KHAN",0}, {"XYON","CHANIS-1",0}, {"OMEGA-9","LV-184",0}, {"ALIDIS","OTURA-6",0}, {"ALPHA CYGNI","LV-103",0}, {"LV-105","LV-105",0}, {"GAMMA","GAMMA-1",0}, {"GAMMULA","GAMMA-2",0}, {"TYRINIS","TYRINIS",0}, {"LV-110","LV-110",0}, {"ALPHA GAMMA","CHALINIS",0}, {"CRYSTAR","CRYSTAR",0}, {"CYRON-VI","CYRON-VI",0}, {"REGULUS","REGIS-IV",0}, {"SARIEN","SARIEN",0}, {"TAREAN","TAREAN",0}, {"OLINDA","DROIA",0}, {"YLISIA","YLISIA",0}, {"MAJORIS","MAJORIS",0}, {NULL,NULL,1} };

Rattler, Insurgents don't have the same rank structure as GALCOM forces - in fact, I'm not aware of any ranks for them at all. So, if you guys want to send me a rank proposal for you misfits, pass it on. And am still waiting for those final fleet structures, as well as the single email with all links to the fleet structure html pages on the respective sites. What exactly is the hold up?

....and whats cool about it?