Jump to content

boaspessoal

Member
  • Posts

    65
  • Joined

  • Last visited

  • Feedback

    0%

Everything posted by boaspessoal

  1. You probably have multiple files triggering the same event making it count twice instead of one(like intended), because as @Syreldar said, the kill trigger is fine, clean your object folder and compile the quest again and see if it counts twice again. Cheers
  2. You can open the .obj files in 3ds max and export as .gr2 with a plugin.
  3. Something like: So it returns esem[0,1,2] whenever you are using 324,325,326.
  4. I think you're trying to call a value out of range. So you use 324/325/326 vnum and then later you add: But then you call for:
  5. Fixed, was some sort of problem in the localeinfo.py(I changed it somehow and of course something unintended came up). Look, I know you think you're better than everyone else(I can tell because of your arrogant answers all around this forum) but why even bother replying in QUESTIONS if you're not going to provide an answer/some sort of help? I honest to god can't get it through my head.
  6. Hey guys, lately i've been having this problem with my client in which I can't even open it at all and it pretty much came from nowhere. The error is as follows: system.py and prototype.py(respectively): syserr is pretty much empty all it has is abort. Thanks in advance!
  7. So recently there have been a few threads asking for a method to make monsters not take damage when a player's wearing x item and I was wondering if there's such a method to apply in a dungeon quest like for example, when the monster gets to 50% hp it triggers some event and it stops taking damage, so you need to do something before it starts taking damage again(like meley's lair statues for example) EDIT: I just remembered, maybe the d.unique_get_hp_perc function can take place here Thanks
×
×
  • Create New...

Important Information

Terms of Use / Privacy Policy / Guidelines / We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.