5 réponses à ce sujet

[cstanish]

Seems like it should be pretty straightforward, but I'm obviously missing something here.  Basically, the first quest of my mod-in-progress has the main character buying a birthday present for his little sister (how everything spirals out of control from that innocuous event is the gist of the whole story). 

Anyway, I need to set a plot flag, GIFT_OBTAINED, based on whether the item is in inventory or not.  I'm buying the item from a merchant.

Following the example of retrieving the innkeeper's sword from the Demo Tutorial mod, I added the following to my module script: 

      case EVENT_TYPE_CAMPAIGN_ITEM_ACQUIRED:
      {
            object oItem = GetEventObject(ev,0);
            if (GetTag(oItem) == "sod_book")
            {
                WR_SetPlotFlag(PLT_SOD_GIFT_PLOT, GIFT_OBTAINED, TRUE,TRUE);
            }

            break;
      }

The variable ITEM_SEND_AQUIRED_EVENT is set to "1"
I made sure to #include plt_sod_gift_plot in my module script.
The plot flag in question does in fact exist (I can trigger it just fine from dialogue, but that opens up the possibility of setting the flag without actually having the book).
The script compiles just fine, but when the item goes into my inventory (item type is Gift, and it's set as a Plot Item), the flag doesn't get set. 

Anybody have any idea what I am missing?  Or is more information needed? 

[DavidSims]

What script is on the player?



The event EVENT_TYPE_CAMPAIGN_ITEM_ACQUIRED is generated by the player's EVENT_TYPE_INVENTORY_ADDED in player_core. If you aren't using that script, the module event won't fire.

[DavidSims]

cstanish wrote...

I have to confess David, I don't know what you mean by " what script is on the player." I freely admit to being a noob, and I don't recall seeing any references to player_core in any of the tutorials I've followed so far so I don't really know how to approach referencing it.

player_core is a script assigned by default to all party members. If you haven't intentionaly changed that, then it's probably not the problem.

Assuming everything is compiling and exporting properly, I'm at a loss as to why the script doesn't work, unless there's some minor typo somewhere, like in a tag. You may have to use logging to figure out exactly where it's going wrong.

[DavidSims]

cstanish wrote...

Well, I didn't change it intentionally, no but that's not to say I couldn't have done it by mistake.

I just triple-checked the tag for the item, and it's definitely correct. Hmmm.

Does it make a difference that I'm buying it from a merchant? I notice that when I first buy it, it doesn't appear in my inventory right away. I have to close the shop window and then re-open my inventory to see it.

It's worth testing. Just put another copy of the item in a container somewhere convenient and see if picking it up that way works. My instinct is that buying from a merchant should still work, but I can't say I've ever specificaly tested it.

[DavidSims]

One disadvantage of using a defined flag in this case is you can't update the journal when the player picks up the item, assuming you want a journal at all. For quest items, I like to give feedback when the player picks the item up, because they may not realize what it's for otherwise.

[DavidSims]

cstanish wrote...

OK so I copied the text of ECLog.ini which was thankfully provided in the wiki and saved it as a new ini file in bin_ship. The log indicates that the EVENT_TYPE_CAMPAIGN_ITEM_ACQUIRED is apparently not happening, as neither of the PrintToLog messages appear in the resulting log file.

Try putting the log messages in something you know for sure is running, just to make sure you are getting log messages at all.

Once you know that, make a local copy of player_core and put some log nessages in there, too see why the event is not being created/sent. There should be an inventory event sent to the player when they get the item, see if you can get a message to print then. If you do, try and see if the variable is being recognized on the item and if the code is running to singal the event to the module.