Author Topic: ...But I've read my journal already!  (Read 170 times)

Legacy_BelowTheBelt

  • Hero Member
  • *****
  • Posts: 699
  • Karma: +0/-0
...But I've read my journal already!
« on: January 20, 2012, 08:18:14 pm »


               I use a persistent journal system and I like it a lot, though there's one annoying feature.  Upon login, all quests are "unread", which means that you have this annoying pulsating journal icon in the upper right-hand screen until you open your journal and view each assigned quest again.

Is there a setting, through scripting or NWNx that would allow me to set these quests as "read"?

Thanks.
               
               

               
            

Legacy_Lightfoot8

  • Hero Member
  • *****
  • Posts: 4797
  • Karma: +0/-0
...But I've read my journal already!
« Reply #1 on: January 20, 2012, 08:28:04 pm »


               I hope someone can correct me and say I am wrong, But I do believe that entire function is solely in the domain of the client.   So not even nwnx can do much about it.
               
               

               
            

Legacy_ehye_khandee

  • Hero Member
  • *****
  • Posts: 1415
  • Karma: +0/-0
...But I've read my journal already!
« Reply #2 on: January 20, 2012, 08:39:15 pm »


               The trick there would be to add a command to your module's ON_ENTER script -

AddJournalQuestEntry();

The entry in the toolkit explains all, you'd make it TRUE for bAllPlayers to have them show up for all, and of course, set the nState appropriately.

Be well. Game on.
GM_ODA
               
               

               
            

Legacy_Lightfoot8

  • Hero Member
  • *****
  • Posts: 4797
  • Karma: +0/-0
...But I've read my journal already!
« Reply #3 on: January 20, 2012, 09:12:52 pm »


               I do not think that is his complaint, ehye.

I think it is more of when he logs out of the server with some quests in his journal that are persistant.  The server then get reset, on loging back in he has to reopen his journal to get it to stop flashing after the journal entrys have been added back in.  

You can try,
// Make the corresponding panel button on the player's client start or stop
// flashing.
// - oPlayer
// - nButton: PANEL_BUTTON_*
// - nEnableFlash: if this is TRUE nButton will start flashing.  It if is FALSE,
//   nButton will stop flashing.
void SetPanelButtonFlash(object oPlayer, int nButton, int nEnableFlash)
               
               

               
            

Legacy_BelowTheBelt

  • Hero Member
  • *****
  • Posts: 699
  • Karma: +0/-0
...But I've read my journal already!
« Reply #4 on: January 21, 2012, 04:53:45 am »


               Thanks for the help, guys.

Lightfoot8 - That looks like it'll do the trick.  In all my time working with the Lexicon, I never realized that function or the constants existed.

I'll give it a go and see if it works.  Gotta love this community.

Thanks!
               
               

               
            

Legacy_BelowTheBelt

  • Hero Member
  • *****
  • Posts: 699
  • Karma: +0/-0
...But I've read my journal already!
« Reply #5 on: January 23, 2012, 03:53:29 am »


               Thought I'd update quickly.  The recommended function worked exactly as expected.  Upon login, when quests are rebuilt, the panel button does not begin to flash any longer.  However, if you open the journal, the individual quests are still outlined in gold (denoting that they are new), but that's much less of an issue.

Thanks for the help.