First off...


I think the "Lag Mode" is quite funny...


As for the "ID Everything"... how else do you decide what to "Find"? Do you ID every 3rd item and guess at the other 2?


Ahhh, it's the Gouru Conspiracy thing... Gouru has a Secret method to ID things that does not require they be id'ed...


I like the other feature Gouru has... after 30 seconds of unattended operation where Find-it can find Monsters it starts silently reporting you for UCM...


Ok, the last 2 are jokes... but hey, so is the Lag mode...

Only check weapons for weapon configs, only check items that can have spells for majors, only check armor for AL, etc, etc.

 

-----signature-----

Hamfast...


the difference is in processing EVERY statistic of EVERY item, or selectivly choosing based on item types


there are certain items that really don't need to even be looked at... by selectively choosing groups of items, it allows you to not have to do massive processing on EVERY item that comes in (which is what BS/2 did).

Actually, theres quite a few lines of code to prevent some things from being ID'd. As much as possible I try to work from the Create Object packet. Some things require an ID, weapons and armor for instance in order to get the stats. The only reason to ID a monster is to find out if it's 'mine'. Put a number of users in a dungeon with plugins that ID monsters, every time a monster dies, every one of those users sends a 'mine?' request to the server. Multiply that by the numbers of monsters dieing in a high spawn dungeon, and multiple dungeons on the same server. Not only is there personal lag being caused, there is additional server lag caused by having to process all these additional requests. How much? I don't know. But it is unneeded work. Worst case problem is trying to open a corpse that you don't yet have rights to. You get a message and move on to the next.

*shrug*


i thought the lag thing was cute when i saw it


it made me smile

 

-----signature-----

I'll take my BS/2, thank you very much, with it's incredibly detailed user configurable rules ability. You may be happy in your Toyota, but I'll enjoy my ride in my Ferrari infinitely more. To each his or her own, I suppose.


Lag? I ran a huge list of rules; it worked perfectly and didn't lag for me.

 

-----signature-----

Drakier,


I understand that every stat of every item need not be looked at... but to get the basic data for an item wouldn't you need to ID it?


Now I don't use Find-it nor did I use BS2, so I am kind of fishing here... I am only looking for casters with Mana C of 10%, Melee Def of 12% and work less then 5... and Imbue materials.


A MOB dies, A corpse gets created, ID it to see if it was mine... yes...


Open it...

5 items on it... (collection of creations)

Pyreals - ignore...

Sword - ignore as item - Material? - Steel - ignore

Caster - Mana C? - 10% - Melee Def? - 8% - ignore as item - Material? - Red Garnet - Grab...

Armor (Breastplate) - ignore as item - Material - Leather - Ignore

Armor (Crown) - ignore as item - Material - Gold - Ignore


At any point in the process an item can be eliminated... but some identification must be done to find out what it is... processing all that information may not be required, but is not all that data returned with the ID?


I can only imagine the lag caused if each statistical field needed to be quieried to get the information...


Thread Hijacking 101

What you get on any ID is the same sort of stuff that appears in the ID page when you right click on something. Everything comes at once.


The savings is in ignoring stuff like pyreals or bad materials, methinks.

 

-----signature-----

Some threads deserve to be hijacked...


A lot of information comes in with a 'Create Object' packet. This comes ANY time an object is created in the area, no matter what the type. It contains a lot of basic information about the object, but does not contain it all.


Additional information is obtained by sending a 'Request Id' message. The client does this when you right click on something, or press the Examine key. The server processes this and then sends you additional information on that object.


The system was designed to be a manual process, requiring either a right click or pressing the E button and was not meant to be something spammed by automatic processes. As a developer I feel a responsibility to avoid using systems too far outside their design parameters. So I try to limit the ID's to be no more than a normal user would use when checking loot. A 'normal' user does not ID every corpse in the vicinity to see if it belongs to them.

I think that is funny as heck.


I also support Chaz in his right to voice his opinion, just like I support Gouru to ask people not to use his programs with xTank.


I also find it "telling" of the state of mind of one App Dev to "rag" on another App Devs code to the point of putting that "joke" in.


As for what it is "telling", I'm not telling.