You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem description:
On Crash site loot chests are hard to get because they are neutral. this means they cannot be deconstructed by the player.
Suggested solution:
When a player deconstructs the scenario checks if there are any neutral chests in deconstruction range, if there are then the chests are switched to the player force and marked for deconstruction.
Possible alternate solutions:
-chests switched to the player force when the outpost is capatured (chests might be attached by biters)
-chests switched to the player force when deconstructed by a filtered deconstruction planner (works but harder to code and harder to use)
The text was updated successfully, but these errors were encountered:
DeadlyKitten37
changed the title
crashsite loot chests cannot be deconed
crashsite loot chests cannot be deconstructed
Jul 28, 2022
I do not have a good answer for 2, but 1 is solved just by the fact the the loot cannot fit in 1 inventory, i usually take several cycles of fill my entire inventory, empty it into chests. There is also the issue that as is the loot is long and tedious to get out of the chests (mining 50+ chests interspersed only by dumping your inventory gets old very fast)
Problem description:
On Crash site loot chests are hard to get because they are neutral. this means they cannot be deconstructed by the player.
Suggested solution:
When a player deconstructs the scenario checks if there are any neutral chests in deconstruction range, if there are then the chests are switched to the player force and marked for deconstruction.
Possible alternate solutions:
-chests switched to the player force when the outpost is capatured (chests might be attached by biters)
-chests switched to the player force when deconstructed by a filtered deconstruction planner (works but harder to code and harder to use)
The text was updated successfully, but these errors were encountered: