taltamir
Member
http://kol.coldfront.net/thekolwiki/index.php/Little_bitty_bathysphere
unlockeding the sea automatically puts the little bitty bathysphere in your inventory as a quest item.
The bathysphere gives you a -20 familiar weight debuff while equipped, and allows your familiar to go into the sea.
not too long ago there was a fix to maximizer so that it will not prefer bathysphere (and its -20 malus) to having nothing equipped on the familiar.
However, this fix seems to have missed the -tie function resulting in current implementation being inconsistent.
If I optimize (in run with bathysphere being my only familiar equip) using the cli command:
maximize meat
maximize adv
then bathysphere will not be equipped.
However, if I instead optimize using the cli commands:
maximize -tie,meat
maximize -tie,adv
then bathysphere will be equipped.
meaning that the current implementation is inconsistent. Although worth noting that familiars that specifically directly affect the maximizer string do not get bathysphere even with tie.
That is, leprechaun will not suggest bathysphere on maximize -tie,meat
Fairy will not suggest bathysphere on maximize -tie,item
It is only when your familiar is not directly contributing to the maximized effect that maximizer -tie decides to cripple your familiar with a bathysphere. (ex, maximizing meat while a fairy is equipped)
Also worth noting I am only using cli command as an example, the same happens if a script calls the maximizer function properly (aka, via the proper ash function and not via a CLI command). This makes this a problem for any script that uses maximize.
I think that the -tie version also be made to exclude bathysphere the same way that it is currently excluded from the non -tie strings. I am pretty sure it was a mistake that -tie was excluded when this was patched out in the past.
unlockeding the sea automatically puts the little bitty bathysphere in your inventory as a quest item.
The bathysphere gives you a -20 familiar weight debuff while equipped, and allows your familiar to go into the sea.
not too long ago there was a fix to maximizer so that it will not prefer bathysphere (and its -20 malus) to having nothing equipped on the familiar.
However, this fix seems to have missed the -tie function resulting in current implementation being inconsistent.
If I optimize (in run with bathysphere being my only familiar equip) using the cli command:
maximize meat
maximize adv
then bathysphere will not be equipped.
However, if I instead optimize using the cli commands:
maximize -tie,meat
maximize -tie,adv
then bathysphere will be equipped.
meaning that the current implementation is inconsistent. Although worth noting that familiars that specifically directly affect the maximizer string do not get bathysphere even with tie.
That is, leprechaun will not suggest bathysphere on maximize -tie,meat
Fairy will not suggest bathysphere on maximize -tie,item
It is only when your familiar is not directly contributing to the maximized effect that maximizer -tie decides to cripple your familiar with a bathysphere. (ex, maximizing meat while a fairy is equipped)
Also worth noting I am only using cli command as an example, the same happens if a script calls the maximizer function properly (aka, via the proper ash function and not via a CLI command). This makes this a problem for any script that uses maximize.
I think that the -tie version also be made to exclude bathysphere the same way that it is currently excluded from the non -tie strings. I am pretty sure it was a mistake that -tie was excluded when this was patched out in the past.
Last edited by a moderator: