Foundry VTT Bug: Healing/Damage Tokens Not Showing Amounts

by Alex Johnson 59 views

Encountering issues with your healing and damage tokens in Foundry Virtual Tabletop (VTT)? You're not alone! This article delves into a specific bug report where players are experiencing problems with tokens not displaying the correct healing or damage amounts. We'll break down the reported issue, the troubleshooting steps taken, and potential solutions or workarounds.

Understanding the Bug

Let's start by understanding the core issue. The user, ironmonk108, reported a bug in the Discussion category where tokens in Foundry VTT were failing to display the amount of healing or damage applied. This means when a player attempts to heal or damage a token by a specific number, that number isn't visually represented on the token itself. This can lead to confusion and difficulty in tracking the current health status of characters and creatures during gameplay.

The user provided some additional information to clarify the problem:

  • Bug Description: When a number is entered to heal or damage a token, the token does not visually reflect the amount of healing or damage applied.

This seemingly simple issue can significantly impact gameplay, especially in encounters where quick and accurate tracking of hit points is crucial. Imagine a complex battle with multiple combatants – without the visual cues from the tokens, players and the Game Master (GM) might struggle to maintain an accurate overview of the situation.

System and Module Configuration

To effectively troubleshoot a bug in Foundry VTT, gathering information about the user's system and module configuration is essential. This helps identify potential conflicts or compatibility issues that might be causing the problem. In this case, the user provided the following details:

  • Browser: Chrome
  • Foundry Version: V13.351
  • System: D&D5E 5.1.10
  • Module Version: 13.03

These details give us a snapshot of the environment in which the bug is occurring. Knowing the browser being used, the specific Foundry VTT version, the game system (D&D 5th Edition), and the module versions helps narrow down potential causes. For instance, a bug might be specific to a particular Foundry VTT version or might arise due to a conflict between modules.

Browser Compatibility

Chrome is a widely used and generally compatible browser for Foundry VTT. However, browser-specific issues can still occur. It's always a good practice to ensure your browser is up-to-date, as newer versions often include bug fixes and performance improvements that can resolve unexpected behavior.

Foundry VTT Version

Foundry VTT is actively developed, with frequent updates and bug fixes. Knowing the specific version (V13.351 in this case) is crucial because it allows developers and community members to check if the bug is known and if a fix is already available in a newer version. It's also possible that the bug was introduced in this particular version, making it a key piece of information for troubleshooting.

Game System and Module Versions

The D&D5E system is a popular choice for Foundry VTT users, and version 5.1.10 provides another point of reference. Game systems often have their own rules and mechanics for handling healing and damage, so any bugs in this area might be related to the system implementation. Similarly, the module version (13.03) is important because modules can significantly alter Foundry VTT's behavior. A conflict between modules, or a bug within a specific module, could be the root cause of the issue.

Troubleshooting Steps Taken

Before reporting a bug, it's always helpful to perform some basic troubleshooting steps. This can help identify the cause of the problem and potentially resolve it without needing external assistance. In this case, the user, ironmonk108, has already taken a significant step by attempting to diagnose the issue. Let's examine the troubleshooting steps they've mentioned:

Console Errors

One of the first things to check when encountering a bug in Foundry VTT is the browser console. The console displays error messages and warnings that can provide clues about what's going wrong. The user noted, "That's the funny thing. There is no visible red errors." This is interesting because error messages in the console often point directly to the source of the problem. The absence of errors suggests the bug might not be a straightforward coding issue, but rather something more subtle, like a data inconsistency or a problem with how information is being displayed.

Find the Culprit Module

Foundry VTT has a useful feature called "Find the Culprit," which helps identify module conflicts. This feature temporarily disables modules one by one to see if the bug disappears, thus pinpointing the problematic module. The user mentions that the "Find the Culprit" module hasn't been updated since May 5, 2025, which is likely a typo (as we are not yet in 2025). However, the key takeaway is that they have (or attempted to) use this method to rule out module interactions. If they indeed used this method correctly and the bug persisted even with all other modules disabled, it suggests the issue might be with the core Foundry VTT system or the D&D5E system implementation itself.

Analyzing the Screenshot

Visual evidence can be invaluable when diagnosing a bug. The user provided a screenshot, which offers a glimpse into the problem. While a single image might not tell the whole story, it can provide important context. Without the actual screenshot, we can only speculate, but it likely shows a token on the game board where the healing or damage amount isn't displayed as expected. Analyzing the visual presentation can help determine if the issue is with the display of the numbers, the token's visual state, or something else entirely.

Potential Causes and Solutions

Based on the information provided, let's explore some potential causes for this bug and possible solutions or workarounds:

1. Core Foundry VTT Bug

If the bug persists even with all modules disabled, it's possible there's an issue within the core Foundry VTT software. In this case, the best course of action is to report the bug to the Foundry VTT developers through their official channels (e.g., their Discord server or bug tracker). Providing detailed information, including the steps to reproduce the bug and the system configuration, will help the developers investigate and fix the problem.

2. D&D5E System Bug

Since the user is using the D&D5E system, the bug could be related to the system's implementation of healing and damage mechanics. In this scenario, reporting the bug to the D&D5E system developers is crucial. They might be aware of the issue already or can work on a fix in a future update to the system.

3. Module Conflict

Even if the user attempted to use the "Find the Culprit" method, there's still a chance of a subtle module conflict. Some modules might interact in unexpected ways, leading to bugs that are difficult to diagnose. To further investigate this possibility, try disabling modules in smaller groups and testing if the bug disappears. This can help pinpoint the specific combination of modules causing the issue.

4. Data Corruption

In rare cases, data corruption within the Foundry VTT world or database can lead to unexpected behavior. This might manifest as issues with token displays or other game elements. If you suspect data corruption, consider backing up your world and trying to restore it to a previous version. You can also try creating a new world and see if the bug persists there, which would indicate whether the problem is specific to a particular world or a more general issue.

5. Browser Extensions

Sometimes, browser extensions can interfere with the functionality of web applications like Foundry VTT. Try disabling browser extensions, especially those that modify website behavior or interact with JavaScript, and see if the bug is resolved. If so, you can try re-enabling extensions one by one to identify the culprit.

Workarounds

While waiting for a permanent fix, there are some potential workarounds that can help mitigate the impact of this bug:

  • Manual Tracking: The most straightforward workaround is to manually track the healing and damage amounts applied to tokens. This might involve using a separate notepad or spreadsheet to keep track of hit points.
  • Chat Log: Pay close attention to the chat log, which usually displays the results of healing and damage rolls. This can provide a record of the amounts applied, even if they aren't visually displayed on the tokens.
  • Token Notes: Some GMs and players use token notes to store additional information, such as current hit points. This can be a useful way to keep track of health status in the absence of visual cues.

Conclusion

The bug where healing and damage tokens don't display amounts in Foundry VTT can be a frustrating issue, but understanding the problem, gathering relevant information, and trying different troubleshooting steps can help identify the cause and find a solution. While waiting for a permanent fix, workarounds like manual tracking and using the chat log can help maintain accurate hit point records during gameplay.

Remember to report the bug to the appropriate developers (Foundry VTT core or the D&D5E system) with as much detail as possible. Your feedback helps improve the platform and ensures a better experience for everyone.

For more information on Foundry VTT bug reporting and troubleshooting, you can visit the official Foundry VTT website for support and resources.