10-26-2003, 02:03 AM
"I got the no-No-Glo version, and it and No-Glo have tons of conflicts..."
"I'm trying to merge Spell Cost Reduction (linked to earlier in this thread) and getting conflicts with wakim's balance plugin. The entries are identical, except for three lines (using the first as example):
BSND poison bolt Ascii 12
HSND poison hit Ascii 11
ASND poison area Ascii 12"
The conflict between WGI and many No-Glo style plugins is that the way most No-Glos work is by changing the color of the Saran-Wrap shimmer to black, ergo it doesn't shimmer. The conflict is that the shimmer color data is stored in the same place as the spell data, so No-Glos and WGI don't get along because WGI changes spell casting cost and No-Glos change the color but both changes share a common err... location, I think it would be appropriately called (if you look at how TESCS manages spell data these words may be more illuminating). Grumblepunk (if I correctly recall his Morrowind forum name) incorporated the black spell shimmer color into WGI, to eliminate the conflict you are experiencing (so that the color changes didn't overwrite the spell changes, or vice versa), and he put out WGI with No-Glo, but I strongly suspect that he had Tribunal installed when he did so because there is no compelling reason for WGI to otherwise be dependent on Tribunal. If you wish, try a glow reducer instead of a No-Glo, as all glow reducers I am aware of are compatible with WGI (since they change the shimmer intensity graphically (through textures or meshes or somesuch thing) rather than alter the raw spell color data), otherwise ya can always set the color of each spell effect to black by hand... As for the Ascii 11s and 12s, I have no idea what that means. One last word on the enchanted item shimmer: considering how egregious the possible abuses of enchanted items are in Morrowind you may wish to leave the objectionable appearing shimmer since it is the only rein on an otherwise obstinate horse.
Mod conflicts, by the way, are generally innocuous for a user, it just means that some mod is changing something that someother mod is also changing - the mod with the most recent file date wins and the older mod gets its changes disregarded. Good luck to ya.
"I'm trying to merge Spell Cost Reduction (linked to earlier in this thread) and getting conflicts with wakim's balance plugin. The entries are identical, except for three lines (using the first as example):
BSND poison bolt Ascii 12
HSND poison hit Ascii 11
ASND poison area Ascii 12"
The conflict between WGI and many No-Glo style plugins is that the way most No-Glos work is by changing the color of the Saran-Wrap shimmer to black, ergo it doesn't shimmer. The conflict is that the shimmer color data is stored in the same place as the spell data, so No-Glos and WGI don't get along because WGI changes spell casting cost and No-Glos change the color but both changes share a common err... location, I think it would be appropriately called (if you look at how TESCS manages spell data these words may be more illuminating). Grumblepunk (if I correctly recall his Morrowind forum name) incorporated the black spell shimmer color into WGI, to eliminate the conflict you are experiencing (so that the color changes didn't overwrite the spell changes, or vice versa), and he put out WGI with No-Glo, but I strongly suspect that he had Tribunal installed when he did so because there is no compelling reason for WGI to otherwise be dependent on Tribunal. If you wish, try a glow reducer instead of a No-Glo, as all glow reducers I am aware of are compatible with WGI (since they change the shimmer intensity graphically (through textures or meshes or somesuch thing) rather than alter the raw spell color data), otherwise ya can always set the color of each spell effect to black by hand... As for the Ascii 11s and 12s, I have no idea what that means. One last word on the enchanted item shimmer: considering how egregious the possible abuses of enchanted items are in Morrowind you may wish to leave the objectionable appearing shimmer since it is the only rein on an otherwise obstinate horse.
Mod conflicts, by the way, are generally innocuous for a user, it just means that some mod is changing something that someother mod is also changing - the mod with the most recent file date wins and the older mod gets its changes disregarded. Good luck to ya.