Dancer Archive

Fix buff not resetting on death along with all the other buff bugs.

Why ? No need for me.

---

Maybe I misread your line... obviously if it's a bug, fix it ASAP. Just don't change the way buffs work ( if they work ) right now.

Okay, as far as the collision thing goes. The idea of players stopping dancing when colliding with one another was brought up by someone and I thought I'd add it to the list to see what you all thought. I think the object collision idea is a good one, the player one I'm not sure about either.

A few things to keep in mind tho.

- It does make things more realistic, some like that, some don't I suppose.

- The harrassment issues with it won't be a concern in player city cantina's for the most part.

- Could still be a problem in public cantina's if any dancers are still actually dancing in those a month from now. (get out of those nasty public cantina's already! )

All in all, its way down on our list and is more of an idea then anything. So far its not something I'm planning on pushing for because I'm not seeing a large amount of support for it. The object collision however seems to sound pretty good to most of you.

Now, for the AFK thing so you people will hopefully be happy. I'm against AFK entertainers myself so you all know where I personally stand. So when its not on my top 5 list its not because I don't feel the same way most of you all do okay?

A few reasons to consider as to why it shouldn't be on our top 5 list.

- Its already been acknowledged by the devs.

- The devs have said they want to put a stop to it.

- The devs are suppose to be working on stopping it already.

- Its already on the Entertainer Correspondants top 5 list. So its definately being covered even more.

- It took up half of my State of the Profession post.

- With player cities you won't have to live with the AFK bots anymore at least.

Seriously, does anyone think theres any point to having it take up a spot in our top 5 list still? Its still a big issue and will be until more is done but the more is coming and I think we've got our point accross. With that in mind I think its in our best intrest to focus on other issues/things we want don't you? Let me know what you think okay?

---

nvoigt wrote:

Seriously, server side collision detection of 3D models that lag is a coding nightmare par excellence. They could probably fix this list plus every otherprofession for the cost of implementing this.

---

LoL, I'll keep that in mind Nvoigt. Guess its a good thing its not on our top 5 list isn't it? heheh

/think I should wait and read Ravens posts before posting *g*

Seriously, does anyone think theres any point to having it take up a spot in our top 5 list still? Its still a big issue and will be until more is done but the more is coming and I think we've got our point accross.

---

I think with the stubborness the DEVs have displayed in player communication so far, keeping that point #1 won't hurt. I'm sorry to say that, but the DEVs have proven to be either untrustworthy or liars or incompetent handling simple communication ( pick the one you like ) time and again. Hammering it home can only benefit us. I would gladly haveonly one point of this list fixed as long as it's Macrotaining.

Hey, some of us LIKE our public venues. I love Keren cantina. Nothing is going to make me stop dancing there at least once or twice a week, no matter what -- even if my group of friends ends up, as we've been lately toying with, making its own player-run, RP-focused city.

Unless we have the ability of fine-scaled control of our dancers even a co-ordinated troupe is going to end up slamming into each other on occasion through no fault of their own. Since our dev has already said that fine-scaled control would not be possible any time soon because of how things work with the client overall, I think stopping dance upon player-player collision is a terrible idea. Most particularly you could do nothing wrong and some new dancer who hasn't figured out how to control her formal dance can stop you from dancing.

Also, I don't think the client right now recognizes ANY player collisions. Why should it recognize it just for dancers? My guess is it can't. They'll have to either turn it on for everyone, or no one. You've just added thousands of new computations that have to be done each second on reciprocal pairs of moving objects. Can you say "lag"?

So again. OBJECT collision detection stopping a dance: fine. PLAYER collision detection stopping a dance: bad idea.

C

---

nvoigt wrote:

Seriously, server side collision detection of 3D models that lag is a coding nightmare par excellence. They could probably fix this list plus every otherprofession for the cost of implementing this.

---

I'm not sure how'd they'd make it happen, and I'm not even saying I'm in favor of this change, but collision detection between avatars shipped as part of EQ 3-4 years ago. I think, especially since it's the same development company, that perhaps we should let the devs decide how difficult any particular effort is and judge our top 5 based on what we want, not what we think they can do.

- J

"You don't apparently do a very good job reading the boards or the lists people post then or more likely the case you probably just don't spend nearly the amount of time reading posts on these boards that I do."

Wow ok, well I guess I won't offer any opinions on your forum anymore your majesty.

- Okokta Whira (part time Lowca entertainer)

My top 5 issues for entertainers;

1. AFK

2. AFK

3. AFK

4. AFK

5. AFK

Yes, throw everything else aside until you get this FIXED. And it's not a matter of PRO-AFK or ANTI-AFK. AFK should not be allowed. If people think it is a too long of a grind to do ATK, then think of ways to speed up dancing, and dance healing xp. It's not a matter of should they be allowed or not. Until this is fixed, the class will be completely broken.

Excellent list.

Thank you for your efforts.

I agree whole hartedly leave the macros be! Cheaters will always macro with outside programs, entertainers NEED macros. I think an hour of unatended play is a fien time, If Im called away for over an hour Im probly about to log out anyhow. However 15min on unatended ACTION is a fair number too. If your runign a boogie macro thats longer then 15min your acts geting old anyhow. There is no reason to be away from the keyboard gaining exp for mroe then 15min. Personaly I dont think its fair to gain a single exp point AFK., but its unavoidable if your runign a macro and get called away. So I would like CSRs to send tells to people they suspect are AFK levelign an if no response is given in 15min suspend the account, after three suspensions ban the account.

Well, not much has changed from the last list, so it's still good. I know some of my ideas are not up here and what I consider to be the top five issues are different from the spoken majority. That's fine. I know I am at least in the spoken minority about what I think are issues and ideas for the Dancer profession and most probably in the general minority. I'm glad at least there is some overlap and some of what the spoken majority agrees needs to be looked at are things that I have issue with too. I know that many of the things I want will never happen, but I still get wistful about it. Hopefully once some of the long-awaited changes go through the focus can change and we can have some new ideas and new complaints.

Staren Langio
Chilastra Galaxy

Sorry if I'm being repetitive (in case someone else mentioned)

but here are my thoughts:

First and foremost - Please give all dances 8 full, motion-captured flourishes. Get rid of the current added flourishes to the dances which have not been motion-captured. They make dancers look like rag dolls being pulled along strings.

Second - At master level dancers should never fall. If you are a master, you should have theknowledge to keep from making such a serious blunder, especially when you are performing one of the more beautiful, exotic dances. How embarassing!

Third - I would like to see a wider variety of dance styles sometime in the future. I hope the dev team is already considering this.

Most of my other concers have already been reflected in this thread so I won't repeat them