Ogre export not working

[Jazcat]

Just signed up for OgreBot, followed all the instructions carefully but when doing an ability export as recommended it says the below. I've closed and restarted isxeq2/isxogre and innerspace. I've ran an SVN update as well.

This is using "Ogre export"

Loading Ability Export...
Script file 'eq2ogrebot/abilityexport' not found
RunScript 'eq2ogrebot/abilityexport' failed

Just tried to launch ogre craft and am getting this error as well:

Loading OgreCraft Lite (Embedded)...
Buffer:OgreCraft(4): Could not locate file E:/Users/FolderName/Utils/InnerSpace/Scripts/OgreCommon/Object_LavishSettings.inc for preprocessing
Preprocessing failed on Buffer:OgreCraft
Loading OgreCraft (Embedded)...
Buffer:OgreCraftUI(4): Could not locate file E:/Users/FolderName/Utils/InnerSpace/Scripts/OgreCommon/Object_LavishSettings.inc for preprocessing
Preprocessing failed on Buffer:OgreCraftUI

 

[Cheesy]

I'd suggest taking a look at http://eq2.ogregaming.com/wiki/Help:Repatch as it sounds like you need a few files which aren't there.

 

[Jazcat]

Thank you for your advice, the link given recommends running "ISXOgre:Repatch[1]" command, doing that returns this error:

Error:No such 'ogre' method 'Repatch' @ISXOgre:Repatch[1]
Error parsing data sequence ''

 

[Kannkor]

I'd suggest taking a look at http://eq2.ogregaming.com/wiki/Help:Repatch as it sounds like you need a few files which aren't there.

oops. That page hasn't been updated. With the new patcher, it always updates the files it needs.

jazcat - Open ONE eq2 session, then look in the console, I assume the patcher is failing, and isn't downloading the files you need. If there is an error message I need it.

 

[Jazcat]

oops. That page hasn't been updated. With the new patcher, it always updates the files it needs.

jazcat - Open ONE eq2 session, then look in the console, I assume the patcher is failing, and isn't downloading the files you need. If there is an error message I need it.

Hello Kannkor, yes I didn't notice much happening on first load of the ISXOgre extension, your guide mentions 200+ files to be downloaded. All I see in the console is this:

"EverQuest 2" extension for Inner Space, ISXEQ2 v20140514.0001, is now ready for use.
ISXOgre loading... Version information: Build date: 2014.03.24, Patch Version: 251
ISXOgre: Checking subscription... please wait.
ISXOgre: Debug: Waiting for connection be become active...
ISXOgre Notice: Subscription expiry date: Aug 15, 2014
ISXOgre: Authentication completed.
ISXOgre: OgreBot access level increased to client.
ISXOgre: OgreCraft access level increased to client.
ISXOgre enabled. Version information: Build date: 2014.03.24, Patch Version: 251

Pretty sure you're both right in the patcher not pulling down the files automatically.

 

[Jazcat]

Seems executing "ISXOgreatch" did the trick, unable to test the bot yet but I saw the patcher download the scripts.

Worth noting though that the autopatcher did not work on a fresh install, I'm also doubting it's going to work at all with the scripts, maybe will only work for the .dll file. I may have to keep running that command periodically to get updates?

 

[axus]

I was having this problem too. It looks like you have your inner space on E: drive and Ogre downloads everything to C: I would try doing fresh install on innerspace on your C drive and see if that fixes it. There may already be a directory there too.

 

[Kannkor]

I was having this problem too. It looks like you have your inner space on E: drive and Ogre downloads everything to C: I would try doing fresh install on innerspace on your C drive and see if that fixes it. There may already be a directory there too.

Good call. The patcher actually uses the innerspace registry entry to determine where to check the files and patch too.

So if you install innerspace, then decide to simply "copy" it to a different location, the patcher will still patch to the original installed location. As mentioned, uninstalling innerspace, and reinstalling to the location you will be using, is probably the best scenario.

 

[Jazcat]

Good call. The patcher actually uses the innerspace registry entry to determine where to check the files and patch too.

So if you install innerspace, then decide to simply "copy" it to a different location, the patcher will still patch to the original installed location. As mentioned, uninstalling innerspace, and reinstalling to the location you will be using, is probably the best scenario.

It wasn't copied it was installed to that location, the registry entry exists and is correct. I should probably mention again that at no point the autopatcher kicked in after fresh install, no scripts were downloaded. Not even to a wrong location.

 

[Kannkor]

Seems executing "ISXOgreatch" did the trick

If that made it patch, then it means patching is probably disabled.

One thing you can try, is make sure you know your username and password for Ogre (it's in the original email).

Then close down all EQ2 sessions, then navigate and backup (then delete/rename) the file:
scripts/extensions/isxogre.xml

Then load 1 eq2 session. Put in your username and password. It won't patch anything (because it's already up to date). But if you have the flag set to not patch at all, that should remove it.

 

[Jazcat]

If that made it patch, then it means patching is probably disabled.

One thing you can try, is make sure you know your username and password for Ogre (it's in the original email).

Then close down all EQ2 sessions, then navigate and backup (then delete/rename) the file:
scripts/extensions/isxogre.xml

Then load 1 eq2 session. Put in your username and password. It won't patch anything (because it's already up to date). But if you have the flag set to not patch at all, that should remove it.

Thanks Kannkor, the isxogre.xml I noted had "AlwaysPatch">FALSE<, after deleting and re-authenticating I made sure to tick on alwayspatch. By default it was unchecked.

 

[Kannkor]

Thanks Kannkor, the isxogre.xml I noted had "AlwaysPatch">FALSE<, after deleting and re-authenticating I made sure to tick on alwayspatch. By default it was unchecked.

That's fine to be unchecked. That just means it only patches once when you load IS1. If you unload and reload the extension (without closing the session down) it doesn't patch again when you reload.