back to a stockpile first.

• Moving of objects and zones.
  The ability to select tiles and have them deconstructed to be rebuild elsewhere. (gridtiles obviously, it includes but is not limited to floors
  having to issue two jobs and spending a lot of wasted time in between.
  They would haul the materials for the new object to the location before breaking down the old one, so that they don't have to walk

Ursprünglich geschrieben von jdtuggey:

I read OP's post but not the replies, here's my opinion after about 1200+ hours of play and exploring different mod combinations and scenario settings:

First
, then people got really defensive when I mentioned the obvious, that it is an exploit, so I had to list why it is, how it is and exploit, what is an exploit and even link some categories of exploit to

does find a way to fix the issue players could find other ways to exploit the AI, that's not to say that this isn't an exploit, it just means the dev chose a different approach, instead of playing whack
some terminology. As far as I can tell no one gives a ♥♥♥♥. There are mods that try to improve the AI or get rid of it all together, making kill boxes even more effective.

Of course it's an exploit

Transpiler
BattleLogEntry_RangedImpact.DamagedBody: TRANS: AlienRace.HarmonyPatches.BodyReferenceTranspiler
BeachMaker.Init: PRE: VanillaBiomes.VanillaBiomesPatches.BeachMaker_Prefix
Bill.PawnAllowedToStartAnew: post
Transpiler
DamageWorker_Blunt.ApplySpecialEffectsToPart: TRANS: AlienRace.HarmonyPatches.BodyReferenceTranspiler
DebugLoadIDsSavingErrorsChecker.RegisterReferenced: PRE

. Relevant? Maybe. Actually useful? Probably not.

A lot of people also seem to place a great deal of importance on being "more hardcore than hardcore" and will not hesitate to try to prove that in their
common usage of the term. When most RimWorld players discuss killboxes, they refer to a specific setup designed to exploit the AI, preventing it from finding a path into your base. These setups often

"killbox" typically refers to an area designated for the purpose of engaging enemy targets with lethal force. It's often used in the context of air operations, where aircraft are authorized to attack any
RimWorld, they may not automatically be referred to as a "killbox" unless they are part of a deliberately constructed defensive layout."


----------------------------

We should have one of those constantly

prohibited to refuse quarter (P.I, 40). An adversary who is not
or no longer able to take part in hostilities, who has surrendered
or who clearly expresses the intention of surrendering, must not
be made the
object of attack (P.I, 41, 42). A captor who lacks the
means to evacuate his prisoners must release them (P.I, 41).[/quote]
Once the enemy flees, you are not allowed to engage them. If a hostile pawn is

monitor.[/quote]
I'd recommend upping the scaling to 1.25 or 1.5 (Interface Settings). I use 1.75 personally. This should reduce mouse movement somewhat. The other part of that would be increasing your mouse
situation would you want to have areas be tracking copies of each other? How exactly are you using areas where this would be helpful? I do agree that the area management system could use an update, but I'm

viable path unless a pawn within sight uses them during the raid. They will, however, see doors as an "installed" object and can/will attack them, though, since they are not capable of "sapping."

A Sapper
effectively minimize the problem. Even so, one Event can throw all that planning into the trashbin...

So, what I'm saying is that what you're experiencing is "part of the game." It's not due to any bad play or

know enemies will walk over isn't cheesy, manipulating your base to make enemies walk over traps isn't cheesy, these are just natural and logical uses of those defensive tools. I'm not a fan of those
the placement and size of the raid. [/quote]
Like I've been saying, I'm not going to argue against common sense defenses being used as intended, a wall is fine, turrets are fine, retreating through a