Foundry VTT Initiative Bug & Feature Request

Hey guys! Today, we're diving deep into a pretty significant issue some of you might be experiencing with Foundry Virtual Tabletop (VTT) concerning initiative tracking. We'll be covering a bug where rolling for initiative creates duplicate characters in the combat tracker, and also a feature request to enhance manual initiative entry. Let's get started!

The Initiative Bug: Duplicate Characters Galore

So, the main issue here is that when some players roll for initiative, Foundry VTT seems to be creating a duplicate of their character in the combat encounter tab. This isn't just a visual glitch; it actually adds a new combatant with a potentially different initiative value, throwing the whole order into chaos. Imagine the frustration during a tense battle when suddenly there are two of the same character acting at different times! It’s like having a time-turner but without the cool Hermione factor.

This bug seems to surface particularly when there's a mix of initiative methods being used. Specifically, if some players manually enter their initiative values while others roll for it, the problem is more likely to occur. To reproduce this issue, you just need a scenario where one person enters their initiative manually, and another player rolls for theirs. Bam! Two of the same character in the combat tracker. This has been tested across different operating systems (Windows 10 & 11) and browsers (Chrome, Edge, and Firefox), so it’s not an isolated incident.

The user who reported this issue, strongpauly, has diligently tested this with all modules disabled and enabled, confirming that it's likely a core issue within Foundry VTT or the DnD 5e system. This eliminates the usual suspect of module conflicts, making it a more critical bug to address. The screenshot provided clearly illustrates the duplicated character entries, making the problem immediately apparent. This kind of visual evidence is invaluable when trying to pinpoint the root cause of a bug. The consistency of the issue across different environments suggests that it might be tied to how Foundry VTT handles different initiative input methods simultaneously. Perhaps there's an internal conflict in the way manual entries and dice rolls are processed and added to the combat tracker.

Here are the versions where this bug has been observed:

• Module Version: 2.0.0
• Foundry Version: 13.347
• System Version: DnD 5e 5.0.3

Knowing these versions helps developers narrow down the scope of the bug and identify any recent changes that might have introduced it. If you're experiencing this issue, providing your specific version information can significantly aid in the debugging process. Now, let's move on to the feature request that's closely tied to this bug.

Feature Request: Enhancing Manual Initiative Entry

The second part of this discussion revolves around a feature request to improve the manual initiative entry system in Foundry VTT. Currently, when a player enters their initiative value manually, the system doesn't automatically add their Dexterity (Dex) modifier, nor does it provide a field for the player to manually input this modifier. This can be a bit of a hassle, as players need to calculate and add their Dex modifier separately, which isn’t very user-friendly. We all love a streamlined process, right?

This feature request essentially boils down to two potential solutions: either the system should automatically add the character's Dex modifier to the manually entered initiative value, or it should provide an additional field where players can manually enter the modifier themselves. Both options would be a significant improvement over the current system. Imagine the ease of just typing in your base initiative and having the system automatically calculate the final value. It would save time and reduce the chances of human error.

From a user experience perspective, this enhancement would make manual initiative entry much more intuitive and efficient. It aligns with the goal of minimizing manual calculations and letting the VTT handle the nitty-gritty details. This is especially important in fast-paced combat situations where every second counts. The ability to quickly and accurately set initiative is crucial for maintaining the flow of the game. Moreover, this feature request ties directly into the bug we discussed earlier. If manual initiative entry is clunky and prone to errors, players might be more inclined to roll for initiative, potentially triggering the duplicate character bug. By improving the manual entry process, we might indirectly reduce the occurrence of the bug itself.

There are several ways this feature could be implemented. One approach would be to add a checkbox or toggle that allows players to choose whether or not to include their Dex modifier. This would provide flexibility for different game systems or house rules that might not use Dex for initiative. Another option would be to automatically include the Dex modifier by default, with a setting to disable this behavior if needed. The key is to make the feature customizable enough to accommodate various playstyles while still providing a streamlined experience for the majority of users.

Steps to Reproduce the Bug: A Practical Guide

For those of you who want to try and reproduce the bug, here’s a step-by-step guide:

1. Have one player manually enter their initiative value without rolling.
2. Have another player roll for their initiative.
3. Check the combat tracker – you should see two entries for the character who rolled for initiative.

This simple test can help confirm whether you’re experiencing the same issue and provide valuable information for developers. Reproducing the bug consistently is a crucial step in the debugging process. It allows developers to observe the behavior firsthand and identify the conditions that trigger it. The more people who can reproduce the bug, the better the chances of finding a solution quickly.

This also highlights the importance of clear and concise steps to reproduce a bug when reporting it. The more detailed and accurate the steps, the easier it is for developers to replicate the issue and understand its context. Including specific examples and scenarios can further enhance the clarity of the bug report. In this case, the steps provided are straightforward and easy to follow, making it simple for anyone to test the bug.

Screenshots: Visual Proof of the Issue

The user, strongpauly, was kind enough to provide a screenshot that clearly demonstrates the bug. Visual evidence like this is incredibly helpful because it leaves no room for ambiguity. A picture is worth a thousand words, as they say! The screenshot shows the combat encounter tab with duplicate character entries, making the issue immediately apparent.

Screenshots are a valuable tool in bug reporting because they capture the exact state of the system at the time the bug occurred. This includes not only the visual appearance of the issue but also any relevant information displayed on the screen. In this case, the screenshot shows the character names, initiative values, and any other relevant details in the combat tracker. This kind of information can be crucial for diagnosing the root cause of the bug.

Moreover, screenshots can help developers understand the user's perspective and the impact of the bug on their gameplay experience. Seeing the duplicated characters in the combat tracker firsthand conveys the frustration and confusion that the user might be feeling. This empathy can motivate developers to prioritize the bug fix and ensure a smooth gaming experience for all users. In addition to screenshots, screen recordings or videos can be even more helpful in capturing dynamic issues or complex interactions. These visual aids provide a comprehensive view of the bug in action and can significantly speed up the debugging process.

Versions: Pinpointing the Scope of the Issue

Knowing the specific versions of Foundry VTT, the system (DnD 5e), and any relevant modules is crucial for troubleshooting. Here are the versions where this issue was observed:

• OS: Windows 10 & 11
• Browsers: Chrome, Edge, and Firefox
• Module Version: 2.0.0
• Foundry Version: 13.347
• System Version: DnD 5e 5.0.3

This information helps developers narrow down the scope of the bug and identify any recent changes that might have introduced it. It also allows them to test the bug in a similar environment to the user, increasing the chances of reproducing and fixing it. Version information is particularly important when dealing with software that undergoes frequent updates and changes. Each new version can introduce new features, bug fixes, or even new bugs. By knowing the exact version in which a bug occurs, developers can focus their efforts on the specific codebase that is causing the issue.

Furthermore, version information can help identify patterns or trends in bug reports. If a particular bug is consistently reported in a specific version, it suggests that the bug is likely tied to that version's codebase. This allows developers to prioritize bug fixes based on their impact and frequency. In this case, the consistent occurrence of the bug across different operating systems and browsers suggests that it might be a core issue within Foundry VTT or the DnD 5e system, rather than a platform-specific problem.

Conclusion: Let's Get This Fixed!

This initiative bug and feature request highlight some important aspects of using Foundry VTT. The duplicate character bug is definitely a pain point, and the feature request to enhance manual initiative entry would be a welcome improvement. By providing detailed reports, screenshots, and version information, users like strongpauly are helping the Foundry VTT community become even better. Let's hope the developers can squash this bug and implement the feature request soon! In the meantime, keep those dice rolling (or manually entering!), and happy gaming, folks!