Hello

Something I have not been sure about.. Now that I have used the 'move worldspace' command on my world to get the Vwd objects to show right, is my .esp all good to go for other users? Or do they need to have Gecko and call it as well on their end?

I appreciate any info on this, I really dont know.

Well, if you've used Gecko on the .ESP, then it should work no matter who you give it to - Gecko or not. What it *should* do is alter the .ESP itself, not create a file to tell the .ESP what to do under these circumstances (I don't even know if that's possible).
If you don't save or alter the .ESP though, they might need Gecko. It'd be a pretty stupid program if they did though (although it does lots and lots of useful stuff!) - I've never used it myself. I'm more inclined to say it'll alter your .ESP though, so you'll be fine.
Good thing I'm not a betting man, though...

Thanks for the response.

I have only been assuming nothing would be needed apart from just my .esp.. But I have ended up with various 'index' files created by Gecko over time from doing a few move Worldspace commands here and there.. I have just gone ahead and deleted them though, and the Vwd still works fine.

Guess the only main reason I ask is that I was under the assumption the commands messes with the index load order for the Oblivion.esm.. but I am hoping that this information is still contained in the .esp ?

Again, just asking to be safe.. A pity it would be to release my mod and find out that 300 people had their gameplay experience diminished because the Vwd objects weren't showing up.

Sounds like a really complicated function! I think indexes are just so you can log changes, but I could be wrong.
I'd be happy to test it, and I've not got Gecko installed on this machine. Your call!

It changes the mod index of the worldspace in the esp to 00 (same as Oblivion.esm). It doesn't change anything in Oblivion.esm itself. The user doesn't need to do anything.

The gecko team could probably explain it better, but that is kinda what happens. Move worldspaces tricks the game to acknowledge that worldspace as being part of the 00 index instead of the 01 or higher index based on where it is loaded. This is all saved within the .esp. The reason why this is needed is because the index that the worldspace is registered to MUST be the same as what the LOD files were created for. Before moving worldspaces was worked out, LOD meshes for new worldspaces could not be linked up with that worldspace without requiring a specific loading position for that mod.

I thank you for the offer Will be advertising for beta testers in the next few days on the mods forums for BladeSong, if your interested feel free to drop in there once the thread is up.




Perfect. Thanks Phitt. I really wasnt sure about the whole deal, and was concerned about not having something avaliable that was needed for users to properly play the mod.



Gotcha. I appreciate the info. Glad to see things were fixed, and at least it is reasonably doable now.

Thanks everyone for the responses. :tops: