Image Designer Archive

• Migration


• Holoemotes (All)


• Height


• Nose Protrusion


• Eye Shape


• Eye Color

You probably don't need to be as specific as that. Usually a client will be able to notice any changes s/he doesn't like by visually watching her/his character. If it a case where armor is on they probably won't be asking for any aesthetic changes so it may be enough to just notify them a change has been made.

It may be less bulky to just have one notification for each tab we have, for instance: Face, Body, Cosmetics, Hair, Tatoo, Fur, etc. That way you have less of long confusing list for them to look at - nose protrusion, whats that? What did you do to it? Etc.

Unless of course there is potential instance I am missing where the detail would be necessary.

That's what was so nice about the old system - "so and so wants to change your NOSE" so the client has an idea of what is being changed.

Edited because I was basically saying the same thing as Syzygy, but I had just misread Syzygy's post to begin with...

Message Edited by NJ62 on 09-09-2004 09:20 AM

---

Syzygy-Gorath wrote:

My own feelings:

At first I had suggested a set of tabs for the client much like our side of the interface has, each bearing a checkbox related to one of our sliders/pickers. These checkboxes would allow changes to the specified characteristic, and would also be subsumed by "Allow All" checkboxes at the bottom of each tab (i.e. "Allow All Hair Changes.") While this system allows for more granular control and greater peace of mind for the client, there are two problems with it: 1) there's scant space for it with the before/after readout and 2) it becomes a chore for both client and ID to allow all of the required changes each session.

With these two problems in mind I would like to suggest a new safeguard. Two new yes/no readouts would be added to the client-side interface listing whether or not cosmetic changes and/or physical changes had been made. In addition, a "Change Manifest" button would be added that would open a new window displaying a list of every change made during the session. The list would not provid any real detail, just the name of the changed characteristic, for instance:

• Migration
• Holoemotes (All)
• Height
• Nose Protrusion
• Eye Shape
• Eye Color

I believe that this would address the client's need to be able to verify what changes we have or haven't made without further bogging down our already forcibly-lengthened sessions.

---

I agree, but I would also add little clicky boxes next to these so that the person could accept what they wanted to accept and decline the rest. There is no sense having to wait another 10 minutes just because someone accidently or intentionally made some cosmetic changes that the customer does not want.

---

NJ62 wrote:
That's what was so nice about the old system - "so and so wants to change your NOSE" so the client has an idea of what is being changed.

Edited because I was basically saying the same thing as Syzygy, but I had just misread Syzygy's post to begin with...

---

Yes. That would be nice. I too agree with Syzygy. I think information on what had been changed should be provided to the customer in some way or other.

---

SFXGenesis wrote:

I personally like the idea of a generated list of changes, but not too specific. I think "Nose Protrusion" or "Eye Color" is sufficient information for the client. Giving exact measurement means bringing the numbers back....ugh...let's not go there.

As for the payment option window, I think the "Required Credits" field and some lines in your bio is sufficient. (Yes, I know....90% of people don't read bios unless it is to determine whether they are stronger than a potential opponent or not)

As for other ideas....hrm....let me toss my brain around inside my head a bit....

Sorry....still stuck on the whole droid module for migrates thing...if I get past that today, I'll let y'all know. /grin

My two creds,

Dan

---

Hmm, you must like counting clicks a lot. Considering every slider has around 225 clicks, I'd rather have those numbers back thank you.

I agree with no click-boxes. The biggest pain about ID for me is making sure the customer, every customer, is properly trained before we do the migration or whatever. Adding more things to explain leaves more room for frustration and error.