agnari posted:

---

LTx isn't intended for UCM


WHAT a joke, a solid majority of folks that use it use it SPECIFICALLY for that purpose.

---

Lil-Blub posted:

---

My insight...


Make it the choice of the user. UCM friendly or not. The user would then have the choice to also get banned should they get caught. All in all, let the enforcement be in Turbines hands. NOT a Developer. You can go into all the logistics. Why? To show your in control of something you really have no control over?

Anyone who's willing to learn programming can make their own program that macros. Sometimes it's not always public. I have even SEEN ones that run to town, restock, and run back to your dungeon and resume. I call that automated! And yes recently.

---

-Kiande- posted:

---

Yeah, it's pretty freaking annoying when someone logs off, giving the leader to an AFK guy. Then people die and don't log off.

So I throw stuff on the leader to get him killed, he logs off and gives leader to the AFK guy @ lifestone, and I spend an hour waking people up to make a new fellow.

---

-Eps posted:

---

By adding any automated features on death they are showing that the macro, or atleast part of the macro, is geared specifically for UCMers, and if they add it they can no longer have a stance of lifetank being an anti-UCM, but still an automated combat, plugin. Lifetank automates repetative tasks-killing, looting, salvaging, buffing, etc-anything else is too simple and has such a low occurence that the only reason of having it is so that it's done while unattended.

Sure a forced log on death feature is for saving your fellow's xp, but unless the fellow leader is unattended as well, then that shouldn't be an issue. Adding a forced log on death, any feature on death for that matter, is just encouraging UCMing more because the user knows that if they die and the macro stops hunting, it will just log out and it won't be an issue. If somebody dies, the fellow will know about it. They deal with it by booting, or they stop fellowing that person the next time. If somebody is known for UCMing and having their macros dying, destroying fellow XP, then they aren't going to be recruited into fellows now are they? Then they won't be able to get XP at all from a fellow. If the leader of the fellow is unattended when something like this happens, then you need to let people know to not join fellows where that person is the leader. Give attended players leader. It shouldn't have to be a macros responsibillity to deal with an issue that the leader of a fellow should be dealing with.

Don't recruit people who sit at ls when they die. Don't recruit fellow leaders or join the fellows of people who sit unattended when there are issues they should be taking care of. Spread the names of people like this around the server. They're going to think again before they UCM so carelessly if you make them suffer the consequences of their actions. Don't give in to careless UCMers and you won't have to deal with dead macros ruining XP.

You're just being greedy and selfish if you're ok with something wrong as long as it benifits you. It's your own fault. Stop helping UCMers by sharing your XP with them and they will stop UCMing so much if they want the full benefits of a fellow. Stop going into fellows full of UCMers and a UCM leader just so you can get more xp, if you're not ok with a chance of a dead UCM at the LS. You're just being greedy. Either accept people UCMing and deal with the consequences, or don't put yourself in a situation with them in the first place. Sure you can't control everything everybody does, but you can get a lot more done than you think.

---

-Eps posted:

---

eps best anti ucmer in ac

---