I have a loop to move towards an item until it's in range and used an if #findcnt <> -1 to loop again... and when it finds nothing near me the #findcnt goes to -1 but an itemtype of YM is somehow found(#findcnt remains -1) and the loop does not recognize the false condition and continues moving towards....


wait for it


a chest at luna bank even if I'm in Skara Brae! Literally, the character runs towards Luna despite that being a different subserver. I checked the itemID it was looking for(despite a #findcnt of -1) and it's the chest beside the provisioner in Luna which shouldn't have an itemtype of YM to begin with. I decided that using a #findcnt check as a condition was probably not a good idea, lol.

This was just for testing purposes, I don't use it in any script.

The roof is hands down the best place, but it's not the only place. I used to get a few fishing up the big baddie with ancient nets but now it takes 10-15 kills to get 1 legendary and that's just not practical as a farming source. I also got some in Shame a long time ago now but again, none in a long while. They keep tinkering with the loot table, it's sometimes fun just to go back and re-try old stomping grounds too.

Sampires used to be my favorite but of late I find myself on a necro/mage with either weaving or mysticism to plow through the early spawn more quickly. The game isn't always friendly to melee when it comes to bosses.

Working on something way past my bedtime again...

I am performing a finditem and iterating through the results with a #findindex but during a couple of tests I realized there is a delay before doing anything if the #findcnt of my search has found too many items. That's expected, the #findindex is needing to process what was found one by one. It dawned on me however that there is no need to iterate through EVERY result, by limiting it to the first 50 or so I could eliminate the initial pause before the script does something. (well, not eliminate, just break it up so as not to procrastinate so long at the start!)

If finditem finds 1000 results how do I best limit it to processing only the first 50 via a #findindex loop? I do use continue as a filter but the sheer volume sometimes leads to prolonged inaction. I also wouldn't need to tell it to check the next 50 and so on afterwards until the 1000 are processed because when it's done acting on the first 50 it could be run again. Call it chunking if you will, and 50 is an arbitrary number, I'd fine tune it based on results.

Is there a command for limiting how many of the finditem results will be processed with #findindex if the #findcnt is exceedingly high, say 1000+ ?

Bingo. With php you can print the literal of any variable within the code itself, my brain was stuck trying to do the same here, lol.

Thanks TM.

One last question,

set %group200 AAA_BBB
set %group450 CCC_DDD

During the sub calculations are made against itemtypes and a final value number is generated(ie: 200). The next section of the script requires that I check to make sure that the itemtype is indeed in the group bearing the final value number(ie: if the final value is 200 then that item's itemtype is in %group200).

Sounds simple, and I'm sure it is, but I'm drawing a brain fart on the syntax. Example:

set %finalvalue 200
IF #FINDTYPE in %group200

I don't want to repeat the above check for each of the 210 groups and obviously "IF #FINDTYPE in %group%finalvalue" won't work(example to give you an idea of what I'm after)... so how can I I append the %finalvalue number to the %group to come up with %group200 ?

It might help if I'm more specific, I'm hoping it's possible to tighten up this particular sub a bit. It deals with 210 "words", each belonging to a different itemtype.

set %itemtypes AAA_BBB_CCC_DDD_EEE_ETC...
finditem %itemtypes etc

but instead of proceeding from there I need to confirm that a particular word is found in the #property of every %itemtypes found, which is itself in a loop that itterates through each result, among other things. Is it not possible to create a single, albeit long, "set" of words instead of creating a lot of arrays? I don't want to return a positive unless an %itemtypes and "word" combo is found. CHecking each result against a long list of arrays, or if statements, doesn't feel optimal for my specific needs with this.

Just to confirm, it's not possible to create a single "set" of many words and return a positive if any one word is in that set ?

I don't have a picture of it but I do know how they are doing it. They originally broke being able to make them by shortening how much text you could enter into the book title, not leaving enough for all of the html code required. There is however a short bit of code you can use and still have enough for a few letters of text on a colored background. All of them are 1 line in length, avoid those... worthless.