I think that the wrong way, and we should first import creature_template_difficulty to avoid to move again creature_static_flags fields. I'm working on it, so for the moment I move this PR to draft.

What? No, 3.3.5 will never get creature_template_difficulty. creature_template is the final destination for static flags

What? No, 3.3.5 will never get creature_template_difficulty. creature_template is the final destination for static flags

My bad. With this discussion (#25626) I was thinking that what applied to retail with these static fields was true in the early versions of the game.

So I figured it would be easier to do things in order. Especially since I was looking at the differences in how Difficulty IDs are handled between the retail and WrW versions for the latest commit, with the individual override of the static flags.