Manage a global history log per token to track event which happens outside a combat

Principles for the first version

Logs are managed using a specific token for each player.
This log token needs to be manually created on _Main_AE map.
It must be of type RQ_Log
It must use the naming convention : tokenLog_the token name (ex: tokenLog_PJ_TST01)

No archiving at this stage :

tokenLog json content can be copy/paste to a json text file before cleaning the log token

Macros related to the feature ONLY :

libRQII/sheetView/showFilteredTokenLogEntry.rqm
libRQII/sheetView/viewSheetLogs.rqm
libRQII/tokenPropertyManagement/editTokenLogEntry.rqm
libRQII/tokenPropertyManagement/findCurrentTokenLog.rqm
libRQII/tokenPropertyManagement/updateTokenLogEntry.rqm

Other macros which are modified for this feature :

libRQII/combatAction/addCombatLogEntry.rqm
libRQII/combatAction/updateCombatProactive.rqm
libRQII/eventHandler/onCampaignLoad.rqm
libRQII/locHpAp/updateAPHP.rqm
libRQII/sheetView/openSheet.rqm
libRQII/sheetView/viewSheet.rqm

sessionName is defined the campainDesc property of lib:RQII token on _Main_AE map.

In order to log an action on both the combatLog and the tokenLog the addCombatLogEntry macro must be called with an additional param set to 1.

As for example in the updateCombatProactive macro

[h, if (action == "firstCast"), code:{
    [h: "<!-- We log also to the tokenLog -->"]
    [h: addCombatLogEntry(tokenId,"proactiveAction",logMsg,logComment,"1")]
  };{
    [h: addCombatLogEntry(tokenId,"proactiveAction",logMsg,logComment)]
  }]

feroulm / rptoolsRQ

Manage a global history log per token to track event which happens outside a combat #85