All im saying is that its not aloud which means they either get banned/warned...corruption42 wrote:....except none of it is that simple. I don't know why you think the GM's can just magically make any secure in a house over a weight limit magically flip to unsecure, with a matter of a few keystrokes. It simply doesn't work that way. As a side effect of the fact that this is related to the mechanics of how lockdowns and secures work in a house, a solution will have to be developed -- ie, programmed, tested, confirmed to not introduce new problems, deployed -- before that can happen.killaboy wrote:It'd be a lesson to learn. Deal with the game and its rules DONT expliot and it wont bite you in the ass... That simplecorruption42 wrote:I like how this is being turned into "Give me permission to exploit this as well, or give me permission to loot people on something that no policy exists for, those are the only 2 options" -- the logic on this shard is just mindblowing.killaboy wrote:Well while you guys sit back and try to figure out what to do with them more and more people going to figure it out....
If you guys just made them in "locked down" so people could loot them it would be a lesson to learn for all those non era accurate chasers and it would be solved..
Instead of the possibility of this being GF'd.
You were given an answer; its not like there's just a switch that can be flipped to make this go away, or change the status of all these containers (and selectively doing it to known ones likewise wouldn't be an option because it potentially punishes a group that is known, but no less guilty, than those who aren't known). You are talking about development changes; these things will require actual time of someone with knowledge of code sitting down to correct these things.
If you want to take the risk and try to exploit this, thats your call. Just openly recognize that there may be ramifications for it -- ramifications that you will not be told right now, because they have not been decided. Why you expect an instant response to development related questions, is simply beyond my fathoming.
No decision regarding things like this are made in haste; thats obvious by Kaivan's responses on this, the LOS bugs, or any other problem on this shard. When decisions are made in haste, and things are developed only to fix for whats directly in front of your nose, you start introducing more unexpected problems and further perpetuate problems. If instead, you take a metered response and plan things out -- treating them with the severity that a free game thats developed in peoples free time for no profit deserves -- then those complications can usually be avoided.
What do you want, a fix that is slapped together quickly to negate this bug, but also inadvertently introduces a major housing break-in exploit -- or one that takes a bit longer, but solves the problem without introducing new ones? The answer's pretty obvious.
The only reason i suggested flipping it to just "locked down" is so its known if you expliot something in game where you know its
not aloud its going to come back to bite you in the ass...