[EQ1] Default Profile

My game is EQ, but I'm not sure that matters for this question. Sometimes I'll need to log in a character to trade items to SlotOne character. The person I need to log on is also always in slot 1 on every character set I have, so I load up the default profile to do my business and get it. Because I don't actually need to play the OtherSlotOne character, the in game interface layout, hot buttons, key maps, etc don't matter. BUT it would be brilliant if I could have the window controlled like the other windows. Specifically, I use stacked, no swapping, avoid taskbar. With IS default profile, there's a window title and it's not quite the right resolution for my default eqgame.ini so everything is all scrunched up. This still wouldn't bother me that much BUT it makes it very hard to click on things. The cursor's position on screen does not line up where the cursor is in game. I have to go "fishing" to find where the mouseover text will popup so I know when to click.

Thanks! (Disclaimer: I just woke up and I've only had one cup of coffee so any grammar/spelling errors are not my fault.)

[bob]

They are two separate applications. InnerSpace the script host and ISBoxer the [InnerSpace] scripts and configuration toolkit.

The problem is that the loading via the InnerSpace game/game profile just loads up under InnerSpace, whereas the ISBoxer Character Set/Slot runs the ISBoxer.iss, which is the ISBoxer script, and this script is what then loads up the game/game profile from InnerSpace, but also does a shedload of other fancy things, like window layouts, file virtualisation, keymaps, which are all configured in the ISBoxer toolkit (and sometimes the ISBoxerUI, which is also another script). You can do all the fancy stuff in your own InnerSpace script too because the script host supports those methods, but it would need to be in your own script.

I'm going to guess (because I really have NFI) that the internals of InnerSpace somewhere home everything that is loaded via ISBoxer (the script) under a group called "isboxer", much like the toolkit shows all your configuration under a root node (this is possibly just handled by script name I guess). So if you had your own script, which you by chance copied from the ISboxer scripts, you would still need to rename a few things along the way so the ISBoxer atoms/tlos etc and G7CustomBoxer atoms/tlos etc were different (not that I know how it all works but I'm pretty sure the TLO's might become problems if named the same) . Once you had it all working, then if your targets referred to "Window: All w/......" which to InnerSpace means All InnerSpace windows, it would in theory work.