Thanks! For future reference, under the terms of the Mozilla Public License which xEdit is published under, for a fork like you are maintaining, you must publish your source code alongside your link to the xEdit source code, always. (Since you're not incorporating xEdit's source code into a larger work.) You've probably already heard this, but I think you may as well make a public fork on GitHub. It'll probably be the easiest way of keeping track of both versions. It might also help clarify why people need to download your specific fork of xEdit for terrain LOD generation if the relationship between the codebases is more visible.