|
|
Post by docclox on Jan 22, 2011 11:56:18 GMT -5
OK, here's some code. There are a few changes to the outline I posted before.
First of all, you can't initialise object literals with variable expressions. So o = { x+b : c } is a syntax error. I've got round this by making the string list an array and providing a function to convert to an object. In practical terms, that means you have to use "[" and "]" to delimit the list and "," instead of ":".
Second thing: I've added two more values: REFUSE for when an assistant refuses an order on grounds of principle (I remember reading that the angel wouldn't do evil things, for instance) and NOTFOUND for when something goes wrong and the eventNum isn't found in the object.
I've also added some code to allow for multiple possible responses to the same event. Basically, instead of giving it a string, you provide an array of strings. For instance:
HSE+BORED , [
"Oh what fun! Another wet nellie who needs to be shown which way up to hold a mop. Is this <i>really</i> the best use of my talents?",
"Here, taste this. Burnt water. I recommend keeping this one her back with her legs apart, since that's where her talents clearly lie"
],
HSE+HAPPY_1 , "She is lazy and slapdash, and left to herself, would leave much undone. Fortunately, I find a riding crop makes a wonderful motivator.",
HSE+HAPPY_2 , "The slave left the room clean, even if she did get filthy in the process. Maybe I should go and help her soap down those hard-to-reach places",
HSE+HAPPY_3 , "Not only do my quarters pass the white glove test, but unasked she has scented them with jasmine and lavender, and left a glass of wine waiting at my bedside. She will do.",
So for the HSE+BORED case one of the options will be randomly chosen. The others work normally.
We can also handle multi-paragraph exchanges. For this use double square brackets:
ART+BORED , "She got more paint on herself than elsewhere. If I she would rub her breasts on the canvas, we could at least sell it as abstract art",
ART+HAPPY_1 , "Composition, perspective, light... I wouldn't have it on MY wall, but I've seen worse in galleries.",
ART+HAPPY_2 , "The silly little tart turns out to have quite the good eye. I think it might be worth developing this",
ART+HAPPY_3 , [[
"$assistant: Delightful! Reminds me of the great Ercollai in his Light period. We should organise a showing.",
"$player: The great e-coli?",
"$assistant: Ercolai! The greatest of the renowned Arn-Hijienik school of art.",
"$player: The unhygienic school of art?",
"$assistant: You are <i>such</i> a philistine. I don't know <i>why</i> I put up with you...",
]],
And that pushes each string into the hopper in turn. (or that's the idea - not tested yet). This is probably a good time to mention that I've included four $variables that get expanded. $player expands into the player name, $assistant into the assistant name, $girl into the girls name, and $item into the item name (if there is one).
And since the "[[" ... "]]" syntax is just an array inside an array, it means you can combine the two:
DEH+BORED , "We take bright, vibrant young women, and we break them down until we destroy all trace of personality. Do you ever ask yourself \"why?\"",
DEH+HAPPY_1 , "She's beginning to realise that the important part of her is not the bit between the ears, but betrween the legs. Slowly, we progress.",
DEH+HAPPY_2 , "The silly slut still has this strange idea that she may be a person. But she's startibg to question it. It won't be long now...",
DEH+HAPPY_3 , [
"All that remains is a cunt that once thought it could think. You will find it obedient, without opinions, but anxious to be used",
[
"$assistant: There is nothing finer than this! To take a woman and destroy her selfhood. To make her a thing of obedient meat. Now we can start to rebuild her",
"$player: Didn't I hear you quesioning the point of this, just the other day?",
"$assistant: Darling, if you did, I must have been over-tired. We do this because it is pleasurable, and we do it because we can. What more is there?"
"$player: That's what I like to hear.",
]
],
What follows is the code that supports this: If you're just writing event scripts, you don't need to understand this.
function asLamiaEvents(eventNum):Boolean
{
return assistantEvent(lamiaEvents, eventNum);
}
function assistantEvent(events:Object, eventNum:int)
{
var ret = true;
var s:string;
var eventObj = events[eventNum];
var player_name = get_player_name(); // placeholder - not sure where to fint these
var assistant_name = get_assistant_name(); // likewise
var girl_name = get_girl_name(); // likewise
var item_name = get_item_name(); // likewise
/*
* if the event number isn't found, print the assistants NOTFOUND message
* if THAT isn't found, print a generic message with the name and event number
*/
if(eventObj == null) {
eventObj = events[NOTFOUND];
if(eventObj == null) {
storyHopper.push(assistant_name + " looks confused. She doesn't seem to understand. ("+eventNum+")")
return false;
}
ret = false;
}
/*
* With that settled, there are a few possibilities
*
* the event obj may be:
*
* * A string - to be displayed
* * an array - of alternatives
* * an array of arrays - of alternative multi-part responses
* * a function - to be executed
*
* Ordinarily, I'd say "do the simplest case first,
* but in this case things are a lot simpler if we handle the array cases first
*/
var eventArray = selectEvent(eventObj);
/*
* So now we have an event array. If the original case was a
* string or a function it will be an arrray of one string only.
* otherwise the array will be the inner array selected by selectEvent.
*
* in any case, we need to iterate over that array
*/
for(var i = 0; i < eventArray.length; i++) {
var rc = display_event(eventArray[i]);
if(!rc) {
ret = false;
break;
}
}
return ret;
}
function display_event(ev:Object)
{
/*
* ev shoudl be a function or a string
*/
var typ:string = getQualifiedClassName(ev)
/*
* simplest case: if it's a string just print it
*/
if(typ == "String") {
s = expand(eventObj);
storyHopper.push("<B>" + peopleName(5) + "</b><br>" + wv);
return true;
}
/*
* Next easiest: if it's a function we exectute the function and return the return value.
* This lets us specify events that would be too complicated to fit in the format
*/
if(typ == "Function") {
return eventObj();
}
/*
* Anything else means something went haywire
*/
trace("unexpected type in display_event: " + typ)
return false;
}
function select_event(ev:Object):Array
{
/*
* Our primary task here is this: to detect arrays and to randomly select one element from them
* So first we need to know the type of our parameter object
*/
var typ:string = getQualifiedClassName(ev)
/*
* now - if it's not an array, we wrap it in an array and return it
* that sounds strange, but it will mean that everything that comes back from this function is
* an array we can loop over - even if it only has a single element
*/
if(typ != "Array") {
return [ ev ];
}
/*
* So we DO have an array. We need a random numbe between 0 and the length of the the array.
*/
var index = math.floor(math.random() * ev.length);
/*
* replace eventObj by its randomly selected member
*/
ev = ev[index];
/*
* now - one possibility here is that ev was an array of arrays.
* if so we return the new array. But we need the type again
*/
typ = getQualifiedClassName(ev);
if(typ == "Array") {
return ev;
}
/*
* otherwise we wrap it in an array again
*/
return [ ev ];
}
I want to cobble together some testing for that, and then I'll post the tested .as file.
[edit]
One more option: you can use functions in the list too. So
BSE+HAPPY_2 , function() {
// anything you like - but you'll need to code it in actionscript
},
BSE+HAPPY_3 , name_of_function_defined_elsewhere,
So that would let you test a variable and change the response accordingly, or you could launch a new screen with a mini-game. This isn't really intended for non-coders - it's just there so we can handle odd cases that don't fit in the string list.
|
|
|
|
Post by daisy_strike on Jan 22, 2011 18:03:40 GMT -5
docclox Wow that is some interesting code. I'm still trying to dissect it. I don't normally use switch but if it makes it easier for the writers I'm willing to give anything a try. Thanks to all the writers who have helped out. Daisy
|
|
|
|
Post by docclox on Jan 23, 2011 5:14:50 GMT -5
Wow that is some interesting code. I'm still trying to dissect it. I don't normally use switch but if it makes it easier for the writers I'm willing to give anything a try. If I can help with anything, just shout out. Incidentally, it's not a switch. The original plan was to use an object with integer keys, so the ":" chars were object field delimiters. var lamiaEvents = { ITEM_ASKING : "Darling! You brought me a $item!", // ... and so on }; Which should have given us an object where you could have written trace(lamiaEvents.200) Had you so desired. The trouble is, that doesn't work. Actionscript expects an identifier on the left of the colon, not an expression. So what we get is an object field kiyed by a string: "ITEM_ASKING". Worse, fields with a "+" sign raise a syntax error. If it had been a switch, we might just have got away with it, now that I've converted the vars to consts for the event numbers. Didn't occur to me at all, at the time. Anyway. plan B: Instead of an object to hold all the number-event pairs, we use an array: lamiaEvents = [ <eventNum1>, <eventText1>, <eventNum2>, <eventText2>, ... ] And run the array through a function to create the object. It probably doesn't help that I missed out the function from the last post 
/*
* takes an array in the form [ key1, value1, key2, value2, ... ]
* and creates an object: { key1:value1, key2:value2 ...}
*/
function make_event_object(l:Array):Object
{
var key, val;
var obj = {};
/*
* Loop, as long as there are at least two values in the array.
* There should be an even number to begin with, since we're dealing with pairs.
* It might be worth the effort to check that up front and raise an error if not...
*/
while(l.length > 1) {
/*
* shift first the key. then the value from the front of the array
*/
key = l.shift();
val = l.shift();
/*
* set up a field in the object using that key and value
*/
obj[key] = val;
}
/*
* return the object
*/
return obj;
}
The nice thing about this approach is it allows a complete separation of logic from data, which is generally a good thing. Also we can write: var lamiaEvents = [ ... ];
var nekoEvents = [ ... ]'
var fairyEvents = [ ... ];
var angelEvents = [ ... ];
function asLamiaEvents(eventNum):Boolean
{
return assistantEvent(lamiaEvents, eventNum);
}
function asFairyEvents(eventNum):Boolean
{
return assistantEvent(fairyEvents, eventNum);
}
// and so on...You could even use the format as a general dialogue structure. |
|
|
|
Post by daisy_strike on Jan 23, 2011 9:37:24 GMT -5
I like that idea a lot better actually and this makes sense to me, my only question isn't loading them all up into arrays going to create even more resource usage? Another question what about multiple pages of text how would you differentiate between them. other then that I really like the array idea and then using constants to access make sense.
Daisy
|
|
|
|
Post by docclox on Jan 23, 2011 10:36:14 GMT -5
my only question isn't loading them all up into arrays going to create even more resource usage? Arrays tend to be quite cheap - four bytes for the current size and four for each element. The big usage is the data they contain. In this case that's the strings, and we were storing them anyway. Arrays and strings both are going to be tiny compared to the megabytes of image data the game handles. All in all, I'd say it's not worth worrying about. Another question what about multiple pages of text how would you differentiate between them. That was the idea behind the double-square-bracket syntax:
var events = [
EXAMPLE_CONST, [[
"each of these strings",
"gets loaded into storyHopper separately",
"in a loop",
"which I presume results in a separate page for each string",
]],
other then that I really like the array idea and then using constants to access make sense. Excellent. I'm just testing this stuff now. One minor hitch - object keys get converted into strings - so I've having to parse them back to recover the integer values. Other than that, I've patched a bunch of type clashes and typos, but not got the code running yet. Soon, hopefully... [edit] ... annnnd, that seems to work. I'll attach the .as file here. What I did was shorted out the introduction text to cycle through the lamia responses. Everything looks OK apart from "screw up" in the title box (I assume because that variable isn't set yet. And it's hard to be sure the randomiser is working correctly. Otherwise, everything seems to work beautifully. You'll probably want to fiddle with it a bit, just to get it to fit in with the rest of your code, but all the bits are there and seem to work www.mediafire.com/?k3ba4lqbpgjbwyt |
|
|
|
Post by daisy_strike on Jan 23, 2011 19:09:34 GMT -5
docclox Thanks will try to convert tonight. That was a lot of work and I appreciate you going above and beyond to get a more universal system up and running. @everyone Be advised Milking and BJ text have been added. Sorry about this, they showed up after my initial thoughts. Daisy
|
|
|
|
Post by docclox on Jan 23, 2011 20:33:28 GMT -5
Thanks will try to convert tonight. That was a lot of work and I appreciate you going above and beyond to get a more universal system up and running. It was fun  Be advised Milking and BJ text have been added. Sorry about this, they showed up after my initial thoughts. I think I did milking already. Here's some BJ events.
BJ+BORED, [
/*
* repeating the messages so the longer event only shows up
* one time in five. We could probably do this more neatly with a function.
*/
"She cannot seem to understand how she can whore wearing a chastity belt. I told her \"Just open your mouth instead of your legs.\" Darling, really, how hard can that be to understand?",
"She cannot seem to understand how she can whore wearing a chastity belt. I told her \"Just open your mouth instead of your legs.\" Darling, really, how hard can that be to understand?",
"We feed that female too much. She has voided her stomach onto the shoes of every john who made use of her tonight. One more time and she will find herself licking the boots clean again",
"We feed that female too much. She has voided her stomach onto the shoes of every john who made use of her tonight. One more time and she will find herself licking the boots clean again",
/*
* if you think this is too long, take it out with my blessing.
*/
[
"$player: how did you get on in town?",
"$assistant: Things got somewhat fraught, I'm afraid.",
"$player: Uh-oh. Did you kill anyone important?",
"$assistant: I thought about it. There was this perfect oik of a local. Fellatio was not good enough for him. He had to have pussy.",
"$player: So? Plenty of other whores in Magmell.",
"$assistant: And no sooner do I point this out than the slut starts wailing that she <i>wants</i> to fuck him.",
"$player: Really?",
"$assistant: She said she was horny and needed to come. I mentioned that this was in fact the <i>point</i> of a chastity belt, and that she would be well advised to <b>shut her fucking yap</b>, if you'll pardon my Spherian.",
"$player: Pardoned.",
"$assistant: At this point the john decides to play white knight, and argues that the slut should fuck him if that is what she wants.",
"$assistant: So between trying to explain the concept of slavery to him, and trying to get her to shut up, the whole thing degenerated into a shouting match. For two pins, I'd have eaten the both of them.",
"$player: ... and spent the next month in a digestive torpor.",
"$assistant: It would have been worth it!",
"$player: Tell you what : I just happen to have a freshly cut switch here. Why don't you take it and explain to her what happens when a slave embarrasses her betters in public?",
"$assistant: Oh, darling! Somehow, you always know just the right thing to say...",
],
],
BJ+HAPPY_1, "Well, she kept her stomach under control and her teeth from touching genitalia. Mot exactly the most talented cocksucking ever, but pleasingly free of disasters",
BJ+HAPPY_2, "I marched her into Redlight Square, naked but for a metal nappy, and had her kneel holding a sign saying \"Fuck me in the mouth, please\". If I say so myself, it worked rather well."
BJ+HAPPY_3, "Just for laughs, I cuffed her hands behind her back. It did not so much as slow her down. It pains me to say it, but she is getting rather good at this."
Speaking of omissions - the doesn't seem to be a hetero sex training category. |
|
|
|
Post by daisy_strike on Jan 24, 2011 4:21:06 GMT -5
Okay playing with it as best I can, please pardon my lack of skills.
I'm having a few issues one is that
function asLamiaEvents(eventNum):Boolean no longer gets a boolean return to tell the game that an assistant event was located. So I'm getting "You want me to... something or other" pushed for everything for EVERY event in the game. Normally this should return false if nothing was found as ALL events run through the same thing.
the other item i'm unable to quite figure out is how to choose from multiple of the same messages. IE if two writers write a bored House work message how does the game choose 1?
Ninjaing in from work and I'm sorry these are probably more my crappy programing then anything wrong with your code.
Daisy
|
|
|
|
Post by daisy_strike on Jan 24, 2011 4:21:58 GMT -5
Moving stuff around to make it easier to pull the code from the writer stuff.
Daisy
|
|
|
|
Post by docclox on Jan 24, 2011 5:54:17 GMT -5
Okay playing with it as best I can, please pardon my lack of skills. You're skills are fine. Look at how much you've achieved already in Otherworld. function asLamiaEvents(eventNum):Boolean no longer gets a boolean return to tell the game that an assistant event was located. So I'm getting "You want me to... something or other" pushed for everything for EVERY event in the game. Normally this should return false if nothing was found as ALL events run through the same thing. Well it returns the value from assistantEvent, which is boolean, although typed as Object. Easy enough to type the return. But I wonder if the problem is the old object keys as strings issue. If we pass an integer and the key is a string, I've been assuming some type coercion happens automatically. Maybe I'm wrong. (I could avoid the issue entirely by using a Dictionary instead of an object, but I was trying to keep things simple). I'll have a look at it. the other item i'm unable to quite figure out is how to choose from multiple of the same messages. IE if two writers write a bored House work message how does the game choose 1? That's the single square bracket syntax
SEVERAL_ALTERNATIVES, [
"This message from modder X",
"This message from modder Y",
[
"This is a multi-page message from modder Z",
"with more than one string",
"to be displayed",
]
],
So if a message is a string, it gets printed. If it's an array however, it gets treated as a list of alternative possible messages. That's where the select_event function comes in: it randomly picks one of the alternatives to display. And if any of the alternatives is itself an array, then the contents of that array form a multi-page event. If it helps, think of all the events as being two level deep arrays, except that we let the writers miss out the brackets if there's only one string. Ninjaing in from work and I'm sorry these are probably more my crappy programing then anything wrong with your code. I dunno about that. Let me test it by passing ints that I didn't get by iterating over the object keys hmmm... seems to work, even so. You might want to look at the get_*_name funcs in the code and make sure I got them right, that was one bit I had to mock up for the tests. Apart from that, how are you calling the code? (This is where I wish we had svn up and running). |
|
|
|
Post by daisy_strike on Jan 24, 2011 10:26:40 GMT -5
|
|
|
|
Post by docclox on Jan 24, 2011 15:56:39 GMT -5
My lips are sealed Downloading now... [edit] OK, that took longer than expected. The messages are working at least they are here, anyway. I am seeing the "I'm sorry darling..." message a lot, but it's in addition to the expected message. Investigating further ... [edit] Added a trace to asLamiaEvents - it's getting called with 100 as eventNum, which isn't one of the numbers we expected. So to that extent, the code is working: it's detecting that it's being called with an unexpected value, and it's printing a "don't know how to do that" message. Now - why's it being called with this value? [edit] OK - you're feeding all events to the assistant, and using the return code to tell if the assistant handled it or not. I didn't realise that before. So the proper behavior is to fail silently, rather than printing out a "not found" error. That might be all it needs. [edit] Yup, that's it. It just needs to fail silently, and all is well. Well, reasonably well, anyway Here's the fixed assistant.as file. www.mediafire.com/?jkuc734recfq3cj |
|
