Other > Suggestions

PvP and others

<< < (8/14) > >>

DocAN.:
Nothing, just You wont jump from WM on POLICE when Runner will die.

Simon:
Yes Balthasar, the team with most skill (teamwork, organization, coordination, execution, strategy) should win a fight not the team that has the most alts. As was previously mentioned in this thread, if there is a relog timer which only activates when your character dies then it will not be a problem to instantly switch through your crafters, taxis and what not so long as you don't die.

If you want endless waves of pvp fun you can go to a special place called hinkley where both teams have equal amount of alts or waves each round and you can play as much as you like there, it even saves you leveling up new characters and getting gear for them.

Original TC system was designed so that team A starts timer then another team comes along and kills enough of Team As players so that the timer will stop, simple as that.


--- Quote from: DocAN. on August 28, 2012, 07:39:17 pm ---Removing FR will bring sandboxie, and its even worst then FR.
--- End quote ---
I don't think you understand how to use sandboxie/fastrelog or how multilog detection worked last session. Maybe you didn't realise that no one was using waves of alts last session probably because you were "awaiting wipe". Just add trigger timer on death and problem is solved.

Honestly if there is a relog timer it just means there will be a 5 minute or so break between actions where teams can replan and it will make for a more fun and diverse pvp experience as compared to hinkley wave of alts.

It's understandable though that many of you have put in months to level up your many alts and get extra gear for them to this stage where you don't want all your work to become useless.

Kilgore:

--- Quote from: Simon on August 29, 2012, 04:22:43 am ---I don't think you understand how to use sandboxie/fastrelog or how multilog detection worked last session. Maybe you didn't realise that no one was using waves of alts last session probably because you were "awaiting wipe". Just add trigger timer on death and problem is solved.
--- End quote ---
Are you even serious? I think you have completely no idea about what was happening in pvp in previous session and 2 sessions ago. Maybe you were too busy roleplaying pvp fighter in NCR.
Yes, waves of alts happened.
Yes, multilog was used heavily.
Yes, fast relog is ALWAYS possible, especially if you have dynamic IP.
Yes, there is no GM who would look for players breaking rules right now.


--- Quote ---It's understandable though that many of you have put in months to level up your many alts and get extra gear for them to this stage where you don't want all your work to become useless.

--- End quote ---
I've heard the same bullshit 3 years ago ("you win because of fast relog"). Then, they added relog cooldown and guess what. Didn't help much, because fast relog is not "I win" button.
I wouldn't whine even a bit if they add relog timer again. I will just laugh in your faces because you will still come to forums and whine the same way you do now, because "enemy cheating" :> Just look now at some teams who whine about other teams winning by fast relog while I'm showing them screenshots with their entire teams dead and EVERY player in (off) state. Stop being fucking hypocrites.

Paladin:
Its not about hypocricy its about what other gangs do. If you know that your enemy has always 5+ alts you need to have at least same number to fight them because if you dont adapt you dont have chance thats it. I dont remember problem with fastrelog last session maybe you do because you were always in jail.

Kelin:
Actually I remember many players with dual logs (proxy) and fastrelogs, yes it was harder than now but still doable. My friend had dynamic IP so before each fast relogging he just switched his IP and he never had any problems with GMs. Your argumentation might be that it was only few players doing such thing, that's true and also the truth is that they had a huge advantage over other "non-cheating" players.

Navigation

[0] Message Index

[#] Next page

[*] Previous page