Don't close the door on Uglúk, the uruk!
Collapse
X
-
NPC Intelligence: the NPC would need to know that it's a door, and the fact that the door hinders the NPC in reaching the player on the other side. The higher the intelligence stat for the NPC, the faster it will try to bash down the door if it's either shut with spikes or simply closed.
NPC Strength: the stronger the NPC, the easier it is for it to bash down the door.Comment
-
Then there are swarm monsters like fire ants that probably would eat their way thru the door rather than bash it.Comment
-
Easy solution to this problem. Give doors a small (1-5%) chance of breaking when being opened. This way, any kind of strategy that relies upon repeatedly opening and closing doors will fail after awhile, but random doors won't break too often.
This is like Fizzix's plan without requiring that monsters that open doors also be able to bash them down.
And it subscribes to my "all actions should have some chance of failure or alternate outcome" ethos.Comment
-
Maybe separate open command that doesn't move you, and open with movement (like just walking in it like if it isn't there). If the door is locked then open with movement wouldn't work.Comment
-
I guess all the snagas are running around fixing doors when they aren't busy cringing from bright lights.Comment
-
One way to solve this is to make opening door make you step in it, and same for monsters. That would be a bit risky though, because you do not know what is at other side of the door.
Maybe separate open command that doesn't move you, and open with movement (like just walking in it like if it isn't there). If the door is locked then open with movement wouldn't work.Comment
-
Or give the monster/npc a % chance to step into the doorframe everytime it opens a door and/or a % chance it will step into the doorframe if standing next to a door being opened by the player?http://www.rpgartkits.com/
Fantasy art kits for personal and commercial use. Commercial use requires a Developer license, also available through my website.Comment
Comment