Internet username spelling? Who cares.
Hitting sumbit button once? Preferred.

Positions can be changed to make it to "scale" but the fact that the text size is still the same, would make it not scale how you would really want it. I'm guessing that's what you mean.

2 fixes for last posted code... Fixed a typ-o on line 58 /if (!${Me.Pet.ID} { Should be: /if (!${Me.Pet.ID}[color=red])[/color] { Add: /varset BuffLine ${BuffLine.Right[-5]} to top of Event_Buffs sub. This is so it doesn't fine "2" in "MQ2" :roll: Code changes are applied to last...

nektulos forest?

Seems unlikely. No problems in any newer games/older games/any other games, applications, programs, ect. As said previosly, has to be a pretty long session, where I end up zoning probably over 20-30 times, before I get a CTD. I still need to run another RAM/CPU test. I'll take your advice though, an...

Thanks. I'll do try that one next.

I ran Prime95 for 11 hours, and got 0 errors/warnings.

I ran MemTest 3.5, a windows application, which ran for about 4-5 hours, and got up to like 1034% or something with 0 errors. I'll have to run some ones mentioned above though. The ones that you boot to I suppose. Hopefully can figure out something, but again, it's more of an uncommon annoyance than...

When I said "it seems to work that way", I mean that I've been using that way, and for a while.

I knew when the changes happened, and I implemented this change after that.
I'm using the code I posted, and it works fine.

Seems it can still be used that way, as I don't get any errors from it. I dunno if it's the same as .Stacks[0], but I'll see what differences happens when I experiment with it.

I Was aware of the change, just wansn't using it, as it didn't seem needed.

Yeah, I have all the hotfixes/drivers required. I may try a stress-test/memtest as you said, but I'm not too worried. I just wanted to rule out anything else first.

yes. AMD 64 X2 6000+ 2x 1GB Crucial Ballistix DDR2 800 I have the XP-released dualcore hotfix, the AMD drivers, and the AMD Dual-Core Optimizer. But like I said, the crash is somewhat uncommon, but after zoning so many times, it is bound to happen eventually. Not really a big problem. Only takes a m...

Here's a new crash log. Takes forever to produce it, seems kind of random. Again, happens on zoning. Following plugins loaded: [Plugins] mq2labels=mq2labels mq2itemdisplay=mq2itemdisplay mq2custombinds=mq2custombinds mq2hud=mq2hud mq2map=mq2map mq2chatwnd=mq2chatwnd mq2eqbugfix=mq2eqbugfix mq2cast=m...

I eventually scratched the method of constantly updating a list of what buffs don't stack. It was nice since it would replace buffs like Spirit of Eagle if you had Spirit of Wolf, but otherwise it was a big inconvenience. Here's my current source of code in which I just use the .Stacks check, and a ...

Hmm ok. I only ever get this crash, usually after I zone a bunch of times. I figured it was just EQ-related, but thought I would ask. I saved the crash info from what I posted above. Using the latest zip as always. Debugger view: [MQ2]MQ2Map::OnRemoveGroundItem(2) [MQ2]MQ2Map::OnRemoveGroundItem(3) ...

If eq crashes, and the debugger returns something related to eqgame.exe itself, that is just a general EQ-related crash, correct? For example: (7e4.cd4): Access violation - code c0000005 (first chance) First chance exceptions are reported before any exception handling. This exception may be expected...