Dynaverse.net
Taldrenites => Dynaverse II Experiences => Topic started by: FPF-DieHard on January 31, 2005, 11:20:51 pm
-
All other BTs were removed on purpose. ;D
I assume you though the R-BT was a base?
-
All the stuff we had restricted seems to be back in
-
All the stuff we had restricted seems to be back in
That is restricted in "stock" OP+
-
All the stuff we had restricted seems to be back in
I noticed tht too. Gorn freightors were in the shipyard tonight.
I'm guessing this is part of the unrestricting fix for the DB errors Bonk and Dizzy were talking about; we'll just have to live with crap in the yards until there is enough time to test which restrictions cause errors and which don't.
-S'Cipio
-
I'm guessing this is part of the unrestricting fix for the DB errors Bonk and Dizzy were talking about; we'll just have to live with crap in the yards until there is enough time to test which restrictions cause errors and which don't.
-S'Cipio
Yes, it is a constant test. One restricted ship the server needs to run a shipyard gives the DB errors. I'll be whittling the list down and all fixes will be done server side.
-
All the stuff we had restricted seems to be back in
I noticed tht too. Gorn freightors were in the shipyard tonight.
-S'Cipio
Well you gotta have something to fly once we are finished with you....... ;)
-
I'm guessing this is part of the unrestricting fix for the DB errors Bonk and Dizzy were talking about; we'll just have to live with crap in the yards until there is enough time to test which restrictions cause errors and which don't.
-S'Cipio
Yes, it is a constant test. One restricted ship the server needs to run a shipyard gives the DB errors. I'll be whittling the list down and all fixes will be done server side.
Delete it from the list
-
Yes and no, DH. They ALL need to be deleted, but in the interests of fixing your ftrlist mistake, the coalition bitching that their carriers couldnt fly the ftrs that were affected and making sure the DB worked error free, I did the best I could with the time I was given.
A little slack please. I have a heavy load. I'll take the tugs out and test the DB to see if its safe. Im sure it will be. Then I will change the server side list so you all can have nice pretty shinny shipyards. Rom shipyards have a bit of spam too. :(
Course, I could, but I wont, go down the list and 'R' out all the unwanted ships, but the server DB would start spewing out errors left and right and I dont want a GW type series server afflicted burp and crash server.
-
Yes and no, DH. They ALL need to be deleted, but in the interests of fixing your ftrlist mistake, the coalition bitching that their carriers couldnt fly the ftrs that were affected and making sure the DB worked error free, I did the best I could with the time I was given.
A little slack please. I have a heavy load. I'll take the tugs out and test the DB to see if its safe. Im sure it will be. Then I will change the server side list so you all can have nice pretty shinny shipyards. Rom shipyards have a bit of spam too. :(
Course, I could, but I wont, go down the list and 'R' out all the unwanted ships, but the server DB would start spewing out errors left and right and I dont want a GW type series server afflicted burp and crash server.
Un-restricting a 200 BPV tug with a BCH powercurve for one race is just plain wrong, period. No amount of player whining justified it.
The fight fix was unilateral, ever hear of the Mirak? Their fighters was as affected by the CORRECTION.
Anyway, back to the technical details. Does a "missing ship cause more harm, the same, or less than a Restricted ship from your tests?
Hmmm, do restricted ships cause the problem more than an empty ship?
-
Yes and no, DH. They ALL need to be deleted, but in the interests of fixing your ftrlist mistake, the coalition bitching that their carriers couldnt fly the ftrs that were affected and making sure the DB worked error free, I did the best I could with the time I was given.
A little slack please. I have a heavy load. I'll take the tugs out and test the DB to see if its safe. Im sure it will be. Then I will change the server side list so you all can have nice pretty shinny shipyards. Rom shipyards have a bit of spam too. :(
Course, I could, but I wont, go down the list and 'R' out all the unwanted ships, but the server DB would start spewing out errors left and right and I dont want a GW type series server afflicted burp and crash server.
Un-restricting a 200 BPV tug with a BCH powercurve for one race is just plain wrong, period. No amount of player whining justified it.
The fight fix was unilateral, ever hear of the Mirak? Their fighters was as affected by the CORRECTION.
Anyway, back to the technical details. Does a "missing ship cause more harm, the same, or less than a Restricted ship from your tests?
Hmmm, do restricted ships cause the problem more than an empty ship?
Well maybe he should have simply told folks that it was done for technical reasons and informed people that they were not to fly it. Seems like a reasonable way to handle it without people getting all bent out of shape over balance again.
-
Yes and no, DH. They ALL need to be deleted, but in the interests of fixing your ftrlist mistake, the coalition bitching that their carriers couldnt fly the ftrs that were affected and making sure the DB worked error free, I did the best I could with the time I was given.
A little slack please. I have a heavy load. I'll take the tugs out and test the DB to see if its safe. Im sure it will be. Then I will change the server side list so you all can have nice pretty shinny shipyards. Rom shipyards have a bit of spam too. :(
Course, I could, but I wont, go down the list and 'R' out all the unwanted ships, but the server DB would start spewing out errors left and right and I dont want a GW type series server afflicted burp and crash server.
Un-restricting a 200 BPV tug with a BCH powercurve for one race is just plain wrong, period. No amount of player whining justified it.
The fight fix was unilateral, ever hear of the Mirak? Their fighters was as affected by the CORRECTION.
Anyway, back to the technical details. Does a "missing ship cause more harm, the same, or less than a Restricted ship from your tests?
Hmmm, do restricted ships cause the problem more than an empty ship?
Well maybe he should have simply told folks that it was done for technical reasons and informed people that they were not to fly it. Seems like a reasonable way to handle it without people getting all bent out of shape over balance again.
What the big-boned Gorn said . . .
-
What? Peeps are flying tugs?
MID SERVER RULE CHANGE: No tugs allowed. :D
-
What? Peeps are flying tugs?
MID SERVER RULE CHANGE: No tugs allowed. :D
+ Karma for making me chuckle at work!!
-
What? Peeps are flying tugs?
MID SERVER RULE CHANGE: No tugs allowed. :D
:rofl: :notworthy:
-
Un-restricting a 200 BPV tug with a BCH powercurve for one race is just plain wrong, period. No amount of player whining justified it.
The fight fix was unilateral, ever hear of the Mirak? Their fighters was as affected by the CORRECTION.
Anyway, back to the technical details. Does a "missing ship cause more harm, the same, or less than a Restricted ship from your tests?
Hmmm, do restricted ships cause the problem more than an empty ship?
Patience sir, if the battle tug appreared in Rom yards than one will eventually appear in all of them. I do not believe that just the rom battle tug exclusively was unrestricted... (that I know of) anyway....
What I do know for sure, is that deleting needed ships has the same effect as restricting them. Until we modify the kit so the shipyards do exactly what admins want (we've yet to settle that) I suggest you put up with the odd undesired ship. Is it really that bad if the odd feighter or frigate slips into the yards? I really prefer stability as the better choice. We simply do not have precise control over the shipyards with this serverkit, if you try and force it something bad will happen, guranteed... I'm looking at resource use in the kit and identifying GenericFile settings before making the shipyard do exactly what various admins want... (perhaps listing all the ships in the gf files? adding another column to the shiplist?...)
We'll get there, just not today... until then, Dizzy will test until he finds the maximum number of undesired ships on this list that can be restricted out...
What? Peeps are flying tugs?
MID SERVER RULE CHANGE: No tugs allowed. :D
:rofl: Simple solution!
-
What? Peeps are flying tugs?
MID SERVER RULE CHANGE: No tugs allowed. :D
+ Karma for making me chuckle at work!!
You know, on that note... Some mid server rule changes are not bad.
Reminds me of one such instance over the F-CS+. Feds made 1 in F&E, yet slipped thru the list unrestricted. Meanwhile, on the other side of the fence, the Klinks were having to pay for D5D's that were made in numbers. It was bad. I made a mistake not allowing me to see the issue on both sides and conceded to the demands of one such person that let it be flown freely.
Back to the 'some mid server changes are not all that bad'... I shoulda restricted that CS+ on the spot. Although I did work out a fairly amicable solution to it with the Alliance.
But as Kroma sorta said in another post, some peeps dont see the big picture, instead they try to capitalize on petty things that can give their side some small advantage despite the possible community backlash over it. They put their own interests above the community.
That's a voice of reason for mid server rule changes directly related to the server issues and not R/P.
This has really piqued my interest. When, where and what happened on a past server that a mid server rule change put it in so many peeps minds that any such mid server rule change is BAD BAD BAD?
-
This has really piqued my interest. When, where and what happened on a past server that a mid server rule change put it in so many peeps minds that any such mid server rule change is BAD BAD BAD?
Dominion Wars 4 or 5- we (Romulans) were at the Federation's doorstep, and were about to wipe them off the map. We were then told that the admin had brought in a new rule which banned anyone running missions on the homeworld hex or the 6 surrounding it. Understandably, the Roms were furious, after coming so far and losing a lot of ships and prestige to get to that point, to be told that we werent allowed to conquer another race.
That one little mid-camp rules change completely derailed the whole thing. Roms logged off in protest, Feds (now they were invulnerable) wiped the floor with everyone, and a lot of people were pissed over it.
-
You know, on that note... Some mid server rule changes are not bad.
BLASPHEMY!!!
BURN HIM!!!
-
What? Peeps are flying tugs?
MID SERVER RULE CHANGE: No tugs allowed. :D
Figures. Finally put a ship in that I don't get my a$$ handed to me in in three minutes or less, and now I can't fly it. By the time this is done, I'll be riding a freaking bike in a space suit using a sling shot as a weapon.
;D
-
What? Peeps are flying tugs?
MID SERVER RULE CHANGE: No tugs allowed. :D
Figures. Finally put a ship in that I don't get my a$$ handed to me in in three minutes or less, and now I can't fly it. By the time this is done, I'll be riding a freaking bike in a space suit using a sling shot as a weapon.
;D
After the server is over Hook up with Madelf, he is the master who can turn you into a Monster pilot.
Or PM me if you don't mind learning from a Fed ;D
-
I am working on getting together with him and Ravok, so I can learn all the intricacies of fighting properly. Kougar can help too, as he is another one that consistently creams people. ;D And I will hook up with you too, DH. Thanks.
-
All you're really gonna learn from DH is how to stop listening to a really shrill voice
over teamspeak..