Image Designer Archive
Thread: To those MID who think the new ID Timer/XP gain isn't bad...
Please drop one level 4 box from your ID skill tree (also drop the excess ID XP if you would please), and then work you way back up to Master Image Designer again.
Please share your experience after you have done this little exercise.
- How long did it take you?
- Did you have any fun while doing it?
- Did anyone help you?
- Did you receive as many ID request without your MID title, as you did with the title?
- Would you do it again?
Thank you for your time and participation.
In light of fairness, I shall drop my one level 4 box from my Doctor (Elite Profession) skill tree, including the excessive XP, and then work my way back up again. I will share my experience with you in a couple days.
Also keep this in mind, whatwe Master IDer's think isn't going to make a difference, what makes a difference is what the DEVs and Kwee think, stop trying to get us to understand and start talking to them instead.
Cirroco:
If we don't gain the support from the Master IDs it will be unlikely to change for us. So I do understand what point he's trying to make.
Many other professions are already on a timer—medics can only heal but so often, entertainers can only flourish but so often, marksmen and brawlers can onlyattack but so often…the difference lies in two things: 1) all of these other timers are post-action rather than pre-action, and 2) the timers are much more bearable in their length.
Lunah wrote:
I disagree. I rather do 1500 ID's without a timer than 200 ID's with. If we accept the timer, who knows what will be done to all the other professions? You think they will stop here? No of course not. They finaly will realize many professions are too easy to master, so instead of adding a bit of challenge they just put everyone and everything on a friggin timer that does nothing but annoy the entire playerbase.
So with a post-ID timer, are you thinking it would start at commit and then would it keep you from "starting an IDs" or "commiting" again until the timer is up? I guess a timer that went from "commit" to "commit" is a fair good answer to this issue, it may be hard to code though.
Syzygy-Gorath wrote:
Many other professions are already on a timer—medics can only heal but so often, entertainers can only flourish but so often, marksmen and brawlers can onlyattack but so often…the difference lies in two things: 1) all of these other timers are post-action rather than pre-action, and 2) the timers are much more bearable in their length.
Sir_Voor wrote:
So with a post-ID timer, are you thinking it would start at commit and then would it keep you from "starting an IDs" or "commiting" again until the timer is up? I guess a timer that went from "commit" to "commit" is a fair good answer to this issue, it may be hard to code though.
Syzygy-Gorath wrote:
Many other professions are already on a timer—medics can only heal but so often, entertainers can only flourish but so often, marksmen and brawlers can onlyattack but so often…the difference lies in two things: 1) all of these other timers are post-action rather than pre-action, and 2) the timers are much more bearable in their length.
- All timers would begin counting at commit.
- You would not be able to initiate another ID session until the timer had concluded.
- Timer lengths would need to be reduced across the board. (1 minute for non-master IDs, 30 seconds for master IDs for cosmetic changes; 2 minutes for non-master IDs, 1 minute for master IDs for body changes—this assumes no tent)
- Stat migrations wouldtime as per a body changefor the image designer, but would not take effect for 10 minutes for the client.(preferably more…but I'm still stuck on the possible abuse of fast changes)
Message Edited by Syzygy-Gorath on 05-20-2004 09:49 AM
I would have a problem with that,asking a future customer to wait until your finished with your current customer is one thing, but asking him to wait until your finish Plus Timer time would become a big issue with me. Waiting for an timer between customers sounds very boring to me.
Syzygy-Gorath wrote:
- All timers would begin counting at commit.
- You would not be able to initiate another ID session until the timer had concluded.
- Timer lengths would need to be reduced across the board. (1 minute for non-master IDs, 30 seconds for master IDs for cosmetic changes; 2 minutes for non-master IDs, 1 minute for master IDs for body changes—this assumes no tent)
- Stat migrations wouldtime as per a body changefor the image designer, but would not take effect for 10 minutes for the client.(preferably more…but I'm still stuck on the possible abuse of fast changes)
Sir_Voor wrote:
I would have a problem with that,asking a future customer to wait until your finished with your current customer is one thing, but asking him to wait until your finish Plus Timer time would become a big issue with me. Waiting for an timer between customers sounds very boring to me.
Vicotnik wrote:
But what's the difference between a between customers timer and the current timer? The waiting is boring in either case.
With the current timer 99% of the time I use/play the time doing the ID on adverage, with the propossed timer 100% on the time you can't do any IDing.
P.S. I don't think what he is talking aboutis what I call ancustomer timer,to me with an "customer timer" the customer's ID does bo take effect until the timer is up. which I don't like the idea of ether.