The Issue Occurs While All Modules Are Disabled

Oct 13, 2025 by windailys.com 26 views

Chat Context Menu Hook Broken on v12+ (getChatLogEntryContext)

What happened?

The getChatLogEntryContext core hook has been reported to be broken in Foundry v12 Build 331, and it is also not implemented in the AppV2 rewrite in V13. This hook is essential for accessing the context menu options in the chat log, which are particularly useful in systems like the DND5E and the SWADE system. The inability to access this hook has caused inconvenience for users who rely on it for their game management.

The Importance of the getChatLogEntryContext Hook

The getChatLogEntryContext hook is a crucial part of the Foundry ecosystem, allowing users to access the context menu options in the chat log. This hook is not only essential for the DND5E system but also for other systems that rely on it for their functionality. The SWADE system, for instance, uses this hook to provide users with essential features. The absence of this hook has caused frustration among users who rely on it for their game management.

Ways of Accessing Foundry Where This Issue Can Be Encountered

The issue of the broken getChatLogEntryContext hook can be encountered in various ways of accessing Foundry, including:

Native App (Electron): The issue can be encountered when using the native app, which is the most common way of accessing Foundry.
Chrome: The issue can also be encountered when using the Chrome browser to access Foundry.
Firefox: The issue can be encountered when using the Firefox browser to access Foundry.
Safari: The issue has not been reported in Safari, but it is possible that it may occur in this browser as well.
Other: The issue may also occur in other browsers or platforms that are not listed here.

Reproduction Steps

To reproduce the issue, follow these steps:

Use Foundry v12 331: Make sure you are using Foundry v12 Build 331.
Enable Hook Debugging: Enable hook debugging by setting CONFIG.debug.hooks = true;.
Right Click a Chat Card: Right-click a chat card and observe the getChatLogEntryContext hook does not fire.
Alternative Method: Alternatively, use Foundry v12 331 and the 5E system. Right-click a roll result chat card and observe the system-specific context menu options not appearing ("apply as damage", etc.).

What Core Version Are You Reporting This For?

The issue is being reported for the following core versions:

Version 12 331: The issue is being reported for Foundry v12 Build 331.
Version 13 Testing 2: The issue is also being reported for the AppV2 rewrite in V13.

Relevant Log Output

// No relevant log output is available for this issue.

Bug Checklist

The issue has been checked against the following bug checklist:

The Issue Occurs While All Modules Are Disabled: The issue occurs even when all modules are disabled.

Conclusion

The getChatLogEntryContext core hook is broken in Foundry v12 Build 331, and it is also not implemented in the AppV2 rewrite in V13. This hook is essential for accessing the context menu options in the chat log, which are particularly useful in systems like the DND5E and the SWADE system. The inability to access this hook has caused inconvenience for users who rely on it for their game management. To resolve this issue, the getChatLogEntryContext hook needs to be fixed and implemented in the AppV2 rewrite in V13.

Possible Solutions

To resolve this issue, the following possible solutions can be considered:

Fix the getChatLogEntryContext Hook: The getChatLogEntryContext hook needs to be fixed and implemented in the AppV2 rewrite in V13.
Implement the getChatLogEntryContext Hook in the AppV2 Rewrite: The getChatLogEntryContext hook needs to be implemented in the AppV2 rewrite in V13.
Provide an Alternative Solution: An alternative solution needs to be provided for users who rely on the getChatLogEntryContext hook for their game management.

Future Development

To prevent similar issues in the future, the following development practices can be adopted:

Regular Testing: Regular testing needs to be performed to ensure that the getChatLogEntryContext hook is working correctly.
Code Review: Code review needs to be performed to ensure that the getChatLogEntryContext hook is implemented correctly.
Documentation: Documentation needs to be provided for the getChatLogEntryContext hook to ensure that users understand how to use it correctly.

Conclusion

Q: What is the getChatLogEntryContext hook?

A: The getChatLogEntryContext hook is a core hook in Foundry that allows users to access the context menu options in the chat log. This hook is essential for systems like the DND5E and the SWADE system, which rely on it for their functionality.

Q: Why is the getChatLogEntryContext hook broken in Foundry v12 Build 331?

A: The getChatLogEntryContext hook is broken in Foundry v12 Build 331 due to a bug in the core code. This bug prevents the hook from firing correctly, resulting in the absence of context menu options in the chat log.

Q: What are the symptoms of the broken getChatLogEntryContext hook?

A: The symptoms of the broken getChatLogEntryContext hook include:

The absence of context menu options in the chat log
The inability to access the getChatLogEntryContext hook
The failure of the hook to fire correctly

Q: How can I reproduce the issue?

A: To reproduce the issue, follow these steps:

Use Foundry v12 Build 331
Enable hook debugging by setting CONFIG.debug.hooks = true;
Right-click a chat card and observe the getChatLogEntryContext hook does not fire
Alternatively, use Foundry v12 Build 331 and the 5E system. Right-click a roll result chat card and observe the system-specific context menu options not appearing ("apply as damage", etc.)

Q: What core versions are affected by this issue?

A: The issue is being reported for the following core versions:

Foundry v12 Build 331
AppV2 rewrite in V13

Q: What are the possible solutions to this issue?

A: The possible solutions to this issue include:

Fixing the getChatLogEntryContext hook in the core code
Implementing the getChatLogEntryContext hook in the AppV2 rewrite in V13
Providing an alternative solution for users who rely on the getChatLogEntryContext hook for their game management

Q: How can I prevent similar issues in the future?

A: To prevent similar issues in the future, follow these best practices:

Regularly test the getChatLogEntryContext hook to ensure it is working correctly
Perform code reviews to ensure the getChatLogEntryContext hook is implemented correctly
Provide documentation for the getChatLogEntryContext hook to ensure users understand how to use it correctly

Q: What is the current status of the issue?

A: The issue is currently being reported and investigated. A fix or alternative solution is being developed to resolve the issue.

Q: How can I stay updated on the status of the issue?

A: To stay updated on the status of the issue, follow these channels:

Foundry's official forums and social media channels
The Foundry GitHub repository
The issue tracker on the Foundry website

Q: What can I do to help resolve the issue?

A: To help resolve the issue, you can:

Provide feedback and suggestions on the issue tracker
Participate in the discussion on the Foundry forums and social media channels
Contribute to the development of a fix or alternative solution

Q: What is the expected timeline for resolving the issue?

A: The expected timeline for resolving the issue is currently unknown. However, the development team is working to resolve the issue as soon as possible.

Q: What are the next steps for resolving the issue?

A: The next steps for resolving the issue include:

Developing a fix or alternative solution
Testing the fix or alternative solution
Deploying the fix or alternative solution to the core code

Q: How can I get involved in the development process?

A: To get involved in the development process, follow these steps:

Join the Foundry development team
Participate in the discussion on the Foundry forums and social media channels
Contribute to the development of a fix or alternative solution

Q: What are the benefits of resolving this issue?

A: The benefits of resolving this issue include:

Improved user experience
Increased functionality
Enhanced game management capabilities

Q: What are the potential consequences of not resolving this issue?

A: The potential consequences of not resolving this issue include:

Continued frustration and inconvenience for users
Decreased user engagement and retention
Negative impact on the overall user experience