Money Talks Game (was:First time playing around in DAZ and F

[Craban]

It will take some time as I have to do a "real" background instead of a simple backdrop to continue.

The next part should be a little less linear and then I have to think about the hints again. I think for the existing part it's ok to give quite obvious hints as the alternative is a game restart. As soon as the options control more than an "all or nothing" flow hints should give you a direction but it's not a descision about good or bad, right or wrong. Well, at least that's what I try to achieve...

Edit: Still playing with DAZ and content - there is so much to learn. I added some examples as previews to the site linked above.

[Craban]

I would have much liked to see her bra...

Hehe, now I can see it.
I changed the light and camera settings in the hope it looks less artificial.

There are some preview images - the game itself needs a lot more work.

[Greebo]

Rikwar wrote :
There's a spelling error at the beginning which means two different things...Sweet instead of Sweat

There's 'peak' instead of 'peek' too! (I eventually got her telling me I could take a peak(sic) at her bra if I followed her, but it's 'TO BE CONTINUED')

[Craban]

Oh, my English vocabulary... Thanks, Greebo and Rikwar.

I uploaded the 'peek' now :-)

[Squeeky]

Craban,
I'm still finding some continuity issues.

Like: I've made my guess but the dialog pops up again to tell me to do that again.

Is there something in your scrïpt expecting a "double comfirmation", duplication expectancy of an onEvent type scenario? Sorry I can't specify exactly what I mean but it's a bit like onMouseOver in Javascrïpt being double called.

Hope that makes sense.

[Craban]

The hint is only updated when you move the mouse, maybe that's what you've seen. You can still change your mind and choose another color.
I'll fix that later.

Edit: The hint displaying should be fixed.

[Squeeky]

Craban wrote : The hint is only updated when you move the mouse, maybe that's what you've seen. You can still change your mind and choose another color.
I'll fix that later.

Edit: The hint displaying should be fixed.

Hmm.
Yes, there is a difference, and I did manage to get her waving as she happily exits. [I'm a little unconvinced though about the hints seeming to endure beyond what I assume to be their expected duration. I will relook at this but this is definitely growing in promise.]

[Craban]

The cursor handling has changed again and hopefully is more intuitive now. Beside a minor graphical problem the first girl should be ready and there is a simple result screen that shows how well you have done.

[Greebo]

Nice! I hope you're going to take it further.

[Squeeky]

Agreed. That is a lot better. This looks like developing into a bit of naughty fun.


Could the "No go" cursor be a little less obtrusive? Is it necessary? By that last question I mean, when you are in a 'hotspot' zone you get told anyway.

[Craban]

Well, do you mean you'd prefer the same cursor shape at all time and just rely on the hotspot hint?

I'm open to suggestions ;-)

[Squeeky]

Actually I'm not sure.

The same cursor but a variation of color in the hotspot?

Greebo and I seem to have dominated the feedback here, it would be good to get some other opinions.

As an aside thought, and not intended for consideration here,
would it be difficult for the cursor to gradually brighten as it approaches hotspots, no hints provided, and one is at the mercy of the hotspot selected? Being at the "mercy of the hotspot" would be like dating Ariane, a move too fast leads to a lesser or disastrous end.

[Craban]

Build 121 is now up. There are two opportunities to get footage.
It's still only a part of what I'd call the final game so you won't be spending a lot of money yet.
The one with the most pictures wins ;-)

Note: The animations stutter but I'm not (yet) working with blended parts so I had to use a low frame rate.

Edit: Feedback and proofreading is welcomed.

[Squeeky]

Um? The page says "Build 121" the version being loaded is "Build 100".

[Craban]

Must be a cache problem. Just reload the page, that should do it.