kiya

Writing up the description for the tree would work much better if I remembered to include the line of code that tells the game where the tree is.

In other news. . . .

IT WORKS! Itworksitworksitworks. It works and I wrote it.

I mean, I didn't write all of it, but I wrote . . . I wrote descriptions of a couple of rooms, and then went into coding my first puzzle. Which included an NPC. Who says something the first time he sees you and never repeats it. Which took me a while to do, because the first time I coded it he said it every fucking turn whether or not you were in the same location as he was. (There's a carrying voice.) And then it wouldn't work at all. And asking him about the various stuff you can ask him about took a bit of debugging, because of the if-clause and code shuffling that runs with one of the asks. Then I had to code the bit where he doesn't let you go by him. And the bit where you get him to go away, which required me to code a verb.

But it all works. Even the updating the game score when the puzzle gets solved.

Current Mood: ecstatic

I think this flash animated soy sauce commercial may be even weirder than the kitty porn ASCII flash. (Link to the soy sauce courtesy

agrumer.)

In other news, I may not be able to code in TADS from scratch, but I speak enough OO conceptually to go look at the definitions for the defaults and find the bit that runs in response to a particular command. And while I stared at the thing in bafflement, I could pull it out, modify the message that gets printed appropriately, and add a line that toggles an attribute from 'nil' to 'true'. I'm sure there was a much more tidy way of writing that specific case, since the result is a duplication of the general case code with Stuff added, but hey! It runs! And it worked on the first run-through! Fluency can come with time, I'll settle for actually getting done what I want done.

Current Mood: enthralled
Current Music: "Breathing", Lifehouse