Jav TKers getting out of hand, got zero help from staff over an eight hour period.

[kthx]

You weren't around to be a part of the leviterring culture, but many of us were. There were pub squads that only levterred, people that new every shot and spent hours making new ones. It's stupid to throw away all of that.

Sigh, you guys act like this is something that is so complicated to do.

Robobots have a module called "tkwatcher" that specs people for X amount of minutes after X amount of tk's, and reduce javelins bomb explosion radius to a bit lower so that tk's generally happen more on purpose than on accident. I mean its better than taking out the entire fucking ship like you did to levi. Why not just replace it with the nightwasp or something btw like i said in the my other thread, or bring levi's back and add walls around the FR, and give every ship antiwarp, every spawn, and then LT's have to come into the base where everyone has antiwarp and manage to escape to get that bounty. You don't need to code 10000 fucking modules just do with what you already have and use a little bit of creativity.

I actually kinda agree with this guy on this.
Instead of the module specing the player, it could set him to only non-tking ships, for a time limit ofc. Intentional or not, numerous tks should have consequences.

I also agree with his idea about lifting the limit of people in pub. Many people log on and then log off because they are stuck in an almost empty secondary pub.

I don't however agree with the idea about antiwarp/wall around flag room. Just replace the Levi with a more appropriate ship would be fine.


Or, since levi is rendered useless in Pub, you could replace it with a ship designed to facilitate people who refuse to stop TKing. It could be a god awful ugly ship that is not very effective, and truly embarrassing to have to play. I know that if my punishment for TKing was loss of style, I wouldn't TK

[kthx]

And just add a bouncer module that moves people from pub 1 to pub 0 if you can't remove the actual arena in the settings.

[Jason]

no, i know it's easy to do. i already said as much. it's just the usual red tape to get through. you know how that goes, wark.

but i'm going to push for this because it makes everyone's lives (players and staff) easier. it's a no-brainer, of course. just give me some time to talk to some folks when i get home from work tonight and sign into the game.

edit: referring to the tk'ing thing. you snuck that other post in on me. as far as big changes to pub, that's a mountain i'm not willing to climb at the moment. gonna take a whooooole lot of nagging, hah.

[kthx]

Oh and can't you fucking see that the zone is not full of players, when pub 0 has 35 people in it there are 9 people in the second pub, which is where anyone "new" who enters the game (you know the ones you are so worried about) logs in to see 5 people flying around and 4 people in spec afk and quits instantly. How about you just add a bigger base, and remove the population limit on pub 0 already, so that instead of the 35 people with 10 afks sitting in pub 0 and 9 players with 4 afks sitting in pub 1 you have 44 people in pub 0 killing each other and when newbies enter they actually see something happening.

[kthx]

Sigh, you guys act like this is something that is so complicated to do.

Robobots have a module called "tkwatcher" that specs people for X amount of minutes after X amount of tk's, and reduce javelins bomb explosion radius to a bit lower so that tk's generally happen more on purpose than on accident. I mean its better than taking out the entire fucking ship like you did to levi. Why not just replace it with the nightwasp or something btw like i said in the my other thread, or bring levi's back and add walls around the FR, and give every ship antiwarp, every spawn, and then LT's have to come into the base where everyone has antiwarp and manage to escape to get that bounty. You don't need to code 10000 fucking modules just do with what you already have and use a little bit of creativity.

[blackrazor]

Today's Jav tkers (many tks to whole team, on purpose) were memorex and BAMBOOZLED.

Connection, to his great credit, responded fast, very fast. Neverthless, both Javs logged out as soon as they saw they were being watched. Apparently this is a growing problem, as "pro griefers" become wise to the system.

This hopefully lends support to fixing this with pubbot tweaks, as I suggested in the first post. That also would free up more staff to do more important things than watch TKers who are just going to log out the instant they suspect they are being watched. It also avoids the whole drama of Javs claiming they were just "practicing a new shot" and "it was an accident, I swear". Who needs that grief? I'll bet staff doesn't. Just tweak pubbot, and let the ship restrictions for Jav and Shark be automated in one way or another.

Also, I disconnected due to too many deaths again as shark today. Flagroom was full of javs, bombs and shrap everywhere. Please, another nice thing to fix is the amount of deaths needed to disconnect in pub. I've bought this up before too, I know.

[kthx]

Cheese hates women, exercise, anyone who doesn't like distension, sunlight, and tits.

[Jason]

why would i need to feel any remorse?

in the original thread about the pub money system i made this post: http://forums.trenchwars.org/showthr...l=1#post768075

and in your follow-up thread to the original i made this post: http://forums.trenchwars.org/showthr...l=1#post768817

in the former i am hardly condemning of dexter, and in the latter i actually defended him amongst all the shit you kept spewing after letting kthx get to you. now i did go on to bash you in that follow-up thread, but you were acting like a douche. you deserved it.

i know you like to hate, but at least direct your hate at the proper people, please.

[roxxkatt]

Lmaonaise (his name well chosen as a griefing account, a conjunction of LMAO and mayonaise)

why did noone lol at this

poor dex got bashed so hard for all that work

is that remorse i hear

[Jason]

no, the mistake was mine. i misunderstood you, and focused only on the part of your post about the voting system. i also forgot about the code that's already in place. poor dex got bashed so hard for all that work, and it was yanked so quickly that the whole thing seemingly never happened.

i'll push this idea up through the proper channels and see if we can't make this happen. i, for one, get tired of taking tk'er cheater calls. unless you're aliasing, the real tk'ers almost always get crafty and wait for you to leave before resuming their shenanigans.

[blackrazor]

Jason, the bot itself measures the numbers of TKs, so there is nothing (besides TKing or not TKing) that players can do to influence its data and decisions. The voting code was an arena-wide thing, so if players vote to restrict Jav, then everyone gets restricted until a re-vote is taken. The pubbot cash is a reward system designed by Dexter, basically if you are flagging or basing (even if losing, but at least trying), you earn more points, which you can then spend on a temporary access to shark or jav to help the team. As it is temporary, you must continue earning those points by basing, to keep being able to buy more of them when the first temp runs out.

In all these cases, there no portion of the code where players can influence the bot by PMing it. If I've misunderstood what you meant in your post, then please explain further, and I will try to, also.

[Jason]

while i agree with you blackrazor and would like to see a system whereby players can put an end to tk'ing on their own, such a system is a double edged sword. i guarantee you would see it abused. some chump would get his chump squadmates to wrongfully pm the bot and get an innocent player locked out of jav or shark.

i don't yet have an answer as to how to make such a system abuse-proof. i'm not sure there is an answer.

any thoughts?

[kthx]

Or just reduce jav prox in pub.

[blackrazor]

If you read my post, you will see that I fully expect and understand staff to not always be available. It's a volunteer position, and they have other things to do.

That is why I suggested we implement restrictions on access to shark and jav. Dexter perhaps can modify pubbot to track team-kills. If you get a certain amount or percentage of team-kills, then you cannot be in shark or jav. Previously there was a "restrict jav" (among other things) voting system, that works too. Or jav and shark can be bought, like lev, with flagging points in Dexter's new pubbot code. There are many options, including others I may have forgotten or not considered. Dexter is the expert on how is best to do it in pubbot, and I trust his judgement.

But no where in my text did I blame staff, I fully understand their position on this. I am looking for solutions, not problems.