R.I.P v16. You HAVE TO UPGRADE TO V17 NOW!

[Kannkor]

Version 16 is about to die, permanently. Let me explain.

Last year, Innerspace went from ISXDK32 to ISXDK33. When this happened, it broke every single extension (they don't load at all). These ISXDK's happen only once every few years, unless there is a need. Currently, (with ISXDK33) Innerspace only supports 32bit games. Many new games coming out, are 64bit games only. This means they don't load with Innerspace. As you can imagine, that's an issue. Lax has been working hard to get 64bit support into Innerspace, but this means he has to push ISXDK34. Which yes, will completely break every single extension.


The plan is, to have ISXDK34 released before Diablo 3's new update, which I'm told is around a week. This means everyone will have to redownload ISXOgre (and ISXEQ2 and ISXBJ) manually. And there will only be 1 version of Ogrebot (v17).

I highly recommend you try to switch over sooner than later.

How to switch over, and to check if you're already running v17, the details can be found here: How to upgrade to V17.

Note: All new users for the past two months at least, have been put on v17.

 

[Kannkor]

Approximately 1 month after this 'forced update' to Version 17, I will be removing the unused tabs from the bot so they aren't taking up space anymore. (IE: CA/NamedCA/Priority/Buffs/Chains).

If someone really needs to see the information that was in them, that information will still be available by looking at the XML file in scripts/eq2ogrebot/save/EQ2Save_server_toonname.xml

This is merely to clean up the UI of old tabs.

 

[blackee]

Approximately 1 month after this 'forced update' to Version 17, I will be removing the unused tabs from the bot so they aren't taking up space anymore. (IE: CA/NamedCA/Priority/Buffs/Chains).

If someone really needs to see the information that was in them, that information will still be available by looking at the XML file in scripts/eq2ogrebot/save/EQ2Save_server_toonname.xml

This is merely to clean up the UI of old tabs.

Is there any chance of leaving the chain tabs? I am sure you have thought this all through, but the Chain tab helps with spells like; shock wave, stupefy, shock wave (Coercer). Also, I betrayed my ass'n to teh ranger due to the lack of chain tab support in 17.

Is there a feature I am missing to replicate the chain tab?

 

[Kannkor]

Is there any chance of leaving the chain tabs? I am sure you have thought this all through, but the Chain tab helps with spells like; shock wave, stupefy, shock wave (Coercer). Also, I betrayed my ass'n to teh ranger due to the lack of chain tab support in 17.

Is there a feature I am missing to replicate the chain tab?

The removing is simply visual, the tabs I listed do nothing at all right now.
At this moment there isn't chain tabs in v17. I haven't had time to decide what to do there.

If anyone is using v17, I'm not removing any functionality at all, merely removing the tabs that say "THIS TAB IS NO LONGER USED. USE CASTSTACK".

 

[blackee]

The removing is simply visual, the tabs I listed do nothing at all right now.
At this moment there isn't chain tabs in v17. I haven't had time to decide what to do there.

If anyone is using v17, I'm not removing any functionality at all, merely removing the tabs that say "THIS TAB IS NO LONGER USED. USE CASTSTACK".

I wasn't referring to the removal of the tabs within v17. I meant bringing the capability to utilize the Chain Tab within v17. This is a loss of capability from 16 to 17.

 

[Kannkor]

At this moment there isn't chain tabs in v17. I haven't had time to decide what to do there.

Is the response regarding Chain tabs at this time.

 

[blackee]

Is the response regarding Chain tabs at this time.

Sounds good. I read that and wanted to provide unsolicited feedback. We'll see what you decide.

 

[Kannkor]

Approximately 1 month after this 'forced update' to Version 17, I will be removing the unused tabs from the bot so they aren't taking up space anymore. (IE: CA/NamedCA/Priority/Buffs/Chains).

If someone really needs to see the information that was in them, that information will still be available by looking at the XML file in scripts/eq2ogrebot/save/EQ2Save_server_toonname.xml

This is merely to clean up the UI of old tabs.

This is your two week warning! The UI purge/clean up is underway!

 

[blackee]

This is your two week warning! The UI purge/clean up is underway!

I have been searching for any mention of you taking out the "@Group" entries within the "aliases" tab. Did you remove the support for this? If so, what is your suggestion for rezzing/healing group members? I am sure I am missing something, but I am not sure what it is...

Thanks.

 

[Kannkor]

I have been searching for any mention of you taking out the "@Group" entries within the "aliases" tab. Did you remove the support for this? If so, what is your suggestion for rezzing/healing group members? I am sure I am missing something, but I am not sure what it is...

Thanks.

uhh.. what?

@Group has never been on the alias tab... @Group is internal to the bot, and isn't 'defined' anywhere. That goes for all aliases that have '@' in front of them. Any custom aliases start with '*'.

If @Group isn't showing up some where, tell me exactly how to reproduce it. That shouldn't/isn't changing.

 

[blackee]

uhh.. what?

@Group has never been on the alias tab... @Group is internal to the bot, and isn't 'defined' anywhere. That goes for all aliases that have '@' in front of them. Any custom aliases start with '*'.

If @Group isn't showing up some where, tell me exactly how to reproduce it. That shouldn't/isn't changing.

Ok, it might not have been in the aliases tab.

But, all of the "@Group" and "@Raid" rezzes and heals put my guys into a spiral. The on game message spams, "Target is not dead". I came back from a 10-day break to find all of my toons who use @Group in the Cast Stack "broken" and I had to run a new Ogre Export... Nothing else changed.

Console Spam says:
"There are no [0] to target in this area.
OgreBotEcho(20:17:38): CastingExtras: Entering f_ Casting Routine-- Ability Reincarnation ID: 224171276 ) -- TargetPerson or 0 ) -- NPCTargetRequired: FALSE -- TimeToWaitForCastTOStart:1000 -- bCastableWhileStunned: FALSE called from: Cast Stack: Res -> Group -> @Group
OgreBotEcho(20:17:38): Casting -> Ability: Reincarnation ID: 224171276 -- With :Use -- called from: Cast Stack: Res -> Group -> @Group"

 

[Kannkor]

Ok, it might not have been in the aliases tab.

But, all of the "@Group" and "@Raid" rezzes and heals put my guys into a spiral. The on game message spams, "Target is not dead". I came back from a 10-day break to find all of my toons who use @Group in the Cast Stack "broken" and I had to run a new Ogre Export... Nothing else changed.

Console Spam says:
"There are no [0] to target in this area.
OgreBotEcho(20:17:38): CastingExtras: Entering f_ Casting Routine-- Ability Reincarnation ID: 224171276 ) -- TargetPerson or 0 ) -- NPCTargetRequired: FALSE -- TimeToWaitForCastTOStart:1000 -- bCastableWhileStunned: FALSE called from: Cast Stack: Res -> Group -> @Group
OgreBotEcho(20:17:38): Casting -> Ability: Reincarnation ID: 224171276 -- With :Use -- called from: Cast Stack: Res -> Group -> @Group"

Class and how exactly is it in the caststack?

Also, was someone dead? and do you have AutoTarget checked?

 

[blackee]

Class and how exactly is it in the caststack?

Also, was someone dead? and do you have AutoTarget checked?

this is happening on both my dirge ("Elegy at Death's Door") and warden. Also, it is happening on all of their "@group" entries.

No one is dead.

Cast Stack (Color: Purple): Reincarnation | Target = @Group | Type = Res