Topic: Announcing Slave Girls of Orion VIII

[Braxton_RIP]

Oh, thought u  signed off on that already. Yeah, SFHQ has been helping me along. He went thru the entire OCI code to make sure it's solid for this server. I think we should give it a shot. I'm about to D/L the config file for the OCI soon and tweak it then pass it along to you for review.

 I got no problem with using SQL, just that I won't be able to do much.   I say we go for it, the player base will be so small at this pont that I can't imagine us crashing the server.

*Points for reference* http://www.dynaverse.net/forum/index.php/topic,163378365.0.html

[Dizzy]

Want some feedback if DH and I rewrite this rule.

Disengagement/Destruction Rule

- If you are forced to Disengage in a PvP match, then you are banned from the hex you either took the mission in or were drafted in and all the hexes adjacent to that one for 15 turns. If your ship was destroyed then you are banned from that hex and all adjacent hexes for 8 turns.
- If you draft or are drafted while moving out of an area you have been banned in, the mission is to be played out normally, but any outcome for purposes of disengagement/destruction is voided and the banned time from the previous mission and hex doesnt begin until the current mission concludes.
- Black Hole hexes are free hexes and the Disengagement/Destruction doesn't apply to these hexes.
- One turn is 4 minutes.

That is the current rule. What if we changed it so that the player that lost points in that hex (got a ship destroyed that was worth points) can come back into it if they fly a smaller class ship than the one they lost and are drafted by an ally? Just throwing this out.

[FPF-Tobin Dax]

No to banning in adjacent hexes please. With frequent low numbers this can be too big a penalty to a side. Smaller class sounds interesting, but policing might be an issue and if you lose a frigate do you have to fly a freighter?

[Dizzy]

Well, yeah, the area ban rule might not be a good idea for this map. It is a tad smaller.

[deadmansix]

Want some feedback if DH and I rewrite this rule.

Disengagement/Destruction Rule

- If you are forced to Disengage in a PvP match, then you are banned from the hex you either took the mission in or were drafted in and all the hexes adjacent to that one for 15 turns. If your ship was destroyed then you are banned from that hex and all adjacent hexes for 8 turns.
- If you draft or are drafted while moving out of an area you have been banned in, the mission is to be played out normally, but any outcome for purposes of disengagement/destruction is voided and the banned time from the previous mission and hex doesnt begin until the current mission concludes.
- Black Hole hexes are free hexes and the Disengagement/Destruction doesn't apply to these hexes.
- One turn is 4 minutes.

That is the current rule. What if we changed it so that the player that lost points in that hex (got a ship destroyed that was worth points) can come back into it if they fly a smaller class ship than the one they lost and are drafted by an ally? Just throwing this out.

 no ban rule for this one and frigate is the smallest you can go (no jumping into a drone frigate or the like)

[Dizzy]

will will have a disengagement rule of some sort until  the day where battles on the sql server can correctly adjust the DV values in multiples for pvp engagements. Too easy for a single frigate to engage 3 players sitting rock so a couple frigate hex munchers can run missions under them and then rinse and repeat. That's not my idea of a fun server and unfortunately without this rule, we do have a bunch of unscrupulous players who'd horribly abuse it.

[Leto Atreides]

the sleeper has awakened!  i got the dyna to work!  my friend Jason works for Quantum something or other and he got my firewall problem to go away lol.  i was set to dmz and it still didn't work.  he opened the ports w/out going to dmz and tada!  he's worth every penny they pay him and more.  200K i'm in the wrong business lmao oh well... IT is the way to go i guess.  I look forward to this server.  2 days playing single player campaign and I'm killing AI like crazy as Lyran again.  I"M BACK!!!!  i remember how to do t-bombs again finally. 


I've missed you guys and gals more emphasis on gals hehe

I look forward to playing again...  "Let the hunt begin!"

[deadmansix]

will will have a disengagement rule of some sort until  the day where battles on the sql server can correctly adjust the DV values in multiples for pvp engagements. Too easy for a single frigate to engage 3 players sitting rock so a couple frigate hex munchers can run missions under them and then rinse and repeat. That's not my idea of a fun server and unfortunately without this rule, we do have a bunch of unscrupulous players who'd horribly abuse it.

sorry was speeking of the ban rule got confused you know us old guys it to us easly

[Dfly]

Want some feedback if DH and I rewrite this rule.

Disengagement/Destruction Rule

- If you are forced to yada yada yada.

That is the current rule. What if we changed it so that the player that lost points in that hex (got a ship destroyed that was worth points) can come back into it if they fly a smaller class ship than the one they lost and are drafted by an ally? Just throwing this out.

Some worried about having to come back in as a freighter.  Would not happen had you read it right .  Check out the "(got a ship destroyed that was worth points)" IF they made sure all ships worth points were bigger than a frigate.  IE make the dronechuckers fit into the LIGHT CRUISER class, since there are some small ships worth points.        Just a suggestion.

[FA Frey XC]

What I have noticed is slow hex movement when the server updates the news for the shipyard.

Slow Hex movement after battle until the server updates.

slow hex movement if moving hexes quickly (like the server lags behind)

I'm starting to wonder if it is the server kit itself that is slowing the Vista players down and not the game since players on Vista can pay GSA no problem, but only have problems when connected to the server (not in battle). I think it is time to recheck the networking code in the server kit.. maybe too many process sent through too few ports, or maybe needing to set the Server Kit to Win 2K compatibility mode before launch. Many game companies had to "Patch" their servers to be Vista compliant (along with some client software as well, but OP is not showing signs of that need on the Client end).

I can't seem to find any problem on the Vista end other than connection with the server.. so if XP player and Vista Player can play TCP/IP, GSA with no issues, but logging on to a server causes movement and updating lag, then it may be the server kit itself.

The results are consistant on all servers.. Boneyard, the Total War server, and the Test Setver using OP Stock shiplist.

The problem does not seem to be client side, but server kit side.. the servers all have 1 thing in common.. Build 37 of the kit. Maybe I can talk Bonk into looking into the Server Kit Code and maybe make a friendlier build to work with both Vista and XP.. but that may take a while with his schedule.

I'll look in to it.

How can you say it's the serverkit when XP users, windows 2000 users, and win98 users have no issues with the campaign? That just doesn't make sense. Now, don't take these words as criticizing you, your effort is greatly appreciated, but throwing it back on the serverkit without any real EVIDENCE is kinda fruitless.

I keep telling you, it's a directplay issue with DirectX 10. Has ANYONE put a packet tracer on the interface in VISTA to see what, exactly, is happening?

I've heard it's the Vista networking interface, then it's the Vista this and that. The bottom line is that if you use VISTA, WITH DIRECT X 10, the game shows issues. If you use WINDOWS XP or ANY OTHER OS, it doesn't.

Has ANYONE contacted Microsoft on this?

[KBFLordKrueg]

Want some feedback if DH and I rewrite this rule.

Disengagement/Destruction Rule

- If you are forced to Disengage in a PvP match, then you are banned from the hex you either took the mission in or were drafted in and all the hexes adjacent to that one for 15 turns. If your ship was destroyed then you are banned from that hex and all adjacent hexes for 8 turns.
- If you draft or are drafted while moving out of an area you have been banned in, the mission is to be played out normally, but any outcome for purposes of disengagement/destruction is voided and the banned time from the previous mission and hex doesnt begin until the current mission concludes.
- Black Hole hexes are free hexes and the Disengagement/Destruction doesn't apply to these hexes.
- One turn is 4 minutes.

That is the current rule. What if we changed it so that the player that lost points in that hex (got a ship destroyed that was worth points) can come back into it if they fly a smaller class ship than the one they lost and are drafted by an ally? Just throwing this out.

IMOPO...The rule is fine, except for the part about the 7 hex ban.
I rather see it a single hex ban.
I possibly would be willing to go with an adjacent hex ban around planets and possibly bases since it could be said they are capable of controlling a fixed position with it's better abilities over starships.

[FA Frey XC]

Pesty should be making an announcement soon in regards to our need for some help in testing the VISTA issue with online campaigns.

We'll derail that particular conversation to that thread, so please continue to post here in regards to the original intent of the poster.

Regards,

[Dizzy]

What box did AOTK3 run on? Those gf files are the ones we need to setup this server. I believe the racial alliance settings will change... and maybe a very few other things. Who has them?

[Braxton_RIP]

Probably Thor... I'll have a look here in a couple of minutes.

[Mithras]

Greetings All-

I am extremely interested to to get involved with SFCOP gaming community, am a long-time Mirak (Kzinti back in the SFB board game days). I am asking for someone to point me in the direction of any Mirak group. As an aside, I am also prepping for GenghisCon here in Denver next month. Thanks loads for any response.

[FCM_SFHQ_XC]

Alliance contains the Mirak race for this server

[KBFLordKrueg]

Greetings All-

I am extremely interested to to get involved with SFCOP gaming community, am a long-time Mirak (Kzinti back in the SFB board game days). I am asking for someone to point me in the direction of any Mirak group. As an aside, I am also prepping for GenghisCon here in Denver next month. Thanks loads for any response.

You should go here:
http://www.sfc2.net/forums/
Register there, if you havn't already, and then request access to the SGOA forums (under "usergroups" ) to be in contact with your team and get voice comm info and operations during the campaign. 

[marstone]

You should go here:
http://www.sfc2.net/forums/
Register there, if you havn't already, and then request access to the SGOA forums (under "usergroups" ) to be in contact with your team and get voice comm info and operations during the campaign. 

Good place to go, but remember to log in often anough, seems if you are off for about a month your account goes inactive (had my machine down recently, account went inactive etc).  But it is the main area for talking of fleet action so I would suggest it also.

[stoneyface]

sees the available races, yawns and crawls back under a rock...

no isc and no romulan = no stoneyface i guess..

[Dizzy]

Ok, OCI config is complete for testing. This is how the testing version of the OCI is being implemented. DH and I reserve the right to alter it in any fashion before the server starts.

Here are some of the goodies you will currently be able to do with the OCI:

- Admins can do about anything... 
- Change races. You can change from either of your two allied races whenever you are at an allied base or planet.
- Online shipyards. Bats, SB's and everything from FF to DN will be able to be purchased. (BS are restricted)
- Warpoints. You may change your location on the map from one allied starbase or planet to another allied starbase or planet.
- RM's may assign any allied ships including BB's which are currently restricted to any allied player.
- Players may transfer pp to to other allied players. Minimum transfer is 6k, max is 25k and there is a one time transfer cost of 5k charged to the player doing the transfer.
- something else, I forget. I'll post it later.