| Author |
Topic:
Virindi Tank Classic Looter Modified Source and Binaries [Locked] |
|
|
Date Posted:
1/1/00 12:00am
Subject:
Virindi Tank Classic Looter Modified Source and Binaries |
So basically this makes the classic loot editor easier to use?
Why should i D/L it if i already have my loot rules set the way i want?
-----signature-----
Rahl
pb
|
|
|
Date Posted:
1/1/00 12:00am
Subject:
Virindi Tank Classic Looter Modified Source and Binaries |
|
Its a two part upgrade.
Part 1 is making the editor itself easier to use.
Part 2 is making your rules more effective via the addition of NEW requirements.
The idea behind these new requirements is to consolidate multiple weapon/armor rules that cover only some of the various possible mutations that might meet your minimum requirements into one rule that would meet every possible mutation.
Too many possible combinations of cantrips and stats to reach target minimums
Incatation of Blood Drinker
Minor/Major/Epic Blood Drinker
Minor/Major/Epic Heart Thirst
Incantation of Defender
Minor/Major/Epic Defender
Total Possible Combinations: 109 (Multiply this by the number of maxdamage/variance combos and it's over 9000!)
What does this mean?
Lets say you want a sword that is 33-59 +15 +15.
Well, there are so many ways a sword can get to those specs.
You could get a sword thats 27-55 +10 +10, and with spells like epic blood thirst, major defender, major heart thirst, it would meet your minimum requirements.
Using my new requirements you can set your rules more precise to pick up ANY POSSIBLE mutation of a weapon that would meet your min targets.
Like I said, if you wanted to do this using the stock classic looter, you would literally NEED to have 1000+ rules PER WEAPON to meet all the possible flavors of that weapon.
Who does this?
Most of us used to make about 30 or so rules per weapon so we wouldn't miss out, but.. you still miss out.
My system, you miss nothing, ever.
|
|
|
Date Posted:
1/1/00 12:00am
Subject:
Virindi Tank Classic Looter Modified Source and Binaries |
Cool, I installed it, and tbh I didnt notice anything different with the GUI, everything seemed the same - the new buffed loot rules.
-----signature-----
Rahl
pb
|
|
|
Date Posted:
1/1/00 12:00am
Subject:
Virindi Tank Classic Looter Modified Source and Binaries |
|
Hi Mag-nus, are you able to fix decal issues?
Lightning Protection on armor is not detected correctly, it's always seen as a "1" no matter what. My armor loot rules are supposed to not loot if any of the protects are lower then below average, and i'm mostly getting items with Poor lightning protect and dropping them on the floor.
Also, since your having fun with Clasic Looter, how about enhancing the color slot rules with some "Not=" options? =)
Another color based enhacement I saw someone else wanting is a "All Color Slots = Color" requirement. I can only guess it's for colors/shades not obtainable from dye, and they want the trim the same.
P.S. I just found your thread today, and I'm confused on obtaining your changes. Am I supposed to download Clasic Looter from your website still or is VI to pushing them out automaticaly now?
|
|
|
Date Posted:
1/1/00 12:00am
Subject:
Virindi Tank Classic Looter Modified Source and Binaries |
|
Some GUI features I added:
* Prompts you to save a modified file on close/exit.
* Form is now resizable and fields stretch accordingly.
* Added cntrl+click functionality to all New and Clone buttons.
-- Holding cntrl while you click on New or Clone will insert the new rule after the current rule instead of at the end of the list.
* Added tool tips for the Move Up, Move Down, New and Clone buttons.
-- Holding cntrl while clicking Move Up and Move Down moves the rule by 3 instead of by 1. This exists in the version published by Virindi but was not advertised.
* You can now associate .utl files in Windows Explorer with uTank2 Settings Editor.
-- Double click a loot profile and click open with, navigate to uTank2 Settings Editor, select the exe, and check always open with.
* You can drag loot profiles directly onto uTank2 Settings Editor for faster loading.
Now, to make these calculated requirements I added make a little more sense:
A common and one of the most simple rules is a sword that has a max potential damage just 3 points off of the perfect max.
The perfect max would be:
+60 Epic BD, BD8, which when buffed would result in a sword with 100 top end damage.
To get this on a weapon, you would need:
+60 Epic BD, BD8.
Using my new Buffed MaxDamage rule, you would set it to be >= 69 for a perfect sword, or >= 66 for a sword thats 3 points off.
Where does that 69 number come from though?
60 + 7 (Epic BD) + 2 (BD8).
BD8 adds two because if BD8 is found on the weapon, it will give you a bonus of 2 points of damage over the BD8 you can cast yourself, thus, +2.
So, with one simple rule, you could cover any possible variation to reach a weapon that is 3 points off of perfect.
Now, lets go over all the rules you would HAVE to make with the old non-calculated/buffed requirements to loot any sword that is - points off perfect.
57, Epic BD, BD8
59, Epic BD
60, Major BD, BD8
If you want a sword thats 6 points off perfect damage, you need to make even more rules to cover for more Major BD variations.
The point of this example is to show you how even such a simple requirement needs multiple rules to be covered with the non-cacluclated/buffed rules.
When you take into account an average damage output, attack mod, defense mod, etc.. the amount of rules you need grows exponentially. In that scenario its the same, you can make 1 rule with my new requirements to cover all of those exponential scenarios.
So what were people doing? They were making their rules so loose that they'd have to examine every piece and drop the ones that they didn't want. This gets old quickly. Not only do you fill up pack space quicker with junk, you need to take the time, every time, to id everything you pick up to make sure its good or junk.
With my system there is no more dropping stuff on the ground. You set these new rules at your absolute min, and however a weapon may get there, if it gets there, you'll loot it.
There are two main goals I wanted to accomplish with this:
1. Loot more variants of weapons/armor I wasn't due to above problems.
2. Save myself the time of having to manually determine if looted items in my pack where actually good or junk.
|
|
|
Date Posted:
1/1/00 12:00am
Subject:
Virindi Tank Classic Looter Modified Source and Binaries |
Aye appreciate the work, but tbh i just have a rule to pick up all major/epic bt weapons lol, and go through afterwards, that way i havent missed any good ones like in the situation I outlined. Sure i throw out a lot of bad ones, but oh well. I see the advatange of yours though. Thanks for your hard work.
-----signature-----
Rahl
pb
|
Paraduck Title: quantum mechanic
Posts: 484
Registered: 2001-2-27 18:19:03
|
Date Posted:
1/1/00 12:00am
Subject:
Virindi Tank Classic Looter Modified Source and Binaries |
Awesome mod. Thanks Magnus!
-----signature-----
We are like dwarfs sitting on the shoulders of giants. We see more and things that are more distant than they did,
not because our sight is superior or because we are taller than they, but because they raise us up and their
great stature adds to ours
|
|
|
Date Posted:
1/1/00 12:00am
Subject:
Virindi Tank Classic Looter Modified Source and Binaries |
* Form is now resizable and fields stretch accordingly. posted:
The window reizes for me but all the fields stay the same.
SL
|
|
|
Date Posted:
1/1/00 12:00am
Subject:
Virindi Tank Classic Looter Modified Source and Binaries |
|
Can you take a screenshot?
The rules list field stretches as do the requirements list, and requirements settings.
The info at the bottom does not stretch as it doesn't need to.
|
|
|
Date Posted:
1/1/00 12:00am
Subject:
Virindi Tank Classic Looter Modified Source and Binaries |
|
Ok checked again, the fields (like rule list and rules composition) do stretch vertical but not horizonal. I'm guessing its working as intended. I was expecting the fields to stretch horizonal also so a long rule name could be seen fully, but thats not really needed.
Its fine as it is, the box you type in to give a "value" to a rule stretches horizonal so that is good when entering numerous name values and such. Alls good thx.
SL
|
|