Jump to content

spyderbytes

Member
  • Posts

    200
  • Joined

  • Last visited

    Never

Posts posted by spyderbytes

  1. I have yet to actually run out of dialog nodes (though I've come close in a couple of towns), but I do try to conserve them. Thing is, I have a few "chatty" NPCs (not necessary stuff, generally--usually comic relief) that can really chew through those nodes. smile

  2. Quote:
    Originally written by coreyh:
    There isn't a common variable size that holds
    -255 to 256.
    Which is why I remember having read that's what SDF range was... I remember being surprised. smile However, since I can't seem to find where I read it, I can't say for sure, now, if it was an "official" source, or someone just guessing and presenting it as true.

    Guess it's time to make a party of SOBs and see if/how badly my scenario breaks. smile

    EDIT: If all else fails, RTFM. smile Docs for inc_flag():

    Quote:
    void inc_flag(short a,short b,short how_much) - Changes SDF(a,B) by how_much (which can benegative). Note the legal range of values for a flag is 0..255.
    Guess that answers it... shocked
  3. A combination of erase_char() and place_monster() ought to do the trick. That is, unless you're talking about the party or an NPC that's expected to have dialog--then the problem becomes much more complex. smile

  4. I can't find it now, but I remember reading somewhere that the valid range for SDFs is -255 to 256. Is that correct? Anyone know for sure?

     

    I've been assuming it is, and so my 'karma kounter' starts with 0 as neutral and uses inc_flag() calls (plus or minus) when the party does good/bad stuff.

     

    Your example dialog would be a bit cleaner (and save you a node, if you run as tight on them as I tend to wink ) if you used action = DEP_ON_SDF instead of the condition check. That would also make your article a tutorial, of sorts, on one of the more advanced dialog techniques. smile

  5. I don't mean to insult your intelligence, but have you checked to make sure there's no set_state(), set_state_continue(), end() or anything like that between the start of the LOAD_SCEN_STATE and where you init the quest? That sort of thing can easily slip up on you if you forget you had a call like that and just append something before the break (which I often do wink ). At any rate, the symptoms seem to be pointing to some kind of "gotcha" rather than a problem with the call.

     

    Only other thing I can think... I notice you have this as quest "1". Do you already have a quest "0"? I wouldn't think that would matter, but then, I do start with 0 and it works for me. smile

  6. Actually, I think it might be Jeff's string handling that has some bounds checking problems. I had the same problem (crashing after load from a save) in one script where I was using string constants defined at init (then putting them in dialog by var name).

     

    As soon as I cut and pasted the strings directly into the message_dialog() call, the problem went away.

     

    Try doing something like play_sound(-57) instead of the message_dialog() and see what happens. I was thinking the problem was the string constants, but it could be something slightly screwy with message_dialog() itself, I guess...

  7. ^ That, too. smile I knew there was another point I intended to make but forgot. Drakey's article is quite good.

     

    You can also check here for some creature scripts you could use "as is" or as inspiration for things you can do in creating your own monsters. Just don't hold the scripts of mine there against me... I was just learning Avernumscript when I wrote those. I should update them with what I know now, I suppose...

  8. ^ That, too. smile I knew there was another point I intended to make but forgot. Drakey's article is quite good.

     

    You can also check here for some creature scripts you could use "as is" or as inspiration for things you can do in creating your own monsters. Just don't hold the scripts of mine there against me... I was just learning Avernumscript when I wrote those. I should update them with what I know now, I suppose...

  9. 2, 3. You can do these right now. You can individually set a monster's resistance to Fire, Cold, Magic, Mental, Poision/Acid, and Melee, anywhere from 0% (no resistance) to 100% (completely immune).

    4. I'm sure this can be "faked" somehow, though I haven't given it enough thought to know how. smile

    5. No way to do this that I know of. And I agree... it would be nice to have (but unlikely we'll ever see it).

    7 - 14. Most of this can be faked with some creative scripting.

    15. I would definitely like to see this, too (but doubt that we ever will). I could do some interesting things with it. smile

     

    EDIT: Had a typo shocked

  10. 2, 3. You can do these right now. You can individually set a monster's resistance to Fire, Cold, Magic, Mental, Poision/Acid, and Melee, anywhere from 0% (no resistance) to 100% (completely immune).

    4. I'm sure this can be "faked" somehow, though I haven't given it enough thought to know how. smile

    5. No way to do this that I know of. And I agree... it would be nice to have (but unlikely we'll ever see it).

    7 - 14. Most of this can be faked with some creative scripting.

    15. I would definitely like to see this, too (but doubt that we ever will). I could do some interesting things with it. smile

     

    EDIT: Had a typo shocked

  11. For your point 7, you can come close to "faking" it by only putting (for example) flaming arrows in your scenario (that do most of their damage from fire). Then make the monsters immune to fire damage.

     

    It would have been nice to have damage broken down by piercing/slashing/bashing/etc., and being able to set resistances to each. But the system we have will work, if not as well. smile

  12. For your point 7, you can come close to "faking" it by only putting (for example) flaming arrows in your scenario (that do most of their damage from fire). Then make the monsters immune to fire damage.

     

    It would have been nice to have damage broken down by piercing/slashing/bashing/etc., and being able to set resistances to each. But the system we have will work, if not as well. smile

  13. So you're essentially wanting to change which sheet is used for outdoor cliffs? I sure haven't seen any call to set that (but then, I've done very little outdoors so far).

     

    If you're wanting it to be used everywhere outdoors, you could define your own cliff terrains and copy them into the default numbers. But I don't know of any way you could change some of the cliffs, but not all, if that's what you're wanting.

     

    EDIT: If that wasn't clear, I was talking about:

     

    begindefineterrain my_number;

    import = current_cliffs_number;

    te_which_sheet = sheet_number_you_want;

     

    begindefineterrain original_cliffs_number;

     

    That last line will copy it back where it was, just with a different sheet.

     

    EDIT 2: Left out an '=' in my pseudo-code. smile

×
×
  • Create New...