Distension discussion

[2kill]

I seem to have posted about the disconnecting issue at the same time as you. I am glad there is a setting for it since it will save some time.

You have to remember that the queue !claim time can't be too long or other people will have to wait too much for their turn in the queue. Besides, I don't know any event that I wouldn't leave right away if I got to !claim a spot. Only exception would be a league match of some kind.

I understand you not wanting people to wait to long as this would cause undue wait for the other people... but we are trying to get the rest of TW (non-distension players) to think that distension will not kill the rest of the zone. if you're just a player in an event then you can leave... but what about if you are the starting zombie? captaining in ?go base? in a twd match... it would mean that you would lose your spot and would have to start over.

ways to fix this would be

• increase the !claim time (which is what I said)

• have a way to get in the queue from a different arena (would allow a person in a basing match when he misses his spot to restart his countdown so when he is done he wouldn't have to wait as long)

• after a person does !claim his total time played increases 1 minute for every 3 minutes he is not there (ratio doesn't matter to me) it should be more then a 1 to 1 ratio cause that would be kind of telling people to rush or leave the basing match (or whatever) cause you are watching your time go out the window

anyway cya in supspace
2kill

[Viruk]

By the way, from people that played far into beta, does anyone know how much damage an L3 bullet does, or if a terrier can tank one at some point?

I mean, I'm just about rank 50, and they still one-shot me, which is extremely aggravating, because when you're in a flagroom fight with 30 other people, half the time you won't even see bullets at all and you just blow up. It just seems a bit extreme, as warbirds get them early enough that that at the time they unlock them, they will one-shot anything that's supposed to be a tank type ship, including a shark or levi warship or whatever, not to mention go straight through repels, as was discussed earlier in the thread.

Does anyone else think they're a teensy bit overpowered?

I am pretty sure terriers can tank L3s eventually. Levi warships will first though.
The claim that warbird bullets go straight through repels did not withstand scrutiny in that discussion.

Top terrier level is 52. Top warbird level is 37 - which is below all the top 5 terriers. A lanc has already caught up with the warbirds.

Clearly it is the terriers that are a bit overpowered - but then as the prime targets perhaps they need to be.

Warbirds seem somewhat underpowered so far so I wish them joy of their L3s.

I think warbirds ought to be able to one-shot kill for much of their lifespan just as they do in pub. The Distension settings have been giving terriers a break up until now. It is good that terrier life is going to get tougher for a bit.

[Mjollnir]

lol I suggest not !sc # as thats the short form for !scrap but no ship changes before dc is controled as project said from the settings in the Security section under MaxShipTypeSwitchCount (the default is 10) in the CFG files.

about the chaos queue that sounds good with me though it will need to be longer incase the person is in a event or doing something else. the !claim could be 30 secs and like 5 minutes or more before you lose the spot

2kill

I seem to have posted about the disconnecting issue at the same time as you. I am glad there is a setting for it since it will save some time.

You have to remember that the queue !claim time can't be too long or other people will have to wait too much for their turn in the queue. Besides, I don't know any event that I wouldn't leave right away if I got to !claim a spot. Only exception would be a league match of some kind.

[Mjollnir]

RE: Preventing ship change disconnections:

I believe that you can do this via arena settings, not by bot (at least the d/c for too many shipchanges thing).

I hope that is possible. If it isn't, here is a bot command example to make my suggestion clear: Player types '!sc 8' to switch to a Shark. If there are too many Sharks, the player gets the error message and never gets switched at all. That way the ship change disconnections will almost never happen, since you never get switched unless it is possible within the given ship limits. It is also quite typical for players to try to enter the queue multiple times, which means that every time you enter you get specced again. When the player finally gets in he might have so many "ship changes" that he gets disconnected right away.

Edit: The command name doesn't have to be !sc. That command name comes from Chaos / League SVS zone as well.

[2kill]

On an unrelated note: I would love a bot command for changing ships to prevent getting disconnected for too many ship changes. This happens when trying, but failing to switch to a Terr or a Shark repeatedly, and when trying to enter the queue from spec. The command would work by checking if you can switch to the specified ship, and only allowing it if possible. This way your ship doesn't change unnecessarily and cause a disconnection. The command could be !sc #, where # is the ship number from 1 to 9. The same command should work when trying to enter the queue.

Second unrelated note: The queuing has been done pretty well in Chaos/League SVS zone. The bot private messages you when it's your turn to play and you have to respond with !claim within 10 seconds. If you fail to respond you lose your spot and if you respond in time you have 30 seconds to enter the arena (before losing your spot). Distension queue could easily work in a similar fashion.

lol I suggest not !sc # as thats the short form for !scrap but no ship changes before dc is controled as project said from the settings in the Security section under MaxShipTypeSwitchCount (the default is 10) in the CFG files.

about the chaos queue that sounds good with me though it will need to be longer incase the person is in a event or doing something else. the !claim could be 30 secs and like 5 minutes or more before you lose the spot

2kill

[Stabwound]

No
if anything is overpowered atm it is the weasel.

Well, no offense, but the WB is your main ship, and you use L3 bullets, so this is a pretty biased response.

[TagMor]

No
if anything is overpowered atm it is the weasel.

And Another Thing:
the bonus for standard TeKs is a little strange..
First, I think it should be raised to atleast 50%.. terr is nearly always surrounded by its teammates and has good tanking abilities. Plus, there is usually only 2-3 per team.
Also, as I understand it, if you kill a terr in fr who's team holds flag, then you get 50% bonus.. but if you kill a terr in fr and it's team doesnt hold flag, you get the standard 10%... I dont think this is quite fair, as said, terr is extremely hard to kill and taking one out in fr (with or without flag) deserves a much greater prize than 10%rp bonus.

May I suggest 3 bonus levels:

FR Terr w/flag Kill (200% bonus)
FR Terr Kill (100% bonus)
Standard Terr Kill (50% bonus)


I feel something like this would better reflect the hardwork involved in TeKs. Aswell as promoting the team aspects, as killing the terr is fundamental to winning and often involves the sacrifice of many deaths.

[Stabwound]

By the way, from people that played far into beta, does anyone know how much damage an L3 bullet does, or if a terrier can tank one at some point?

I mean, I'm just about rank 50, and they still one-shot me, which is extremely aggravating, because when you're in a flagroom fight with 30 other people, half the time you won't even see bullets at all and you just blow up. It just seems a bit extreme, as warbirds get them early enough that that at the time they unlock them, they will one-shot anything that's supposed to be a tank type ship, including a shark or levi warship or whatever, not to mention go straight through repels, as was discussed earlier in the thread.

Does anyone else think they're a teensy bit overpowered?

[Stabwound]

You can't fault a child for being childish.

[Liquid Blue]

or you could not constantly rise to childish bait and focus on producing positive posts

[roxxkatt]

ill just leave this here...

Cheese!> POLL RESULTS: DISTENSION 45 - NEWBS 7

[Dwopple]

distension should be an event. something like ?go warzone...everytime you come back when its hosted all your shit will be there. instead of a regular thing.


or just get rid of it all together

[project dragon]

On an unrelated note: I would love a bot command for changing ships to prevent getting disconnected for too many ship changes. This happens when trying, but failing to switch to a Terr or a Shark repeatedly, and when trying to enter the queue from spec. The command would work by checking if you can switch to the specified ship, and only allowing it if possible. This way your ship doesn't change unnecessarily and cause a disconnection. The command could be !sc #, where # is the ship number from 1 to 9. The same command should work when trying to enter the queue.

I believe that you can do this via arena settings, not by bot (at least the d/c for too many shipchanges thing).

[Mjollnir]

Btw, I think there's something wrong with the part of the code that adds people into the queue. From what I can tell from the code (although I could be reading it wrong) when a player tries to enter the game but it is full, it attempts to queue them. If they have played the most out of any player that day, it's supposed to deny them a slot with the message:

"Sorry, no play slots are available, and you've flown more today than any other pilot here. Please try again later."

But it's actually denying many people with varying play times. Right now there are 3-4 people that are getting that message; they can't even get in queue for literally hours (I was in spec for 2 hours and always got that message when trying to enter, and I am positive I had not played the most out of everyone in the arena). My guess would be that it's not setting the "highestTime" variable correctly, or needs to set it a different way, but I didn't really look at it that closely.

It sure does seem to work in a weird fashion. What is the original reason for not letting the player that has played the most in the queue?

On an unrelated note: I would love a bot command for changing ships to prevent getting disconnected for too many ship changes. This happens when trying, but failing to switch to a Terr or a Shark repeatedly, and when trying to enter the queue from spec. The command would work by checking if you can switch to the specified ship, and only allowing it if possible. This way your ship doesn't change unnecessarily and cause a disconnection. The command could be !sc #, where # is the ship number from 1 to 9. The same command should work when trying to enter the queue.

Second unrelated note: The queuing has been done pretty well in Chaos/League SVS zone. The bot private messages you when it's your turn to play and you have to respond with !claim within 10 seconds. If you fail to respond you lose your spot and if you respond in time you have 30 seconds to enter the arena (before losing your spot). Distension queue could easily work in a similar fashion.

[Stabwound]

Btw, I think there's something wrong with the part of the code that adds people into the queue. From what I can tell from the code (although I could be reading it wrong) when a player tries to enter the game but it is full, it attempts to queue them. If they have played the most out of any player that day, it's supposed to deny them a slot with the message:

"Sorry, no play slots are available, and you've flown more today than any other pilot here. Please try again later."

But it's actually denying many people with varying play times. Right now there are 3-4 people that are getting that message; they can't even get in queue for literally hours (I was in spec for 2 hours and always got that message when trying to enter, and I am positive I had not played the most out of everyone in the arena). My guess would be that it's not setting the "highestTime" variable correctly, or needs to set it a different way, but I didn't really look at it that closely.