Start with the first visible error rather than changing multiple files. Confirm the entry HTML exists, then verify that the referenced script and stylesheet paths are correct.
Missing styles or images
A filename case mismatch can work on one computer and fail on case-sensitive hosting. Check the exact asset name and the path used by the page.
Practical check
Keep the process small and testable. Make one meaningful change at a time, confirm the result, and preserve enough context to undo it if needed.
Interactive tools not responding
Open the browser console and note the first JavaScript error. A single missing dependency or renamed file can stop later scripts from executing.
What to avoid
Avoid mixing advice from unrelated builds as if every copy behaves identically. Version, file structure, enabled data and hosting method can all change the correct next step.
Stale content after replacement
Browsers can keep cached assets. After making a safe backup and replacing files, clear the cached site data for that origin and reload the page.
Summary checklist
- Work from a clear reference goal.
- Keep source and version context visible.
- Preserve a known-good local backup.
- Test paths and browser behavior before making broad changes.
For a wider overview, return to the 5etools features section or open the complete guide library.