MasterLeon79
New Member
- Joined
- Dec 31, 2014
- Messages
- 213
LOL someone's on the fast lane.. I'll test the new release right away 
thanks!!

thanks!!
"Massassi Pendant", "Mark of Cooperation",
Bob you're awesome...
What I noticed is that it is still ignoring prototypes (tested with implants and chest gear)
Also: Could you add another check to "toggles" for Decorations as soon as you figure how to separate them from the other goodies such as rep-items?
Other than that GREAT WORK MAN!!! You're truly worth it
ADD: Sorry just one more question . The plugin does need time to compare all the gear. Are you checking the new items in the inventory by slot or as "gear"-type in general? Maybe it's possible to check only the slots which the new Item in the inventory refers to?
Edit: It does look like the implant is equipping in your logs. Only the leggings and lightsaber aren't equipping. I can't do anything about that at the moment, but I did message Aevitas about the orange items not working correctly, so hopefully it gets fixed. If that's fixed, it will solve all of these problems.
.
For some reason, the bot can't get the slot types sometimes. I added some new code in v.06 to see if it's more reliable, but I'm not 100% certain. As for the blue implant coming in as orange, I'm not sure why it's doing that. I tried equipping some blue implants on my guy that had an augment slot and they were still coming in correctly. I'm wondering if it's because it equipped over the first implant, but was still trying to compare the 2nd implant to the Might Package which was already equipped, so it bugged out. I added a fix to not look at the 2nd item if the 1st one was replaced.
Line 248: [00:48:19.261 N] [EquipMe] Synthesized Battle D-Package - Strength: 28 Weight: 280
Line 249: [00:48:19.288 N] [EquipMe] Synthesized Battle D-Package - Endurance: 24 Weight: 0
Line 250: [00:48:19.298 N] [EquipMe] Synthesized Battle D-Package - CriticalChanceRating: 12 Weight: 96
Line 251: [00:48:19.329 N] [EquipMe] Comparing Specialized Might Package(392) to Synthesized Battle D-Package(376)
Line 252: [00:48:19.355 N] [EquipMe] Skipping Synthesized Battle D-Package because it is Custom(Orange).
Line 388: [00:48:30.439 N] [EquipMe] Synthesized Battle D-Package - Strength: 28 Weight: 280
Line 389: [00:48:30.505 N] [EquipMe] Synthesized Battle D-Package - Endurance: 24 Weight: 0
Line 390: [00:48:30.530 N] [EquipMe] Synthesized Battle D-Package - CriticalChanceRating: 12 Weight: 96
Line 391: [00:48:30.562 N] [EquipMe] Comparing [Prototype] Subelectronic Reaction D-Implant(460) to Synthesized Battle D-Package(376)
Line 392: [00:48:30.568 N] [EquipMe] Skipping Synthesized Battle D-Package because it is Custom(Orange).
Thanks very much! That's next on my TODO list, hopefully reducing the runtime in checking. My idea is possibly ignoring items that have been checked in the past. I don't think there's any other way to check only new items that come in, but it would be super nice.
Getting there
The implants seem to equip correctly now.
This is just a reminder because I have mentioned this one already
[EquipMe] Skipping Prototype Krail Armory Banded Cuirass because it is Custom(Orange). <- it's actually blue
Same as for the implants.
btw: I'm new to SVN and I always preferred to have a previous version to roll back to if something nasty happens with an update. Is there a way to store versions locally via i.e. tortoise svn or do I have to do a copy manually?
So tortoise SVN makes it really easy to roll back on updates. I've attached images that show how to checkout a past revision of mine. You'll basically right-click on my plugin folder, go to Turtoise SVN => Log and then you can checkout any of my past updates. To go back to my latest update, you can just select the Update option like normal.
[03:35:30.168 N] [EquipMe] Beginning inv count: 42 vs old count: 41
[03:35:30.284 D] Nav callback called.
[03:35:37.962 N] [EquipMe] Checking: TholCorp Electrotex Sash -- EquipHumanBelt, Inventory, Bank, Loot, Buyback, 67. Matching slot: EquipHumanBelt
[03:35:38.019 N] [EquipMe] [Prototype] Venerable Ardent Blade's Waistcord Artifact -- 4
[03:35:38.091 N] [EquipMe] TholCorp Electrotex Sash - Endurance: 37 Weight: 0
[03:35:38.121 N] [EquipMe] TholCorp Electrotex Sash - CriticalChanceRating: 5 Weight: 40
[03:35:38.152 N] [EquipMe] TholCorp Electrotex Sash - ArmorRating: 209 Weight: 0
[03:35:38.194 N] [EquipMe] [Prototype] Venerable Ardent Blade's Waistcord - Strength: 51 Weight: 510
[03:35:38.223 N] [EquipMe] [Prototype] Venerable Ardent Blade's Waistcord - Endurance: 40 Weight: 0
[03:35:38.251 N] [EquipMe] [Prototype] Venerable Ardent Blade's Waistcord - CriticalChanceRating: 20 Weight: 160
[03:35:38.278 N] [EquipMe] [Prototype] Venerable Ardent Blade's Waistcord - ArmorRating: 313 Weight: 0
[03:35:38.338 N] [EquipMe] Comparing TholCorp Electrotex Sash(40) to [Prototype] Venerable Ardent Blade's Waistcord(670)
[03:35:38.362 N] [EquipMe] End of checking. Total inv count: 42
I had the bot turned off and when I started it again the plugin (during the initial check) compared the offhand with the main hand again. And even though both currently equipped sword were better the plugin insisted to reequip. Doing this the offhand changed again and the ingame the error "You cannot wield a secondary weapon without a primary one"
As for your quote above, the plugin thinks the Paramount Marauder's Offhand Saber is better because you only have the strength and crit chance weights set, which the Paramount Marauder's Offhand Saber has higher combined weight compared to the Paramount Marauder's Offhand Saber.[/FONT][/COLOR]
<EquipMeSettings>
<EnableAutoEquip>true</EnableAutoEquip>
<EnableRepItems>false</EnableRepItems>
<EnableLockboxes>true</EnableLockboxes>
<StatMain>20</StatMain>
<StatTechForce>18</StatTechForce>
<StatEndurance>14</StatEndurance>
<StatAccuracy>13</StatAccuracy>
<StatAlacrity>15</StatAlacrity>
<StatArmor>0</StatArmor>
<StatCritChance>17</StatCritChance>
<StatDamage>0</StatDamage>
<StatDefense>-10</StatDefense>
<StatGlance>0</StatGlance>
<StatPower>19</StatPower>
<StatExpertise>-10</StatExpertise>
<StatSurge>16</StatSurge>
</EquipMeSettings>