Jump to content

Think

Member
  • Posts

    175
  • Joined

  • Last visited

  • Days Won

    4
  • Feedback

    0%

Think last won the day on August 15 2015

Think had the most liked content!

About Think

Informations

  • Gender
    Not Telling

Recent Profile Visitors

7969 profile views

Think's Achievements

Collaborator

Collaborator (7/16)

  • Very Popular Rare
  • First Post
  • Collaborator
  • Conversation Starter
  • Week One Done

Recent Badges

117

Reputation

  1. Your issue is likely to be memory corruption anywhere on the code (that is, not just that file). Roll back all changes until the moment you had this issue and then analyze them carefully or spend a long while tracking what's being done to your items and under which conditions this will end up happenning. Good news is, it crashes every day, so it must be easy to reproduce.
  2. Trigger on kill, and then loop through quest members with something like... local pids = {party.get_member_pids()} for i, pid in next, pids, nil do q.begin_other_pc_block(pid) --stuff with the other player... pc.functions() will act as if it's another char q.end_other_pc_block() end As for the problem with killing in party, party_kill is only triggered for the leader when either the leader or someone on the group kills anything. Some kill trigger with party conditions (but without party flags, is it really intended that progress is shared?) seems about right though.
  3. %%A is not a thing ([Hidden Content]). This will just do (like Denis said), there's no need to complicate it more than it:
  4. I am confused as to how this is supposed to work: - weekend will hold the weekday as number (e.g 6) - day will hold % + weekday's full name (e.g %Saturday) - or simply '%', not quite sure how it's parsed. (ref for what the os.date yields: [Hidden Content]).
  5. return day > 4 or day == 0 greater than 4 and 0 Ahem, 5 and 6 are greater than 4.
  6. so 5, 6 and 0 are valid weekend days. How long do your weekends last? Mine have two days!
  7. You can use this one and modify it for your needs:
  8. Unless someone has specific experience on crashes with those serverfiles or are magicians, without syslog/syserr we're all clueless. If you have core files, you can also try to debug them yourself.
  9. Well, yes, so long it doesn't keep increasing forever You can check your player.item_award table, there you will have all the ids that the database is loading.
  10. That's item_award loading for things not yet associated to an ingame item, completely normal thing.
  11. Did you just change game without changing database?
  12. The quest is just a test, I'm not sure why you'd want to use it (To quickly see if its working, I hope? You can easily extend any other quest to test, though). As for why it doesn't work, I suppose you didn't add the parenthesis after npc.is_pc()
  13. @Rideas your function will forever try to re-equip new arrows each time an arrow is shot, provided only one arrow of type 79503 is equipped. If you want to prevent vnum 79503 from reducing arrows, you are better off with an if(...) return; at the very beginning.
  14. You really shouldn't have more than 3, I think 4 are as many pages you can have without overflowing the datatype.
  15. ... no. You don't need to do anything in UseArrow, you don't even need to keep the UseArrow function.
×
×
  • 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.