no game configured

Hi,
So im having troubles exporting from my main pc and isboxer creating new wtf files.
http://prnt.sc/clfvj4
As you can see it says that there isn't any game configured in innerspace, but yet there is.. I need to export from my second pc in order to make any changes to isboxer or it wont work. Now that itself is not really an issue. But what is an issue, I believe because of this, isboxer or innerspace keeps creating new wtf files whenever I change the name of those, eventhough they are the same in isboxer as in the wow folder.
For example: config-Dreamwindow.WTF will turn into config-Dreamwindow-Icecrown.WTF, Icecrown being the realm name. I could just use the one with the realmname, but I believe Jamba uses that file and therefore can't detect my character, because the realmname is behind it.
http://prntscr.com/clg0l9

My isboxer setup:
http://www.filedropper.com/dqwewqe

Any help would be appreciated.

[bob]

My first suggestion is to make sure that the Inner Space folder is pointing correctly to the running installation of Inner Space (this only matters on the PC you are exporting from ISBoxer Toolkit). The Config-charname-icemane.wtf setting you are suggesting is not in your profile, although looking at the Battle.net values for the virtual files, it might have been, which seems more like you are running a different profile to what is configured/supplied. This would also explain the issue you are having with "No game configured". You can see where ISBoxer is pointing, by selecting the ISBoxer node in the top left of your profile.

The other thing of note, when exporting on multiple PC's, the Game and Game Profile names in Inner Space need to match on both PCs for the given characters. The installation of the games does not, it is purely the name of the Game and Game Profile (it is not case sensitive AFAIK), as displayed in Inner Space (or as displayed in the drop downs in ISBoxer for each Character). This is because if you configure your profile on a single PC, then you use the name of the game profile on the local PC. ISBoxer doesn't know the name of the game profiles on the other PC, (and you'd never select it if it did), so, when it comes to exporting and putting files in the right place, it is just easier to do it the other way, and make sure you have them named the same.

Thanks for your reply!

I did indeed change the virtual files in ISBoxer, but I had the exporting problem before I did that.
Anyways, a quick reinstall of ISBoxer on my main pc somehow fixed the exporting problem. But the problem with the jamba addon still exists. And I know the problem is because of the realm name, because its not on my second pc.
This is what happens when I invite my chars with jamba:
http://prntscr.com/clqba3

The chars being invited are on my second pc.
So the question is basically, how can I get rid of that realm name in the wtf files, if ISBoxer keeps remaking them?
As you could see, I tried deleting the realm name for the chars anywhere in ISBoxer (i'll try the battle.net stuff but that shouldnt matter as those files are not even being used in this version of wow), but also in my wow folder.

[bob]

The realm name in the name of the config-charname*.wtf files will make no difference at all to Jamba. The name is used purely by ISBoxer so when the game asks for the config.wtf, and the ISBoxer character in question has a virtual file entry which says config.wtf -> config-charname-realmname.wtf, then ISBoxer will replace it. The only place the virtual file names come from are the per character settings for the virtual file in question.

If the setting in ISBoxer does not match the file being created after you change the ISBoxer settings, then delete the files (or rename them), then that would indicate to me, that the profile Inner Space has is not the one you are exporting.

The only places that Jamba might get some names from would potentially be the ISBoxer Addon files, but this would only be the case if you had something incorrect with the game profiles and when you were exporting to Inner Space, ISBoxer was either 1. not updating the Addon files (which might happen if you have characters in 2 or more teams that are across 2 or more PC's), or 2. the game profile was pointing at a wow.exe (or variant) which was not the same folder as the one that is being launched (this would just be really weird and next to impossible as far as I can tell).

A final choice would be, the setting causing the issue is in the JAMBA team config, which is not really an ISBoxer type issue, and I know not how to fix that.

[MiRai]

If you're attempting to use an older version of JAMBA on the private server you're playing on, we cannot provide any support for that.