Bug - Confirmed Maximizer didn't equip a weapon
- Thread starter ziz
- Start date
Have done a couple of autoscend runs this year (when cleaver's dropped out of standard, generally it's been fine while i've had it) and it's having all sort of issues getting a weapon (for SC and TT) are logs useful to here or to autoscend? and if so assuming just the bit where it fails and adds extra debugging?
IIRC, Autoscend detects this and does some useful stuff like turning on debugging and redoing the search with Dump and 2 dump parameters.
What would help the most is a reduced test case that Frono and others could hit with a hammer until it confesses to the nature of the issue.
I, too have seen this while running autoscend, but it's usually a victim of the scroll back buffer being not very big and I have to remember that I had a problem and then go look. It was usually on day 1 or 2, usually between levels 5 and 8.
What would help the most is a reduced test case that Frono and others could hit with a hammer until it confesses to the nature of the issue.
I, too have seen this while running autoscend, but it's usually a victim of the scroll back buffer being not very big and I have to remember that I had a problem and then go look. It was usually on day 1 or 2, usually between levels 5 and 8.
Last edited:
Every time I have seen autoscend's logging, to the best of my ability, not equipping a weapon was the correct answer. This makes me sad and gives me nothing to try and debug.
If I were to guess, I'd wonder if it wasn't failing because for the weapon slot, it only had stolen accordion and none and the accordion is two-handed. It finds a better combo with none and august scepter, but since you can't equip an off-hand without a weapon, both fail.
That's where I'd start looking, anyway. But it's odd, because I do have weapons, like the boot knife and candy cane sword cane, so it could do an on-and-off hand combo. It just didn't consider the 1 handed weapons once it decided on an off-hand instead of a 2 handed weapon.
That could be a red herring.
That's where I'd start looking, anyway. But it's odd, because I do have weapons, like the boot knife and candy cane sword cane, so it could do an on-and-off hand combo. It just didn't consider the 1 handed weapons once it decided on an off-hand instead of a 2 handed weapon.
That could be a red herring.
This has happened to me again I believe 3 times in the last few days (autoscend, Normal Zoot). Sometimes closing and reopening mafia resolves it. Today I pulled Nuge's crossbow to see if that would resolve it (after seeing your post, MCroft) to no avail. Here's some debug info.
(Edit: Didn't realize Nuge's crossbow has a 30 moxie requirement, which I don't meet. Will try to pull an item I can use.)
(Edit edit: Pulled a sawed-off blunderbuss, which is immediately equippable. Pulling this unblocked the script. This supports MCroft's suggestion!)
Code:
> debug output
[fake arrow-through-the-head (1,708), astronaut helmet (1,710), Apriling band helmet (1,769)]
[Apriling band helmet]
SLOT OFFHAND
[hobo code binder (1,644), stuffed astral badger (1,644), McHugeLarge left pole (1,646), Roman Candelabra (1,689), august scepter (1,719), oversized monocle on a stick (1,769)]
[oversized monocle on a stick, McHugeLarge left pole]
SLOT CONTAINER
[McHugeLarge duffel bag (1,585), bat wings (1,769)]
[bat wings, McHugeLarge duffel bag]
SLOT PANTS
[old sweatpants (1,700), tearaway pants (1,769)]
[tearaway pants]
SLOT ACCESSORY1
[datastick (1,648), astral belt (1,651), McHugeLarge right ski (1,658), McHugeLarge left ski (1,669), Everfull Dart Holster (1,676), cursed monkey's paw (1,686), yamtility belt (1,710), Cincho de Mayo (1,769), spring shoes (1,899)]
[spring shoes, Cincho de Mayo, yamtility belt, McHugeLarge left ski, McHugeLarge right ski]
SLOT ACCESSORY2
[Knob Goblin tongs (1,644), Knob Goblin tongs (1,644), McHugeLarge right pole (1,644), McHugeLarge right pole (1,644), candy cane sword cane (1,677), candy cane sword cane (1,677)]
[candy cane sword cane, McHugeLarge right pole]
SLOT FAMILIAR
[toy Cupid bow (1,769)]
[toy Cupid bow]
Code:
> inv
1 (4)
2002 Mr. Store Catalog
astral belt
astral pilsner (6)
astronaut helmet
august scepter
beery blood (5)
big rock
Black and White Apron Meal Kit
bowl of cottage cheese
candy cane sword cane
Clan VIP Lounge key
closed-circuit pay phone
crunchy brush
cursed microwave
cursed monkey's paw
cursed pony keg
datastick
Everfull Dart Holster
fake arrow-through-the-head
goat cheese
groveling gravel
gunpowder burrito (5)
inflammable leaf
Knob Goblin tongs
Leprecondo
Mayam Calendar
McHugeLarge duffel bag
McHugeLarge left pole
McHugeLarge left ski
McHugeLarge right pole
McHugeLarge right ski
milestone
old sweatpants
Roman Candelabra
S.I.T. Course Completion Certificate
Sept-Ember Censer
server room key
stuffed astral badger
stuffed yam stinkbomb
TakerSpace letter of Marque
talking spade
The Nuge's favorite crossbow
wardrobe-o-matic
whet stone
yam (3)
Code:
> equip
Hat: Apriling band helmet
Weapon: (none)
Off-hand: oversized monocle on a stick
Shirt: (none)
Pants: tearaway pants
Back: bat wings
Acc. 1: Cincho de Mayo
Acc. 2: spring shoes
Acc. 3: yamtility belt
Pet: Jill-of-All-Trades (1 lbs)
Item: toy Cupid bow(Edit: Didn't realize Nuge's crossbow has a 30 moxie requirement, which I don't meet. Will try to pull an item I can use.)
(Edit edit: Pulled a sawed-off blunderbuss, which is immediately equippable. Pulling this unblocked the script. This supports MCroft's suggestion!)
Last edited:
Available weapon choices are none and 2 handed. Numerically a one handed weapon plus something offhand is a better choice. Maximizer picks that and then fails because cannot equip offhand without a mainhand. Correct?
In that case the "bug" might better be described as the maximizer recommends an impossible combination - none, plus offhand. Correct?
That might be easily testable. I'll add that to mist although the list is long enough that I keep forgetting what is on the bottom of it.
Also, it looks like we try to take care of that very case
Edit: I don't see in that block where we take care of offhand but not a weapon, but that doesn't mean we don't.
Java:
(Evaluator.java, line 143+)
// Equipment slots, that aren't the primary slot of any item type,
// that are repurposed here (rather than making the array bigger).
// Watches have to be handled specially because only one can be
// used - otherwise, they'd fill up the list, leaving no room for
// any non-watches to put in the other two acc slots.
// 1-handed weapons have to be ranked separately due to the following
// possibility: all of your best weapons are 2-hand, but you've got
// a really good off-hand, better than any weapon. There would
// otherwise be no suitable weapons to go with that off-hand.
static final Slot OFFHAND_MELEE = Slot.ACCESSORY2;
static final Slot OFFHAND_RANGED = Slot.ACCESSORY3;
static final Slot WEAPON_1H = Slot.STICKER3;
Last edited:
Yellowbeard
New member
Posted on the main thread then realized this was here. Pasting my comment below and will attach my log. Sorry in advance for the initial mistake.
NOTE: Equipping a weapon first and then re-running autoscend does NOT work in my case. Saw that as I was reading through threads and thought it might be useful to report. Thanks again for all you do!
ALSO: Autoscend - Hardcore - Standard
First of all, thanks for any help in advance. I LOVE this script and thank you very much to those working on it. You folks ROCK.
I have tried loading old builds and keep getting this error. I just got it after installing the newest daily build (28494) but also got it when I ran 28493, 28488, 28484, 28481, and 28477. I have been in aftercore for a few weeks and just got this on a new ascension immediately. This is my first bug report and I am trying to follow all the instructions but please forgive me if I err. Just let me know if I do and I will try to correct it.
Basically every time I try to run autoscend I get to this almost immediately.
Here's the message I get when I run autoscend (forgive me if I shouldn't have posted this part here please):
[ERROR] It looks like the maximizer didn't equip any weapons for you. Lets dump some debugging info to help the KolMafia devs look into this.
[DEBUG] Adding "2 dump" to current maximizer statement
Maximizer: 5item,meat,0.5initiative,0.1da 1000max,dr,0.5all res,1.5mainstat,-fumble,0.4hp,0.2mp 1000max,3mp regen,1.5weapon damage,0.75weapon damage percent,1.5elemental damage,2familiar weight,5familiar exp,15Moxie experience,5Moxie experience percent,+200bonus spring shoes,+200bonus bat wings,effective,+20bonus rake,2 dump
Loading character status...
Maximizing...
Outfits [Bounty-Hunting Rig, Tapered Threads, Cursed Zombie Pirate Costume, Hyperborean Hobo Habiliments, Grimy Reaper's Vestments, Legendary Regalia of the Master Squeezeboxer, Transparent Trappings, Blasphemous Bedizenment, Bits o' Honey, Seafaring Suit, Violent Vestments, Dreadful Zombie Suit, Cool Irons, Wrought Wrappings, Toxic Togs, The Jokester's Costume, Eldritch Equipage, FantasyRealm Warrior's Outfit, Mutant Parts Apparel, Whittled Wearables]
SLOT HAT
[ravioli hat (2,317), helmet turtle (2,317), disco mask (2,318), mariachi hat (2,318), coconut shell (2,321), fake arrow-through-the-head (2,324), astronaut helmet (2,324), Apriling band helmet (2,392)]
[Apriling band helmet]
SLOT WEAPON
[(none) (2,392), stolen accordion (2,394)]
[stolen accordion]
SLOT OFFHAND
[hobo code binder (2,218), magical ice cubes (2,220), McHugeLarge left pole (2,222), rake (2,241), April Shower Thoughts shield (2,263), oversized monocle on a stick (2,343), Roman Candelabra (2,358), august scepter (2,392)]
[august scepter, McHugeLarge left pole]
SLOT CONTAINER
[McHugeLarge duffel bag (2,213), bat wings (2,392)]
[bat wings, McHugeLarge duffel bag]
SLOT PANTS
[old sweatpants (2,299), tearaway pants (2,392)]
[tearaway pants]
SLOT ACCESSORY1
[datastick (2,141), McHugeLarge left ski (2,146), McHugeLarge right ski (2,156), cursed monkey's paw (2,184), yamtility belt (2,203), Cincho de Mayo (2,262), spring shoes (2,392)]
[spring shoes, Cincho de Mayo, yamtility belt, McHugeLarge right ski, McHugeLarge left ski]
SLOT ACCESSORY2
[seal-clubbing club (2,221), seal-clubbing club (2,221), turtle totem (2,221), turtle totem (2,221), pasta spoon (2,221), pasta spoon (2,221), saucepan (2,221), saucepan (2,221), little paper umbrella (2,225), little paper umbrella (2,225), McHugeLarge right pole (2,312), McHugeLarge right pole (2,312), candy cane sword cane (2,385), candy cane sword cane (2,385)]
[candy cane sword cane, McHugeLarge right pole]
120 combinations checked, best score 2,392.59
[DEBUG] Removing "2 dump" from current maximizer statement
NO WEAPON WAS EQUIPPED BY THE MAXIMIZER. REPORT THIS IN DISCORD AND INCLUDE YOUR SESSION LOG! YOU CAN RE-RUN AUTOSCEND AND IT SHOULD RUN OK (possibly).
Stack trace:
at equipMaximizedGear (auto_equipment.ash:1062)
at equipBaseline (auto_equipment.ash:1181)
at initializeDay (autoscend.ash:993)
at auto_begin (autoscend.ash:2150)
at safe_preference_reset_wrapper (autoscend.ash:2192)
at safe_preference_reset_wrapper (autoscend.ash:2199)
at safe_preference_reset_wrapper (autoscend.ash:2199)
at safe_preference_reset_wrapper (autoscend.ash:2199)
at main (autoscend.ash:2247)
allowNonMoodBurning => false
Preference allowNonMoodBurning changed from true to false
logPreferenceChangeFilter => _lastCombatStarted,libram_savedMacro,maximizerMRUList,testudinalTeachings,spadingData,combo_lastTileCombed,_beachLayout,_beachMinutes,_beachCombing
Preference logPreferenceChangeFilter changed from maximizerMRUList,testudinalTeachings,auto_maximize_current to _lastCombatStarted,libram_savedMacro,maximizerMRUList,testudinalTeachings,spadingData,combo_lastTileCombed,_beachLayout,_beachMinutes,_beachCombing
printStackOnAbort => false
Preference printStackOnAbort changed from true to false
removeMalignantEffects => true
Preference removeMalignantEffects changed from false to true
afterAdventureScript =>
Preference afterAdventureScript changed from scripts/autoscend/auto_post_adv.ash to
autoSatisfyWithCoinmasters => false
Preference autoSatisfyWithCoinmasters changed from true to false
autoSatisfyWithNPCs => false
Preference autoSatisfyWithNPCs changed from true to false
betweenBattleScript =>
Preference betweenBattleScript changed from scripts/autoscend/auto_pre_adv.ash to
breakableHandling => 1
Preference breakableHandling changed from 4 to 1
choiceAdventureScript =>
Preference choiceAdventureScript changed from scripts/autoscend/auto_choice_adv.ash to
dontStopForCounters => false
Preference dontStopForCounters changed from true to false
hpAutoRecoveryTarget => 1.0
Preference hpAutoRecoveryTarget changed from -0.05 to 1.0
lastChanceBurn => cast # Patience of the Tortoise
Preference lastChanceBurn changed from to cast # Patience of the Tortoise
lastChanceThreshold => 100
Preference lastChanceThreshold changed from 1 to 100
maximizerCombinationLimit => 0
Preference maximizerCombinationLimit changed from 100000 to 0
maximizerMRUSize => 5
Preference maximizerMRUSize changed from 0 to 5
promptAboutCrafting => 1
Preference promptAboutCrafting changed from 0 to 1
autoscend (formerly sl_ascend) is under new management. Soolar (the maintainer of sl_ascend) and Jeparo (the most active contributor) have decided to cease development of sl_ascend in response to Jick's behavior that has recently come to light. New developers have taken over maintenance and rebranded sl_ascend to autoscend as per Soolar's request. Please be patient with us during this transition period. Please see the readme on the github page for more information.
NOTE: Equipping a weapon first and then re-running autoscend does NOT work in my case. Saw that as I was reading through threads and thought it might be useful to report. Thanks again for all you do!
ALSO: Autoscend - Hardcore - Standard
First of all, thanks for any help in advance. I LOVE this script and thank you very much to those working on it. You folks ROCK.
I have tried loading old builds and keep getting this error. I just got it after installing the newest daily build (28494) but also got it when I ran 28493, 28488, 28484, 28481, and 28477. I have been in aftercore for a few weeks and just got this on a new ascension immediately. This is my first bug report and I am trying to follow all the instructions but please forgive me if I err. Just let me know if I do and I will try to correct it.
Basically every time I try to run autoscend I get to this almost immediately.
Here's the message I get when I run autoscend (forgive me if I shouldn't have posted this part here please):
[ERROR] It looks like the maximizer didn't equip any weapons for you. Lets dump some debugging info to help the KolMafia devs look into this.
[DEBUG] Adding "2 dump" to current maximizer statement
Maximizer: 5item,meat,0.5initiative,0.1da 1000max,dr,0.5all res,1.5mainstat,-fumble,0.4hp,0.2mp 1000max,3mp regen,1.5weapon damage,0.75weapon damage percent,1.5elemental damage,2familiar weight,5familiar exp,15Moxie experience,5Moxie experience percent,+200bonus spring shoes,+200bonus bat wings,effective,+20bonus rake,2 dump
Loading character status...
Maximizing...
Outfits [Bounty-Hunting Rig, Tapered Threads, Cursed Zombie Pirate Costume, Hyperborean Hobo Habiliments, Grimy Reaper's Vestments, Legendary Regalia of the Master Squeezeboxer, Transparent Trappings, Blasphemous Bedizenment, Bits o' Honey, Seafaring Suit, Violent Vestments, Dreadful Zombie Suit, Cool Irons, Wrought Wrappings, Toxic Togs, The Jokester's Costume, Eldritch Equipage, FantasyRealm Warrior's Outfit, Mutant Parts Apparel, Whittled Wearables]
SLOT HAT
[ravioli hat (2,317), helmet turtle (2,317), disco mask (2,318), mariachi hat (2,318), coconut shell (2,321), fake arrow-through-the-head (2,324), astronaut helmet (2,324), Apriling band helmet (2,392)]
[Apriling band helmet]
SLOT WEAPON
[(none) (2,392), stolen accordion (2,394)]
[stolen accordion]
SLOT OFFHAND
[hobo code binder (2,218), magical ice cubes (2,220), McHugeLarge left pole (2,222), rake (2,241), April Shower Thoughts shield (2,263), oversized monocle on a stick (2,343), Roman Candelabra (2,358), august scepter (2,392)]
[august scepter, McHugeLarge left pole]
SLOT CONTAINER
[McHugeLarge duffel bag (2,213), bat wings (2,392)]
[bat wings, McHugeLarge duffel bag]
SLOT PANTS
[old sweatpants (2,299), tearaway pants (2,392)]
[tearaway pants]
SLOT ACCESSORY1
[datastick (2,141), McHugeLarge left ski (2,146), McHugeLarge right ski (2,156), cursed monkey's paw (2,184), yamtility belt (2,203), Cincho de Mayo (2,262), spring shoes (2,392)]
[spring shoes, Cincho de Mayo, yamtility belt, McHugeLarge right ski, McHugeLarge left ski]
SLOT ACCESSORY2
[seal-clubbing club (2,221), seal-clubbing club (2,221), turtle totem (2,221), turtle totem (2,221), pasta spoon (2,221), pasta spoon (2,221), saucepan (2,221), saucepan (2,221), little paper umbrella (2,225), little paper umbrella (2,225), McHugeLarge right pole (2,312), McHugeLarge right pole (2,312), candy cane sword cane (2,385), candy cane sword cane (2,385)]
[candy cane sword cane, McHugeLarge right pole]
120 combinations checked, best score 2,392.59
[DEBUG] Removing "2 dump" from current maximizer statement
NO WEAPON WAS EQUIPPED BY THE MAXIMIZER. REPORT THIS IN DISCORD AND INCLUDE YOUR SESSION LOG! YOU CAN RE-RUN AUTOSCEND AND IT SHOULD RUN OK (possibly).
Stack trace:
at equipMaximizedGear (auto_equipment.ash:1062)
at equipBaseline (auto_equipment.ash:1181)
at initializeDay (autoscend.ash:993)
at auto_begin (autoscend.ash:2150)
at safe_preference_reset_wrapper (autoscend.ash:2192)
at safe_preference_reset_wrapper (autoscend.ash:2199)
at safe_preference_reset_wrapper (autoscend.ash:2199)
at safe_preference_reset_wrapper (autoscend.ash:2199)
at main (autoscend.ash:2247)
allowNonMoodBurning => false
Preference allowNonMoodBurning changed from true to false
logPreferenceChangeFilter => _lastCombatStarted,libram_savedMacro,maximizerMRUList,testudinalTeachings,spadingData,combo_lastTileCombed,_beachLayout,_beachMinutes,_beachCombing
Preference logPreferenceChangeFilter changed from maximizerMRUList,testudinalTeachings,auto_maximize_current to _lastCombatStarted,libram_savedMacro,maximizerMRUList,testudinalTeachings,spadingData,combo_lastTileCombed,_beachLayout,_beachMinutes,_beachCombing
printStackOnAbort => false
Preference printStackOnAbort changed from true to false
removeMalignantEffects => true
Preference removeMalignantEffects changed from false to true
afterAdventureScript =>
Preference afterAdventureScript changed from scripts/autoscend/auto_post_adv.ash to
autoSatisfyWithCoinmasters => false
Preference autoSatisfyWithCoinmasters changed from true to false
autoSatisfyWithNPCs => false
Preference autoSatisfyWithNPCs changed from true to false
betweenBattleScript =>
Preference betweenBattleScript changed from scripts/autoscend/auto_pre_adv.ash to
breakableHandling => 1
Preference breakableHandling changed from 4 to 1
choiceAdventureScript =>
Preference choiceAdventureScript changed from scripts/autoscend/auto_choice_adv.ash to
dontStopForCounters => false
Preference dontStopForCounters changed from true to false
hpAutoRecoveryTarget => 1.0
Preference hpAutoRecoveryTarget changed from -0.05 to 1.0
lastChanceBurn => cast # Patience of the Tortoise
Preference lastChanceBurn changed from to cast # Patience of the Tortoise
lastChanceThreshold => 100
Preference lastChanceThreshold changed from 1 to 100
maximizerCombinationLimit => 0
Preference maximizerCombinationLimit changed from 100000 to 0
maximizerMRUSize => 5
Preference maximizerMRUSize changed from 0 to 5
promptAboutCrafting => 1
Preference promptAboutCrafting changed from 0 to 1
autoscend (formerly sl_ascend) is under new management. Soolar (the maintainer of sl_ascend) and Jeparo (the most active contributor) have decided to cease development of sl_ascend in response to Jick's behavior that has recently come to light. New developers have taken over maintenance and rebranded sl_ascend to autoscend as per Soolar's request. Please be patient with us during this transition period. Please see the readme on the github page for more information.
Yellowbeard
New member
Just FYI the first time I have had this problem is ALSO when I was running an AT. I am starting to wonder if this is the issue. Please let me know if there are tests I can run to try and help.
Yellowbeard
New member
Also just tried selling my stolen accordion and then re-running. Still having the same problem unfortunately.
Yellowbeard
New member
I am not a coder and so I don't know if this helps, but this section of code is odd to me. Looking at the portion in red below:
1. It seems to be looking at weapons as potential SLOT ACCESSORY2 choices
2. It doesn't seem to be choosing a SLOT ACCESSORY3
3. It doesn't seem to be choosing a SLOT WEAPON
And the maximizer ITSELF tells me that "NO WEAPON WAS EQUIPPED BY THE MAXIMIZER...etc" so this definitely seems like a maximizer error to me. Is it somehow skipping SLOT ACCESSORY3 and SLOT WEAPON?
Hope I am not saying hopelessly stupid things that are obvious to anyone who actually programs.
SLOT HAT
[ravioli hat (2,349), helmet turtle (2,350), disco mask (2,351), mariachi hat (2,351), coconut shell (2,353), fake arrow-through-the-head (2,356), astronaut helmet (2,356), futuristic hat (2,367), Apriling band helmet (2,425)]
[Apriling band helmet]
SLOT OFFHAND
[hobo code binder (2,251), magical ice cubes (2,253), McHugeLarge left pole (2,254), rake (2,274), oversized monocle on a stick (2,277), April Shower Thoughts shield (2,296), Roman Candelabra (2,391), august scepter (2,425)]
[august scepter, McHugeLarge left pole]
SLOT CONTAINER
[McHugeLarge duffel bag (2,186), bat wings (2,425)]
[bat wings, McHugeLarge duffel bag]
SLOT SHIRT
[futuristic shirt (2,425)]
[futuristic shirt]
SLOT PANTS
[old sweatpants (2,324), tearaway pants (2,425)]
[tearaway pants]
SLOT ACCESSORY1
[continuum transfunctioner (2,172), datastick (2,172), McHugeLarge left ski (2,177), McHugeLarge right ski (2,187), cursed monkey's paw (2,215), Cincho de Mayo (2,235), yamtility belt (2,236), spring shoes (2,425)]
[spring shoes, yamtility belt, Cincho de Mayo, McHugeLarge right ski, McHugeLarge left ski]
SLOT ACCESSORY2
[seal-clubbing club (2,253), seal-clubbing club (2,253), turtle totem (2,253), turtle totem (2,253), pasta spoon (2,253), pasta spoon (2,253), saucepan (2,253), saucepan (2,253), little paper umbrella (2,258), little paper umbrella (2,258), McHugeLarge right pole (2,345), McHugeLarge right pole (2,345), candy cane sword cane (2,418), candy cane sword cane (2,418)]
[candy cane sword cane, McHugeLarge right pole]
SLOT FAMILIAR
[tiny rake (2,336), futuristic collar (2,340), toy Cupid bow (2,425)]
[toy Cupid bow]
1. It seems to be looking at weapons as potential SLOT ACCESSORY2 choices
2. It doesn't seem to be choosing a SLOT ACCESSORY3
3. It doesn't seem to be choosing a SLOT WEAPON
And the maximizer ITSELF tells me that "NO WEAPON WAS EQUIPPED BY THE MAXIMIZER...etc" so this definitely seems like a maximizer error to me. Is it somehow skipping SLOT ACCESSORY3 and SLOT WEAPON?
Hope I am not saying hopelessly stupid things that are obvious to anyone who actually programs.
SLOT HAT
[ravioli hat (2,349), helmet turtle (2,350), disco mask (2,351), mariachi hat (2,351), coconut shell (2,353), fake arrow-through-the-head (2,356), astronaut helmet (2,356), futuristic hat (2,367), Apriling band helmet (2,425)]
[Apriling band helmet]
SLOT OFFHAND
[hobo code binder (2,251), magical ice cubes (2,253), McHugeLarge left pole (2,254), rake (2,274), oversized monocle on a stick (2,277), April Shower Thoughts shield (2,296), Roman Candelabra (2,391), august scepter (2,425)]
[august scepter, McHugeLarge left pole]
SLOT CONTAINER
[McHugeLarge duffel bag (2,186), bat wings (2,425)]
[bat wings, McHugeLarge duffel bag]
SLOT SHIRT
[futuristic shirt (2,425)]
[futuristic shirt]
SLOT PANTS
[old sweatpants (2,324), tearaway pants (2,425)]
[tearaway pants]
SLOT ACCESSORY1
[continuum transfunctioner (2,172), datastick (2,172), McHugeLarge left ski (2,177), McHugeLarge right ski (2,187), cursed monkey's paw (2,215), Cincho de Mayo (2,235), yamtility belt (2,236), spring shoes (2,425)]
[spring shoes, yamtility belt, Cincho de Mayo, McHugeLarge right ski, McHugeLarge left ski]
SLOT ACCESSORY2
[seal-clubbing club (2,253), seal-clubbing club (2,253), turtle totem (2,253), turtle totem (2,253), pasta spoon (2,253), pasta spoon (2,253), saucepan (2,253), saucepan (2,253), little paper umbrella (2,258), little paper umbrella (2,258), McHugeLarge right pole (2,345), McHugeLarge right pole (2,345), candy cane sword cane (2,418), candy cane sword cane (2,418)]
[candy cane sword cane, McHugeLarge right pole]
SLOT FAMILIAR
[tiny rake (2,336), futuristic collar (2,340), toy Cupid bow (2,425)]
[toy Cupid bow]
Yellowbeard
New member
This isn't maximizer this is autoscend.
Nothing has been changed or fixed. This issue doesn't happen all the time, which is why it is tricky to fix.
We know one issue -- with "+effective", if there are no valid weapons, nothing will be equipped. The accordion issue you have above is different, but by the looks of it, it happens because you only have a 2-handed weapon, and "nothing" + "offhand" is ranked higher.
@Yellowbeard
First, thank you for reporting. This has been a long and difficult issue to debug. The folks at autoscend graciously agreed to assist in gathering data which is why you get the messages you do.
The hope is that someone will come up with a set of conditions where no weapon is equipped AND identify a weapon that is available to equip and equipping the weapon produces a higher maximizer score under the same conditions. In the absence of such an example it is not clear whether there is a bug or a feature request or just an opportunity for people who write maximizer strings to make a greater effort to understand the side effects of their maximizer string choices.
There are people who think any weapon is better than none. This is probably a feature request because there are a few cases where no weapon is the right answer. Using the effective keyword is a common case where no weapon is correct. Way of the Surprising Fist path and skills sometimes make no weapon the appropriate choice. Low level characters often lack weapons that could be equipped. As noted above "nothing" + offhand can score higher than any two handed weapon. A case where "nothing" + offhand is chosen when there are available one-handed weapons is probably a bug, but so far no one has reported it.
The autoscend information is helpful but ideally the next step after getting the message would be to identify the weapon that should have been equipped.
Thank you.
First, thank you for reporting. This has been a long and difficult issue to debug. The folks at autoscend graciously agreed to assist in gathering data which is why you get the messages you do.
The hope is that someone will come up with a set of conditions where no weapon is equipped AND identify a weapon that is available to equip and equipping the weapon produces a higher maximizer score under the same conditions. In the absence of such an example it is not clear whether there is a bug or a feature request or just an opportunity for people who write maximizer strings to make a greater effort to understand the side effects of their maximizer string choices.
There are people who think any weapon is better than none. This is probably a feature request because there are a few cases where no weapon is the right answer. Using the effective keyword is a common case where no weapon is correct. Way of the Surprising Fist path and skills sometimes make no weapon the appropriate choice. Low level characters often lack weapons that could be equipped. As noted above "nothing" + offhand can score higher than any two handed weapon. A case where "nothing" + offhand is chosen when there are available one-handed weapons is probably a bug, but so far no one has reported it.
The autoscend information is helpful but ideally the next step after getting the message would be to identify the weapon that should have been equipped.
Thank you.
I didn't find where it should take care of that case, but it looks like in the past evaluator.java was supposed to be aware of it. It may be that it sometimes is and there's an edge case. I'm looking to see if there's an obvious place to say "offhand value=0 if weapon=null", but no one should wait on me if they see a way to fix it.
We should discuss what a fix might be. "nothing" + offhand is the right answer in some cases.
If we can ever find a case where (something + offhand) > (nothing + offhand) but the maximizer picks nothing then we have a bug that needs to be fixed. But until we find that something what we really have is a feature request.