Deprecated: Function create_function() is deprecated in /var/www/html/jellyro.com/archive/forums/Sources/Load.php on line 178
Deprecated: Function create_function() is deprecated in /var/www/html/jellyro.com/archive/forums/Sources/Load.php on line 183
Deprecated: Function create_function() is deprecated in /var/www/html/jellyro.com/archive/forums/Sources/Load.php on line 184
Deprecated: Function create_function() is deprecated in /var/www/html/jellyro.com/archive/forums/Sources/Load.php on line 220
Deprecated: Function create_function() is deprecated in /var/www/html/jellyro.com/archive/forums/Sources/Load.php on line 223
Deprecated: Function create_function() is deprecated in /var/www/html/jellyro.com/archive/forums/Sources/Load.php on line 235
Deprecated: Function create_function() is deprecated in /var/www/html/jellyro.com/archive/forums/Sources/Load.php on line 250
Deprecated: Function create_function() is deprecated in /var/www/html/jellyro.com/archive/forums/Sources/Load.php on line 268 Print Page - KS Definitions - @commands
Old aRO Forums
The 'Other' Section => AnesisRO Archive => Archive => General Questions => Topic started by: Rabin_Uman on December 10, 2008, 11:52:54 am
Title: KS Definitions - @commands
Post by: Rabin_Uman on December 10, 2008, 11:52:54 am
I have been finding that many players don't know or don't understand the rules. One thing that appears to need clarification is wether a monster under an status (frozen, sleep, etc) belong to the player who inflicted the status or are "free for all" as many players insist they are.
a common occurrence is for players to get out of the way when they see u coming with a chain (mob) of monsters that you have collected with effort, only to "skim" the tail end once u are past.
Looting is a bit less of a problem, but i would like to suggest the implementation of "autolooting" as exists in other servers. Other @commands such as "warp" or "go" devalue some of the game items or characteristics, though sometimes after having to go through several dungeon levels just to get to an MVP I wish I could warp directly there.
Players and GM's comments and advise on this matter would be most welcome.
Title: Re: KS Definitions - @commands
Post by: No Fixed Path on December 10, 2008, 11:56:22 am
No no no :'(
Title: Re: KS Definitions - @commands
Post by: Fear07 on December 10, 2008, 12:00:26 pm
I have been finding that many players don't know or don't understand the rules. One thing that appears to need clarification is wether a monster under an status (frozen, sleep, etc) belong to the player who inflicted the status or are "free for all" as many players insist they are.
That would be a fairly circumstantial thing. For some examples:
If Player A has a mob of Monster X around him, all attacking him, and he has, say, a sasquatch-carded armor on, and one of those monsters gets frozen, that monster still would belong to him.
If Player B has a mob of Monster Y around him, all attacking him, and Player C comes along and puts one of those monsters to sleep, the monster would still belong to Player A. If Player C went to attack that monster, he could be reported for KSing (with proper screen shot evidence, of course).
If Monster Z was not attacking anybody, and Player D comes along and makes that monster frozen, I'm actually not 100% positive whether the monster would now belong to Player D or not. Maybe a GM will be able to clarify on that one. Anybody know if causing a status to a monster without damaging the monster will make it become aggressive towards you (once the status goes away)? If so, then most likely this example would have the monster now belonging to Player D. If not, then I have no idea.
Quote
a common occurrence is for players to get out of the way when they see u coming with a chain (mob) of monsters that you have collected with effort, only to "skim" the tail end once u are past.
If you are properly controlling your mob (using sanc or hammer fall, or other similar attacks), people shouldn't be capable of "skimming" bits off of the tail end of it. As long as the mob changes targets of its own "free will" (ie - another player didn't intentionally pull it away with an attack, but just happened to be too close), then no rule has been broken. If you're mobbing correctly, you shouldn't be losing bits of it just because a player is nearby. Properly controlled mobs would require another player to actually attack one of your monsters in some way in order to pull them away from you. You also always have the option of stopping and killing your mob before crossing the path of another player, so it's really your choice to risk losing bits of your mob when you cross paths with another player and just decide to keep on walking.
Quote
Looting is a bit less of a problem, but i would like to suggest the implementation of "autolooting" as exists in other servers. Other @commands such as "warp" or "go" devalue some of the game items or characteristics, though sometimes after having to go through several dungeon levels just to get to an MVP I wish I could warp directly there.
@commands are an eAthena thing. We can't do them on Aegis as far as I know. Also, see the above posts concerning this.
Title: Re: KS Definitions - @commands
Post by: Aozora on December 10, 2008, 01:56:54 pm
@autoloot is also in some low rate servers, its useful. But i dont like the @warp, @go
We already have @storage, so let's jsut go all the way. We can't make autoloot but might as well implement greed clip.
Title: Re: KS Definitions - @commands
Post by: Rabin_Uman on December 10, 2008, 08:34:56 pm
Thanks for the explanation on monster ownership Varis. I agree that losing monsters in a "chain" is bad handling, however I was talking about KS, and i mean players attacking the tail end of the chain once u are past. Of course, closing (killing) the mob before giving that opportunity to other players is a solution, but it is sad to have to modify or reduce the "chaining" because of ill behaved players. If u read my original posting carefully, you'll notice that I do not favor the @commands, there are cards that enable warping that do become meaningless where @warp is implemented. My only real regret is not being able to warp to dungeons directly. Again, having to go through the lower levels has certain advantages, at least for lower level players who have the opportunity to observe tactics and other things.
Title: Re: KS Definitions - @commands
Post by: shadowpheonix88 on December 10, 2008, 10:19:03 pm
what're you suggesting if you're not favoring the @commands?
other than that, the biggest problem with autoloot is an AFK homunculus alchemist... quite a bit of a problem, don't you think?
Title: Re: KS Definitions - @commands
Post by: Sacherz on December 10, 2008, 11:02:45 pm
i dont even think we run @commands to be honest
<cough cough>
Title: Re: KS Definitions - @commands
Post by: jcflyguy on December 10, 2008, 11:21:09 pm
I was almost 100% positive that frozen, stone cursed, or sleep'd monster didn't belong to the one who caused the status, since technically, the monster isn't attacking anyone, isn't trapped, and isn't following them. And usually since the status is caused by armor, they're not being attacked by the player.
Of course, what do I know, right?
Title: Re: KS Definitions - @commands
Post by: Varis on December 10, 2008, 11:58:21 pm
well if the status is caused by armor, that means the monster was attacking someone in order to get status'd. Wouldn't the monster remain belonging to that person? I don't see why ownership would suddenly stop just because you status'd the monster.
If I'm wrong, I apologize for the incorrect info, but it doesn't seem to make sense for it to work any other way.
Title: Re: KS Definitions - @commands
Post by: shadowpheonix88 on December 11, 2008, 12:33:20 am
doesn't a monster belong to someone if it's being attacked by, attacking, or following a player?
so no matter how the monster was status'd it can be considered as "being attacked by" the player and/or "trapped" by the player... trapped may not just refer to hunter traps... they may also refer to trapping such as IWing a monster in a closed area... *shrug* not sure
Title: Re: KS Definitions - @commands
Post by: Lord Cypher on December 11, 2008, 01:37:46 am
see thats just it we all need to stay a way from the @ comands its bad wnuff there makeing this server more like the high rate with out the high rate in sted of giveing the @ comands thay chuld make clips for the stuff we like to use and now worping in to eney map with an @ i been playing this server for over 3 years and it is steting to look like one i do not wont to play for all the changes made to can makeing it more like a high rate server i came to this game for its peace and quiet but will all this new sh-t added its geting bad one lag and bugs and whats with the pot thow on bios pets not worling and the xp in talk bar the new name look i need to stop i can go on all day woth all this new crap added to game
Title: Re: KS Definitions - @commands
Post by: femme fatale on December 11, 2008, 01:59:08 am
@autoloot is also in some low rate servers, its useful. But i dont like the @warp, @go
We already have @storage, so let's jsut go all the way. We can't make autoloot but might as well implement greed clip.
Seems like your the expert about those kind of stuff so why not make a greed clip yourself? or are you just jealous 'coz someone figured out how to make a kafra clip before you have? ::)
Title: Re: KS Definitions - @commands
Post by: DeePee on December 11, 2008, 02:20:20 am
...why would he want to make a clip like that by himself? o.O That doesn't make much sense. It's not all that hard making an item that enables Greed, seeing that about all SQI's give you new skills.
Title: Re: KS Definitions - @commands
Post by: Arkensark on December 11, 2008, 08:23:01 am
Autogreed for every class is not fair and will make everyone sooooooo lazy.
/nosupport
Title: Re: KS Definitions - @commands
Post by: DeePee on December 11, 2008, 08:49:54 am
well if the status is caused by armor, that means the monster was attacking someone in order to get status'd. Wouldn't the monster remain belonging to that person? I don't see why ownership would suddenly stop just because you status'd the monster.
If I'm wrong, I apologize for the incorrect info, but it doesn't seem to make sense for it to work any other way.
When a monster is status'd, it loses all aggressiveness. If it's a normally passive monster, it'll go back to being passive. If it's normally aggressive, it'll attack whoever it sees first. If it attacks the new guy, then it's the new guy's monster. If the new guy attacks it first, then it's the new guy's monster.
Of course, any decent player should never let that happen. Unless they like... freeze it and sit down for SP or something :/
Title: Re: KS Definitions - @commands
Post by: Varis on December 11, 2008, 07:26:22 pm
well if the status is caused by armor, that means the monster was attacking someone in order to get status'd. Wouldn't the monster remain belonging to that person? I don't see why ownership would suddenly stop just because you status'd the monster.
If I'm wrong, I apologize for the incorrect info, but it doesn't seem to make sense for it to work any other way.
When a monster is status'd, it loses all aggressiveness. If it's a normally passive monster, it'll go back to being passive. If it's normally aggressive, it'll attack whoever it sees first. If it attacks the new guy, then it's the new guy's monster. If the new guy attacks it first, then it's the new guy's monster.
Of course, any decent player should never let that happen. Unless they like... freeze it and sit down for SP or something :/
Interesting. Learn something new every day, then. /ok
Title: Re: KS Definitions - @commands
Post by: Guardian Lord on December 11, 2008, 07:28:14 pm
well if the status is caused by armor, that means the monster was attacking someone in order to get status'd. Wouldn't the monster remain belonging to that person? I don't see why ownership would suddenly stop just because you status'd the monster.
If I'm wrong, I apologize for the incorrect info, but it doesn't seem to make sense for it to work any other way.
When a monster is status'd, it loses all aggressiveness. If it's a normally passive monster, it'll go back to being passive. If it's normally aggressive, it'll attack whoever it sees first. If it attacks the new guy, then it's the new guy's monster. If the new guy attacks it first, then it's the new guy's monster.
Of course, any decent player should never let that happen. Unless they like... freeze it and sit down for SP or something :/
Interesting. Learn something new every day, then. /ok
OFF TOPIC: who is the girl?????
Title: Re: KS Definitions - @commands
Post by: Varis on December 11, 2008, 07:34:51 pm
Hwang Mi Hee
Title: Re: KS Definitions - @commands
Post by: Benitoh09 on December 11, 2008, 08:36:47 pm
Looting is a bit less of a problem, but i would like to suggest the implementation of "autolooting" as exists in other servers. Other @commands such as "warp" or "go" devalue some of the game items or characteristics, though sometimes after having to go through several dungeon levels just to get to an MVP I wish I could warp directly there.