Author Topic: Personal Reputation and Reaction System 2.2  (Read 492 times)

Legacy_henesua

  • Hero Member
  • *****
  • Posts: 6519
  • Karma: +0/-0
Personal Reputation and Reaction System 2.2
« on: March 19, 2011, 02:37:04 pm »


               I have been playing around with Vendalus's PRR system and discovering minor bugs here and there in the process. I don't believe I've found any show stoppers, but this is unsettling as I have not been testing for any of these bugs. I simply stumbled upon them. The latest issue I have noticed as attributable to PRR is a very long pause before character creation when launching the mod in single player. This completely goes away when I comment out all calls to PRR in the on module load event.

Question 1:
is anyone else using this system?

Question 2:
have you run into major problems with this code and if so what are they? performance problems? poor DB integration? overall failure?

Question 3:
would you use a bugfixed version of PRR posted on the vault?
               
               

               
            

Legacy_DM_Vecna

  • Hero Member
  • *****
  • Posts: 501
  • Karma: +0/-0
Personal Reputation and Reaction System 2.2
« Reply #1 on: March 21, 2011, 02:21:55 am »


               I am using the PRR for my new PW. However I changed it to use NWNX instead. I did have to rewrite some of the functions to use NWNX and along the way found a few bugs but not any show stoppers as you also note. I really have a lot of fun with it though. I created 40 separate factions that are a blast to play with. If you have any questions fire away. You can also search on the old forums under my handle and will see some of the threads where I was asking others smarter than me about it.
               
               

               
            

Legacy_ffbj

  • Hero Member
  • *****
  • Posts: 1097
  • Karma: +0/-0
Personal Reputation and Reaction System 2.2
« Reply #2 on: March 21, 2011, 11:50:10 pm »


               I use it.  About the only thing I noticed is that when an npc kills certain creatures and you use the adjust enemy factions you will sometimes get a TMI.  Not a problem for me since I just tell the system to ingnore any faction adjustments that are not related to the PC.  So the script will fire, at least the adjustment part, only if a PC actually killed the npc.

Currently I have 10 factions that have persistent relations with the PC.  The opposed ones will like you if you kill their enemies.  So if you alignment is reasonable with that faction they will like you.  You can even have undead friendly to you for instance.  At the start of the campaign no-one, no faction will hate you until you start killing their members, or attack their holdings, totems.  Then for real mistakes, like the guards, pirates, etc... hate you I have a fixer guy who will adjust your faction for a fee, that is, you pay wergeld for you mistakes.
               
               

               
            

Legacy_henesua

  • Hero Member
  • *****
  • Posts: 6519
  • Karma: +0/-0
Personal Reputation and Reaction System 2.2
« Reply #3 on: March 22, 2011, 11:00:36 pm »


               Thanks for the info on this. I'll post more issues to this thread as well when I find them.
               
               

               
            

Legacy_henesua

  • Hero Member
  • *****
  • Posts: 6519
  • Karma: +0/-0
Personal Reputation and Reaction System 2.2
« Reply #4 on: March 22, 2011, 11:02:15 pm »


               WTF? Double posting?
               
               

               


                     Modifié par henesua, 22 mars 2011 - 11:02 .
                     
                  


            

Legacy_henesua

  • Hero Member
  • *****
  • Posts: 6519
  • Karma: +0/-0
Personal Reputation and Reaction System 2.2
« Reply #5 on: April 10, 2011, 04:26:54 pm »


               FYI - That pause during module load was actually not attributable to PRR. I had mistakenly removed DMFI at the same time from my OnLoad and OnClientEnter module events. After putting PRR back in and taking DMFI out, I've realized that the temporary hangup is due to the latest DMFI scripts.