Is it legal to use a script that makes a macro? - Page 3

Vosloo · 07-26-2009, 11:53 PM

lairs........

Brondon · 07-27-2009, 12:07 AM

Quote:

Originally Posted by Vosloo

lairs........

almost to 100 post count yay! keep going! stupid retard, rofl.

Pink Poodle · 07-27-2009, 01:24 AM

Quote:

Originally Posted by Vosloo

lairs........

EQ2 has plenty of them

Prugor · 07-27-2009, 02:12 AM

Quote:

Originally Posted by Brondon

almost to 100 post count yay! keep going! stupid retard, rofl.

Stop buffing your post count by replying to him. Learn the way of the light grasshopper. Maybe it will go away. Tuor lurks now and doesn't post alot.

dragowulf · 07-27-2009, 05:42 AM

Pretty much SoE's stand on macroing is simply NO unattended gameplay or distribution of these programs/scripts.

Due to avoiding potential lawsuits, SoE has not dissaproved of attended macroing otherwise they'd be subject to discrimination towards persons with disabilities. Issues have come up in the past where people using macroing software have been punished, but turn around and sue the company because of their dissabilities. These people also have very strong advocates that can make it very expensive and time consuming for the companies to fight off. SoE has tried to steer clear and avoid these kinds of confrontations.

Modifications such as Click-to-Cure/Ability do not promote unattended gameplay and the developers have been very clear that mods like such are fine.

-I recently developed a UI mod, not a program, that made it so upon clicking a harvestable node it queued the ability so I wouldn't have to click it again and again and again to harvest (which can become a time consuming clickfest). This is an example of attended macroing.

-On the same note I again developed a Tradeskill UI modification, again...not a program. I made it so when I'm creating more than one of the same item I wouldn't have to keep pressing Repeat and Begin over and over and over. Pretty much what it did was it was your normal Tradeskill UI, but there is an extra textbox where you type a number between 1 and 100. If you typed 6 it would just click Repeat and Begin once you created the item until you made 6 of the items, it was great for writs and being an Alchemist/Woodworker (Poisons/Potions/Totems). It didn't do the counters or anything for you, but if released someone could have modified it to do such. This is an example of attended macroing and unattended macroing (you can do it unattended for grey items)

I stopped using my Queued Harvesting mod and my Tradeskill mod for the chance of violating the EULA and doing something the developers never intended me to do. I never released any of them and will never use them because I do not want to risk getting punished over my own lazyness. Were these third party programs or scripts? No, they were designed as easily as Fetish/ProfitUI through EQ2's own .xml UI system. But to risk such things? Never again.

Bottom line: Read the EULA to get a good understanding of what is and isn't allowed. If you have any questions and are unsure just ask a GM.

EDIT: there is a fine line between attended and unattended macroing.

dragowulf · 07-27-2009, 06:18 AM

To add to my previous post. You'll be pretty much safe with mods on EQ2Interface because it's part of the ZAM network which is partnered with SoE.

Quote:

Originally Posted by Pinski

I don't have a problem with the "ProfitUI" Click-to-cure(just fyi, they didn't create that, and how is that even a 3rd party program anyway? Please explain, I'm against it because I think it's a waste of time for anything besides raid curing, it's slower, bulkier, and way more prone to user error than clicking 2 buttons). As for what it is being explained in this thread, notice how it says it modifies a macro.(it doesn't say it uses do_file_commands, it says it modifies the macro).
True, it's not a 3rd party program because it isn't a program like ACT, but it is a third party modification. ACT is allowed because it's a 3rd party parser, which is fine.

Also, the scripts that were used to create the auto-attack bar before EQ2 supported in-game were against the EULA. Just ask Razieh about it, completely against the EULA. Please reread the thread before crying about what I said, notice how I am saying it shouldn't be modifying and running things automatically for you, but you just skip all that and take what information you want.
I wouldn't completely say that. Razieh was kind enough to lend me the code so I can assess myself why he could do something I tried so hard to do (I got pretty darn close), but could not. I looked over the code and saw nothing unusual or against the EULA, can you clarify with me what it was? I have the file on my PC and I see nothing. I might be missing something though.
(I'm not arguing with you)

If anything, imo, the only thing ACT should be doing is timing AEs and parsing. Everything else is just retarded shit for people who need to learn how to play. Sure it's cool ideas, but it takes away from the spirit of the game. They are made for the retarded people who can't look at a detrimental effect window every now and then. That is all they are made for. It gets old seeing how all these things are made to make the game a total joke.

Also, just because you are at the window doesn't make it within the EULA, Aditu's auto-cure in-game UI feature was told to be breaking the EULA, yet oddly enough all it did was use things in-game to do so.
This is the truth. See the last quote.

Quote:

Originally Posted by razieh

This is CLEARLY against the EULA, trying to argue that is insane. He is using a third party program to GREP the file, then turn around and create a macro in the third party program. This is not an in game macro on your hot bar, this is a macro making intelligent choices for you completely separate of EQ2. (though not very smart choices)

Would the following be against the EULA? The program reads the log files and creates macros based on what is going on in game. All you need to do as the user is spam F2 over and over, the program will cast for you based on what is going on in your group.

Agreed 100%. Not intended.

Quote:

Originally Posted by Dolby

Word has come directly from SOE that these interfaces do in fact break the EULA. I was under the impression that anything that could be made with the interface xml would be ok but I was wrong. I know EQAditu only made these interfaces with the best intentions so it saddens me to have to pull the work from our site.

For the future anything that automates game play is against the EULA even if it uses EQ2's own modifiable interface. So if you've downloaded these interfaces I suggest you remove them or you may face consequences of banishment from the game if they ever find out.

It came from this thread on EQ2Interface and is pretty much the reason why I never released and no longer use the UI modifications I had made and discussed in my previous post. I should have known better.

Vuetee · 07-27-2009, 09:24 AM

I'd say the mynzak one is probably an exploit, but something that detects who is what on which mob... for instance, who is iced on mynzak, who is cursed on thet, and then copies a string that says that isn't a problem at all... It's when you're getting it to actually do something that means you will be automating a piece of gameplay.

Another thing being is it's not even needed... it's just another detremental window in effect... people with hourglass can see their hourglass... people with thet curse can see the curse, people who are iced have an uncurable arcane... people who need salts have an uncurable arcane (and so do the tanks with charm so you just need to watch for everyone getting an uncurable arcane on then off before the tank gets it, if he gets it at that instance it's the charm, if not it's salts).

I made a program for thet-em-aua for the Mark of the Serpent as the guild I was in kept wiping and I quite frankly wanted someone to blame, as it is a simple fight where everyone knew what they were doing, but someone kept letting the side down. Again, I could have looked for 4 curses in the raid window, and I could have looked by clicking on people to check they have the curse I expected them to have, it's just another way of doing it, and if SoE didn't want us to be able to do that they wouldn't have put it there in the first place... the power drain and damage could just be turned random with a different name for example on the snake.

As far as I'm concerned, having a program that detects who you are fighting (ie matches against Thet-em-aua and if the match succeeds, have one section of the program available, if not, just not have it available... bools + if statements and crap like that or even a state table to show progression through a zone), and then tells you who is required to do the special thing, like adds on snake, or salts on xeb, or stop casting on xythus twins, or go yellow on switch, is perfectly legal, as it would only be 1 central, slightly more intelligent program than the rest (or even a combination of them all).

If you wanna complain about it, it's probably because you haven't got the capability to make anything like it, so go learn something rather than sitting on EQ2 all night every night.

Pinski · 07-27-2009, 09:41 AM

Quote:

Originally Posted by Hoss

Wow, you're pretty fucking stupid. Its more error prone to click one button than to click two. And it takes more time to click one button than it does to click two.

Uhm, did you miss the fact that you have to MOVE YOUR MOUSE AS WELL? I don't have to move my hand to hit 2 keys on the keyboard. I do have to move the mouse to the correct place on the screen then hit the mouse button, which IS in fact more error prone than clicking 2 keys on the keyboard.

Quote:

Originally Posted by Dragowulf

I wouldn't completely say that. Razieh was kind enough to lend me the code so I can assess myself why he could do something I tried so hard to do (I got pretty darn close), but could not. I looked over the code and saw nothing unusual or against the EULA, can you clarify with me what it was? I have the file on my PC and I see nothing. I might be missing something though.
(I'm not arguing with you)

He used a plug-in that made ACT hit a key every time something went off.

EQAditu · 07-27-2009, 11:18 AM

Quote:

Originally Posted by dragowulf

{...}
It came from this thread on EQ2Interface and is pretty much the reason why I never released and no longer use the UI modifications I had made and discussed in my previous post. I should have known better.

It's still about varying degrees of greyness. Since then I've released a less controversial but much more useful mod(in my opinion) that has way more scripting involved in it. As an abstract description, you could have it cast useful spells for like up to a minute or more with one action. Usually only stopping when it ran out of those "useful spells"... I often just start it and not even watch it. Sounds pretty controversial with the abstract description alone. Regardless... I can say that I've passed it with at least one SoE employee who, while not in charge of SoE policy, was in the position to understand the implications of the UI mod.

firamas · 07-27-2009, 11:52 AM

Quote:

Originally Posted by Pinski

Uhm, did you miss the fact that you have to MOVE YOUR MOUSE AS WELL? I don't have to move my hand to hit 2 keys on the keyboard. I do have to move the mouse to the correct place on the screen then hit the mouse button, which IS in fact more error prone than clicking 2 keys on the keyboard.

There you go again, using the "f-word" improperly (when you should have had an "o-word" or a "b-word" there). Tsk tsk. You're smart enough to know better, Eddie.