显示页面过去修订反向链接回到顶部 本页面只读。您可以查看源文件,但不能更改它。如果您觉得这是系统错误,请联系管理员。 --- redirect_from: "/How-to-spot-db-struct-diff-commits" --- <!DOCTYPE markdown> # How to spot DB struct diff commits **1)** Clone a [3.3.5 TrinityCore](https://github.com/TrinityCore/TrinityCore/tree/3.3.5) and open it with [Visual Studio Code](https://code.visualstudio.com/) or any other IDE that has **annotate** feature (e.g. IntellIJ and similar). If using Visual Studio Code, you can install the [Annotator](https://github.com/ryu1kn/vscode-annotator) plugin. **2)** Start from a diff, that can be any of [those](https://github.com/azerothcore/azerothcore-wotlk/milestone/3)/ For example:  **3)** Select the name of a changed field and copy it, for example `BaseAttackTime` and look for it in Visual Studio Code **4)** Scroll until you find the file that changes it, for example:  **5)** Press CTRL+SHIFT+P (or CMD+SHIFT+P if macOS) and type Annotator  **6)** Choose "Annotate the current file...", it will open something like this:  **7)** Go with the mouse over the line of the change that you want to spot the commit of  **8)** Copy the commit hash and paste on: https://github.com/TrinityCore/TrinityCore/commit/PASTE-THE-COMMIT-HASH-HERE that will be the commit you were looking for. **IMPORTANT**: it's also useful to check the file(s) that were modified on the [latest revision](https://github.com/TrinityCore/TrinityCore/tree/3.3.5) because they could have been modified in newer commits. docs-en/how-to-spot-db-struct-diff-commits.md.txt 最后更改: 2024/03/15 19:08由 127.0.0.1