EQ2Extreme with Exhume : EverQuest 2 Premium Discussions - Page 5

Hey boxy, what OS and have you patched recently? I wonder if a MS patch has updated the runtime files.

At what point does it freeze? Which splash screens are visible, etc...

I use XP on all my systems. Everything was working at one point and I even had the bots working for a while. I just tested again and for some reason it started working and I didn't do anything different although Exhume did take a really long time to let me log in. I'll keep you posted if it starts acting up again.

Thx

Is there an issue this AM with this app? As of this morning- doesn't seem to work any longer... When you do "start" with or without debugging- nothing happens....literally nothing. When starting Extreme- it does do the splash screen and you get to login....but can't run any programs.

I know there was a small EQ update today...did that affect things? ...and any ETA when it will be repaired? This is a great tool, and I was really just start to get a good idea how to write useful utilities with it. Hope it's working again real soon.

Thanks!!

...and just a follow-up. I just tried Exhume itself and it appears to still work OK. ...looks like something just related to the service behind Extreme?

OK- my deepest apologies. Not sure what happened, but I reinstalled Extreme (even though nothing changed with the version) and that seems to have fixed my issue. Guess something got corrupted? ....or maybe someone can tell me what might have been the issue (and how I caused it) so I can avoid it in th future. =) Again- well done with this.

Thanks!!.... and sorry again. Next time I will exhaust ALL my options before jumping to conclusions.

No prob dirdle. That happens when EQ2Extreme can't create the service object. I need to put in a message when it fails, but I've been lazy lately

Update posted for GU39

Still not finding target for me (testing with EQ2Extreme.vbs) ... nor picking up 'object.IsAttacking()' in eXbot. Appears that I have the latest EQ2ServiceHelper.dll ...

Should be fixed now lordbeowulf

Awesome, thanks Gheezer. Didn't realize how hooked I was on this thing until I had to go a day without it! I think I was sweating! =D

Ok, running into an odd problem now. Something that was working perfectly prior to the update now has me totally perplexed. I was loading your DynamicDataItem for group effects into an array and making a comparison ... like this:



Then using this comparison to execute my cure effects routine:



Prior to the update, if there was no effect active, this comparison ( oEffect(xCount,1).Value > 0 ) returned false ... but now it appears that when the *.Value returns empty, this comparison is true?

Any changes to how you polled for that data? (or stored it, or return it)?? Any ideas at all?!?! heh ... I'm stumped!?!

PS EDIT: I recall that the value used to return '0' (zero) if there were no effects active. I just wrote some test code and it now appears to return "" (empty string) when there are no effects. Was this 'feature' intentional (i.e. do I need to change my code to compensate)?

Yeah I changed the code so that now if an item is invalid it will still show but will be empty or false depending on the data type. The isvalid check must be catching the effects too.

The DynamicData code is still a work in progress and I still have at least one change planned. Each data item may have more than one value and I am planning on returning more data for each item.

Some of the possible data returned could be tooltip text, text, color, boolean, long, progress%, etc...

Once I have it all worked out I will let everyone know the new properties.

I have tried each of the following:



... combined with the comparison:



(I also tried Cint(oEffect(x,1).Value) ... causes error if there is no effect.)

All of these appear to always return TRUE even though there may be no actual effect in there (when I display the .Value in a string between two colons, it is zero spaces).

I find it odd that if I add up all the players' effect values:



... that the total of tmpflag will not be greater than zero if no one has effects, and will be greater than zero if someone has effects. In other words, this part still works properly, so it is still finding accurate and appropriate data in there. Ergo I don't understand why none of my efforts to ferrett out a valid value have worked.

Well, last release this dynamicdataitem.value returned the value 'zero' and everything worked great. Can you revert back to having it return the value 'zero'? Or do you have other suggestions?

Thanks Gheez!!

The number returned for effects isn't always a positive number. I wouldn't trust it for any calculations, but rather test for a non-blank value:



The problem is trying to make all the datatypes fit into one value field. I should have an update out tomorrow that will make more fields available. So far text, tooltip, boolean, long, progress, color, and event seem to be working.

Update posted to GForge. Developers of compiled applications will need to recompile.

Notes to developers:
I also included TestEQ2Extreme.exe which will allow you to examine the new DynamicData available. The DynamicData tab will poll and display all variables and values twice per second. Values that have changed since the last time the "Refresh" button was hit will be red, making it much easier to determine what changes each action produces.

New DynamicDataItem Properties: