Grid Sage Forums
- November 22, 2024, 06:38:15 PM
- Welcome, Guest
|
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
1
Fixed Bugs & Non-Bugs / Re: [Beta 7.2] Auto equip prioritizes replacing same part over "weaker" variant
« on: January 22, 2019, 02:14:03 AM »
Ah yeah, no problem. Thanks for replying so fast! 
2
Fixed Bugs & Non-Bugs / [Beta 7.2] Auto equip prioritizes replacing same part over "weaker" variant
« on: January 22, 2019, 01:34:38 AM »
Beta 7.2
(Note: Exact integrity values arbitrary but correct relative to each other for the purpose of explaining behavior)
Scenario:
Equipped:
Medium Storage - Integrity 10
Large Storage - Integrity 20
Inventory:
Full (No free slots)
On ground:
Large Storage - Integrity 30
Current behavior:
Auto equipping Large Storage from ground results in Large Storage swapping out the currently equipped Large Storage since one on the ground is higher integrity.
Old Large Storage is now on ground. Auto equip that one and it replaces the Medium Storage.
What I would expect:
Large storage on ground to replace the Medium Storage since it is both a stronger variant and higher integrity.
Notes
I'm not sure if this is actually a bug, it's possible it's intended behavior. It seems like the priority of "replacing the same module with lower integrity" is higher then "replace a weaker variant". I feel like it would be of more value to make replacing weaker variants a higher priority for the auto-equip.
You might then ask "what about when the stronger variant actually has lower integrity", then I guess the decision is not as clear cut. For instance, a full integrity medium storage might be of more value compared to say a 1 integrity Large Storage. In that case I think it would be fair to not auto-equip/swap. But in the currently reported instance the module on the ground was a higher integrity then both.
This isn't unique to Storage, it's just the most recent example I noticed the behavior on.
(Note: Exact integrity values arbitrary but correct relative to each other for the purpose of explaining behavior)
Scenario:
Equipped:
Medium Storage - Integrity 10
Large Storage - Integrity 20
Inventory:
Full (No free slots)
On ground:
Large Storage - Integrity 30
Current behavior:
Auto equipping Large Storage from ground results in Large Storage swapping out the currently equipped Large Storage since one on the ground is higher integrity.
Old Large Storage is now on ground. Auto equip that one and it replaces the Medium Storage.
What I would expect:
Large storage on ground to replace the Medium Storage since it is both a stronger variant and higher integrity.
Notes
I'm not sure if this is actually a bug, it's possible it's intended behavior. It seems like the priority of "replacing the same module with lower integrity" is higher then "replace a weaker variant". I feel like it would be of more value to make replacing weaker variants a higher priority for the auto-equip.
You might then ask "what about when the stronger variant actually has lower integrity", then I guess the decision is not as clear cut. For instance, a full integrity medium storage might be of more value compared to say a 1 integrity Large Storage. In that case I think it would be fair to not auto-equip/swap. But in the currently reported instance the module on the ground was a higher integrity then both.
This isn't unique to Storage, it's just the most recent example I noticed the behavior on.
Pages: [1]