|
Sarien | Tue 19-Mar-13 10:24 AM |
Member since 14th Feb 2009
740 posts
| |
|
#49160, "Request: Please make it so Tahren will not speak to you if you have _Ever_ grouped with a mage."
|
So,
This is currently (unfortunately) once again a topic elsewhere. It has long been made public knowledge that grouping with a mage, leading them off and bashing them down is a '####' way to get your 1st mage PK.
Specifically when pledging allegiance to a cabal that views 'Betrayal' as the most despicable thing you can do.
When I was playing Bofin I had some doucher would-be village app try this with me. He didn't succeed, but still it soured me on him, and I almost posted the 'assassination' style log.
so: I would like to propose that Tahren be adjusted so that anyone who has 'grouped' with a mage needs to go through more 'hoops' to even become an applicant.
my .02$
|
|
|
|
Too ripe for abuse/misunderstanding.,
Homard,
19-Mar-13 12:06 PM, #1
RE: Too ripe for abuse/misunderstanding.,
Sarien,
19-Mar-13 12:11 PM, #2
Yeah, it could happen. ,
Homard,
19-Mar-13 12:54 PM, #3
C'mon. It WILL NOT happen on a regular basis. Also it's...,
Shapa,
19-Mar-13 04:51 PM, #4
Attention is paid to leveling up with a mage already,
highbutterfly,
20-Mar-13 02:10 AM, #5
RE: Attention is paid to leveling up with a mage alread...,
Sarien,
20-Mar-13 08:01 AM, #7
Not easy to engineer it?,
Homard,
20-Mar-13 08:36 AM, #8
I don't think your scenario is very realistic.,
Vortex Magus,
20-Mar-13 07:40 AM, #6
A timer is a solution.,
Homard,
20-Mar-13 08:38 AM, #9
RE: Too ripe for abuse/misunderstanding.,
Daevryn,
21-Mar-13 12:09 AM, #10
RE: Too ripe for abuse/misunderstanding.,
Sarien,
21-Mar-13 10:14 AM, #11
| |
|
Homard | Tue 19-Mar-13 12:06 PM |
Member since 10th Apr 2010
959 posts
| |
|
#49165, "Too ripe for abuse/misunderstanding."
In response to Reply #0
|
I'm Pincersvirf. I'm going Battle.
Ranger asks me to group. Sure.
follow ranger he groups me gr
<15 Ran> Ranger 100% hp 80% mana 100% mv 6100 xp <15 War> Pincersvirf 100% hp 68% mana 100% mv 8900 xp <15 Shf> Mage 91% hp 89% mana 100% mv 9812 xp
Whoops. Now I need an IMM induct.
|
|
|
|
  |
Sarien | Tue 19-Mar-13 12:11 PM |
Member since 14th Feb 2009
740 posts
| |
|
#49166, "RE: Too ripe for abuse/misunderstanding."
In response to Reply #1
|
While I suppose your scenario 'could' happen. The amount of times it has happened to me is 0, as generally when it comes to grouping any rager on the 'up and up' is pretty up front about disliking magi.
Generally you know who your 'third' is prior to them being your third.
I don't know what the right answer is.
I do know that every low level mage wants to rank
I do know that total piece of garbage douchebags take advantage of this by being all 'lets group! bash bash bash trip trip'
I do know 100% that left to my own devices I'd love to simply have people post logs of assclowns doing this in some format (Maybe they could make a way of reporting using logs or something).
|
|
|
|
    |
Homard | Tue 19-Mar-13 12:54 PM |
Member since 10th Apr 2010
959 posts
| |
|
#49168, "Yeah, it could happen. "
In response to Reply #2
|
But if grouping with a Mage meant Imm induct only, it would be engineered to happen on a regular basis.
I'm not really sure what the solution is, either.
|
|
|
|
      |
Shapa | Tue 19-Mar-13 04:51 PM |
Member since 22nd Jun 2006
252 posts
| |
|
#49174, "C'mon. It WILL NOT happen on a regular basis. Also it's..."
In response to Reply #3
|
Also you can place a timer ... like 1 minute. It will be enough to type group and see a mage. Even if you can't see a mage on where, look and you have a melee class who seriously needs to betray you.
But the rp path "to use the magic/healing/healers and to group with mages to level up only to betray them lately to get that 1 mage pkill as future battlerager" is used by the people who know much more than me (for example) about the village of battleragers too often for the game where 95% of the playerbase aren't total newbies.
Whom are we really lying to?
|
|
|
|
        |
highbutterfly | Wed 20-Mar-13 02:10 AM |
Member since 24th Aug 2011
364 posts
| |
|
#49183, "Attention is paid to leveling up with a mage already"
In response to Reply #4
|
|
|
          |
Sarien | Wed 20-Mar-13 08:01 AM |
Member since 14th Feb 2009
740 posts
| |
|
#49185, "RE: Attention is paid to leveling up with a mage alread..."
In response to Reply #5
|
Right,
I know they log who is in the group whenever a char gains a level. I do not believe they log all group activity period - I could be wrong, but I doubt it.
My solution would catch those who grouped a mage with the direct intention of killing him, but did not rank with such said mage.
|
|
|
|
        |
Homard | Wed 20-Mar-13 08:36 AM |
Member since 10th Apr 2010
959 posts
| |
|
#49189, "Not easy to engineer it?"
In response to Reply #4
|
All you have to do is group with some invoker who is busy spamming in his guild, then ask any level 11 Svirf warrior if they want to learn.
When they follow you, group them and now they need IMM induct.
Are you really telling me that the people who play this game are not so petty as to engage in that sort of behavior?
Really?
Have you met the people who play this game?
|
|
|
|
      |
Vortex Magus | Wed 20-Mar-13 07:40 AM |
Member since 20th Apr 2005
400 posts
| |
|
#49184, "I don't think your scenario is very realistic."
In response to Reply #3
|
And even if it did happen, I think it would be easily resolved if you just implemented the shaapa suggestion and gave someone 2-3 ticks to leave the group, if he joined one with a mage in it unintentionally.
|
|
|
|
        |
Homard | Wed 20-Mar-13 08:38 AM |
Member since 10th Apr 2010
959 posts
| |
|
#49190, "A timer is a solution."
In response to Reply #6
|
But if you guys don't think that people would roll attractive low-level ranking partners just to inconvenience would-be Battle Apps, I think you have too high an opinion of humanity.
|
|
|
|
      |
Sarien | Thu 21-Mar-13 10:14 AM |
Member since 14th Feb 2009
740 posts
| |
|
#49212, "RE: Too ripe for abuse/misunderstanding."
In response to Reply #10
|
Yea,
My post was in response to what I perceived as an 'increase' in this behavior, and likely a decrease in time that IMM's can police it.
As I said, I didn't know if there was any kind of codeable answer to the dillema, and I completely understand that it would be difficult/impossible to implement.
All in all, if my post has just brought more attention to this behavior, I believe it has served its purpose.
|
|
|
|
|