Rant...

banananose · Post by **banananose** » Sun Jun 01, 2003 8:44 am

Ok, if you're going to macro while AFK, that's your business.

But if you're going to macro while AFK using an environmental combiner...

In a town where there's only one such combiner...

And there are people wanting to use said combiner for their newbie armor...

You're being rude and inconsiderate and begging to get petitioned and banned. I don't want this to happen to you, and I spoke with the players who were gonna petition you and told them you were probably asleep or something. You know who you are ... please think twice before you run a macro like that while you sleep at night ...

Stargazer · Post by **Stargazer** » Sun Jun 01, 2003 10:36 am

That's good advice for everyone I think.

The general rule of thumb for any macro that uses an environmental container is to have it automatically close the container if any comes near. You are just begging for trouble if you don't plus it is the courteous thing to do.

compuboy · Post by **compuboy** » Sun Jun 01, 2003 12:33 pm

yeah real easy, set a proximity event.. when someone gets close, stop, when they leave, star again.. not to hard, take ya five min to do

Jaerin · Post by **Jaerin** » Sun Jun 01, 2003 12:39 pm

I agree...any suggestions for the folks on how to detect a PC within a certain range?

Jaerin

vzmule · Post by **vzmule** » Sun Jun 01, 2003 1:20 pm

Never go too terribly afk while running that type of macro.

Amadeus · Post by **Amadeus** » Sun Jun 01, 2003 4:03 pm

I could probably write a $char(closest_spawn, xxxx) that would return some stats about the closests spawn ...including distance, type, etc... if you're interested.

Jaerin · Post by **Jaerin** » Sun Jun 01, 2003 5:23 pm

Actually that wouldn't necessarily be what would be needed. A PC within certain range would be better suited. Problem is currently /alert pc will trigger on yourself.

So even making /alert ignore themselves would work.

Jaerin

Amadeus · Post by **Amadeus** » Sun Jun 01, 2003 9:25 pm

PCs are spawns :) ...at least as far as the code is concerned.

if $char(closest_spawn, type) == PC ...for example

...one would also be able to tell it's class, race, whether NPC or PC, level, blah blah blah....heck, ther should be a way of figuring out if it's undead or not, then casting either invis to undead or invis.

Jaerin · Post by **Jaerin** » Sun Jun 01, 2003 10:05 pm

Yes but what I was saying in regards to this topic is that NPC's are also spawns and in the case of this topic the PC that want's to use said combiner may not be the closest spawn.

Ideally /alert should not fire on yourself. Which it does.

Jaerin

Amadeus · Post by **Amadeus** » Mon Jun 02, 2003 1:14 am

You've totally confused me now...you posted:

I agree...any suggestions for the folks on how to detect a PC within a certain range?

Then, I suggested that we could have a set of variables that deal with the nearest spawn to the character. I use 'spawn' simply because it would make it reusable in more situations other than just this one.

What I was offering was to make a set of variables that would allow you to do something like this (pseduo-code):

Code: Select all

if ($char(closest_spawn, type) == TYPE_PC ) {
    if ( $char(closest_spawn, distance) < 200 ) {
            PauseMacro = true; } }

It's crude ...but, based on what I've read here, isn't that what you want? Some sort of way of determining if something is close and how close it is?

dont_know_at_all · Post by **dont_know_at_all** » Mon Jun 02, 2003 2:54 am

Please don't do anything stupid:

http://games.slashdot.org/article.pl?si ... 06&tid=209

Amadeus · Post by **Amadeus** » Mon Jun 02, 2003 3:52 am

That there in that posting is exactly why I always argue for us to draw a line as to our own morals and ethics as to what is cheating and what is TOO much cheating.

For those that think that cheating is cheating, read that. There is definately a point at which a person can go too far.

Thank God we have a bit more restraint. EverQuest should read it and be thankful.

HOWEVER, that being said, ShadowBane coders should get their heads out of their asses and fix such things. There's no excuse for hackers to be able to do that kind of crap and instead of punishing those, they ought to send them money for motivating their asses enough to plug up such exploits. Seriously, sometimes I wonder what devs are thinking....that everyone is just going to play nice and not try to hack their games?

kagonis · Post by **kagonis** » Mon Jun 02, 2003 4:42 am

Security through obscurity. I think Microsoft invented it.

Chamber · Post by **Chamber** » Tue Jun 03, 2003 5:31 pm

Simple way to get rid of those macroing an enviromental container like that, is pull newbie guard X near the offender and root it. Then cast a heal on MacroBoy01. Zone out. The guard will aggro them and do one of two things, kill them if they are AFK or get thier attention long enough to let them know people are watching and are not happy.

Mckorr · Post by **Mckorr** » Tue Jun 03, 2003 9:26 pm

Nope. Training others on purpose is a bannable offense. And if I have all my macro output going to a telnet window or something, I can easily do a /report on you when I get back and get you booted.

Not that I'm morally opposed to such a tactic mind you, rude people should be wiped out in some such manner. But you risk your account doing it, however justified it might be.