I've noticed some of my scripts running kinda slow lately and I think it's because I have too much going on at once.  For example I typically run a looter, pvm script, and pvp script.  The looter is running just 100lpc, but the pvm/pvp ones are running often around 1000lpc, but switch back and forth from low to high, journal scanning, pixel scanning etc.

Before on OSI shard I did run a looter, but never a pvp script, and things ran fine.  Typically scan times were low from 25-100ms complete cycles on everything.  Since I wrote the pvp one I noticed the cycle times have been getting extremely high, around 500-1000ms which isn't acceptable haha.

I rethought some of the coding for some pixel scanning, and came up with some options to simplify things, which will hopefully speed things up.  But I'm wondering if i'll be still encountering problems because of all the journal scanning.

Also each script does have hotkeys associated with them, which make toggling them a pain when things kinda run slow!

I'm wondering if I should remove a lot of the journal/pixel scanning out of the individual scripts, and incorporate them into like a master control type script?  One that handles all the journal crap, pixel stuff, and hotkey things and kinda queues them up for the other scripts to use?  I just already have enough tabs open and don't want more, especially if it wont solve anything!

Another thing is I'd like to run 5 clients at once, and I'm having problems with the two... lol...  Any ideas?

Used to be able to cut non cutable items (that couldnt cut with scissors) in salvage bags.

If it dont work, try putting smith items in there too, maybe their code is a bit screwed up between smith/tailor salvage, smith only salvage, tailor only salvage...  don't see why it would be but worth a shot.

is it possible they just have their screen resized larger?

tried rift for ~2 hours and uninstalled it.  hated it.

froze again.

I'm starting to think its a display driver issue.

Right before I finally got it to shut down it poped up with error (posted this previously) "The igzprd32 display driver has stopped working normally.  Save your work and reboot the system to restore full display functionally.  The next time you reboot the machine a dialog will be displayed giving you a chance to upload data about this failure to Microsoft.".

I'm pretty sure I have the correct display drivers.  But they make it so confusing.  I guess I'll redownload drivers and try again.

this is STILL happening...

can't figure it out.  it's happened about 20 times today which is insane.  I took out and reput in the motherboard.  Same with memory.  Tried different memory.  Removed everything but the primary harddrive so nothing else is running off the powersupply.  I unplugged, replugged everything, completely disassembled/reassembled the whole thing

any more ideas?  i'm about to trash this one.

Another good dirty trick I use to get past certain things is paperdoll poping.  For a lot of moveable items if you paperdoll pop while walking/running the tile before, itll bounce you right over it.  I used this trick to break through a barrier some people placed to the upstairs of a public auction house.  I've also used this trick multiple times during EM events to get past thier "blockades", to run far ahead to look for things to take!  Be careful though, I was jailed for it previously but only received a warning.  Careful though, it can get you stuck in some nasty locations...  My friend hit it by accident while running and fell through some steps in despise during a big fight and couldn't get out in time and got statted lol.

In my script I do a few extra arguments for certain findtypes (humans/elves i do both checks, for possible pet #FINDTYPES I just check the #FINDREP) for #FINDREP and secondly a sub that checks the distance between 1; players current position, 2; locations that the #FINDTYPE found exists as a 'monster' (ie;  Abyss Wyvern Spawn for elves, Champion Alters (Nierra) female human && findrep = murderer, off the top of my head, I'm sure there's others).  You can also do an event property on questionable targets, but I find event property unreliable, and slow which is why I check the players locations.