Where did all the writers go to? At this point Girlsmeets/Interaction texts are like 90% of the remaining workload for the @, I've done all I could with the code save a major review. Get working (sound of a whip)!
Well, as for what I've been doing. ... my bed has been very comfortable lately, and my recovery vacation ends on friday. Not that going back to work will change anything. (I can still do writing after work, it's not a big deal, but my responses on the site won't be as often or push updates)
There's a big problem I've encountered; I'm not entirely sure how you're wanting to do the girlsmeets/interactions/etc.
I'll try to explain what I'm talking about.
Right now we have a lot of code blocks for each action ( you probably know this), and inside it's just sorted by two long elif nests. One for 'yes' the other for 'no'. My biggest issue, is I have no clue which traits should be there and which shouldn't. And should we be using multiple tags at a time?
ex:
elif "Egocentric" in chr.traits: (most are single like this)
elif "Optimist" in chr.traits and "Lolita" in chr.traits: (others are double like this)
Basically, what I'm saying is the work load currently looks infinite to me. Also, I remember reading that we're not even sure if we're going to keep all the traits or not, or change them etc etc etc.
Don't get me wrong, I can certainly get 'into the zone' think a personality (or whatever trait) through and put in some lines, but I'm not confident in what you (the management) is expecting in terms of the @ release.
I tried going through the traits xml file to see what was there but ... aren't there like a hundred traits?! Do we need a line for each trait?
But as for what would really help me (as far as writing is concerned), is having a little more direction. Basically tell me, "I want X many under general, X many under <certain trait>, X many under <certain other trait>" or you could even put it in comments in the code, that would work too. But that way, I'd at least know what traits I can ignore; for the @, at least.
I'll need at least some of this so I can get some idea of what we need. Then I can go through and tell myself "ok, tonight I'll get X traits done for Y action" and work piece by piece. But right now it's just one huge blob of work.
Best case scenario: have someone tell me
elif ct(<trait(s)>):
$rc("") #want <whatever number> of responses here <----
That way I can start going through filling it out.
_________________________
Issue #2
Also, how are you wanting the logic under the insult actions to be done? Wouldn't getting insulted piss off most women? This seems like something other than the 'writing' department.
And issue 1 applies to this as well. What's the bare minimum traits/number of responses desired for the @?
__________________________
possibly issue #3?
Right now, if we have every single trait in the elif nest. Will the general responses even be used? What if a girl has multiple traits? Should the code be able to select a response from any trait or multiple responses? Because right now it only chooses the first one, right?
This seems more like a design issue, more than a writing issue. But it affects the writing portion, or at least, it may cause problems in the future.
The most important issue is #1. If that one is addressed, I can at least work while the others get sorted out.
Any responses are appreciated.
p.s. I have no idea what any of the other writers are doing, since I rarely see them communicate via this forum. Also, I work alone, so hopefully I won't do something someone else is working on. If there are any issues like this, please let me know.