Kannkor
Ogre
I just patched out thousands of lines of code changes to the core of Ogrebot.
If anything isn't working properly, do this first. Close everything down, then load it back up. What happens a lot, and especially with large patches, is IS1 (your first session you load) is patching, and the rest of your sessions just use the old patch. So there is a sync issue. So by reloading, everyone then uses the new one.
If that still didn't work, then ask for help and post exactly what isn't working.
In a perfect world, everything will continue to work and no one will notice anything.
That's it.. now if you're curious what changed... Here is a brief explanation. It's a little technical, and not required reading at all.
When you load a game with innerspace, it gets assigned a name. Such as "IS1" and "IS2". For most people, they play 1 game at a time, and play up to 1 group at a time. So when you press an MCP button (for example), it just tells all the names (IS1, IS2, etc) to do whatever the MCP button says.
This works great... ... Until you hit one of the following:
You load more than 1 game. Such as Everquest1 and Everquest2, or Everquest2 and Eve, (etc etc).
You load more than 1 group in a game. Lets say you want to do TWO duo zones at the same time. So it might be IS1+IS2 doing a zone, and IS3+IS4 doing a zone. What happens if you press a button on MCP? All 4 listen!
This isn't what you want, you want IS1 and IS2 to listen to some, and IS3 and IS4 to listen to some.
This patch solved all of these problems. It's called Relay Groups. A simple grouping system that is built into innerspace, that Ogre now utilizes.
By default, if you are in Everquest2 and using Ogre, it will only send commands to other Everquest2 sessions using Ogre.
We then extend this further, and (only if you want), you can actually set these groups. So you can make your IS1 and IS2 be in "G1", then you can say, any commands sent from these sessions, will only go to G1. You can then do the same thing for IS3 and IS4 for "G2".
That is the bulk of it! For the few whom will use custom relay groups, see the revision history in the wiki for how to use it.
If anything isn't working properly, do this first. Close everything down, then load it back up. What happens a lot, and especially with large patches, is IS1 (your first session you load) is patching, and the rest of your sessions just use the old patch. So there is a sync issue. So by reloading, everyone then uses the new one.
If that still didn't work, then ask for help and post exactly what isn't working.
In a perfect world, everything will continue to work and no one will notice anything.
That's it.. now if you're curious what changed... Here is a brief explanation. It's a little technical, and not required reading at all.
When you load a game with innerspace, it gets assigned a name. Such as "IS1" and "IS2". For most people, they play 1 game at a time, and play up to 1 group at a time. So when you press an MCP button (for example), it just tells all the names (IS1, IS2, etc) to do whatever the MCP button says.
This works great... ... Until you hit one of the following:
You load more than 1 game. Such as Everquest1 and Everquest2, or Everquest2 and Eve, (etc etc).
You load more than 1 group in a game. Lets say you want to do TWO duo zones at the same time. So it might be IS1+IS2 doing a zone, and IS3+IS4 doing a zone. What happens if you press a button on MCP? All 4 listen!
This isn't what you want, you want IS1 and IS2 to listen to some, and IS3 and IS4 to listen to some.
This patch solved all of these problems. It's called Relay Groups. A simple grouping system that is built into innerspace, that Ogre now utilizes.
By default, if you are in Everquest2 and using Ogre, it will only send commands to other Everquest2 sessions using Ogre.
We then extend this further, and (only if you want), you can actually set these groups. So you can make your IS1 and IS2 be in "G1", then you can say, any commands sent from these sessions, will only go to G1. You can then do the same thing for IS3 and IS4 for "G2".
That is the bulk of it! For the few whom will use custom relay groups, see the revision history in the wiki for how to use it.