New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using crowbar to open locks #101
Comments
But you're not getting the XP! That alone is enough to stop an obsessive type. |
I'm literally breezing through SAD with just using crowbar on everything that is locked. Doing that for the whole game and never had a crit fail. Sometimes I have to use the crowbar twice, but that's as bad as it gets. Didn't even noticed diminishing xp. I'm level 14 now and seem to be doing fine. :> |
Looks like criticals don't work for stat checks, only skill checks.
But for some reason Edit: looking at CE source, it's rolling d10, then checks is |
I thought prying was added by killap as #61 said, but I checked vanilla files, and it's actually there too, so it's an original feature. |
As usual, pull a thread and the whole thing starts to unravel... Just fyi, if you pull prying changes into 1in2, the breaking algo is just something I came up with on the fly. Since pry never worked, we have some leeway in how exactly to implement it. The whole codebase needs to be reexamined for |
This isn't really a bug report, just some thoughts ...
I kinda feel like using the crowbar to open any lock makes the lockpick skill completely useless. My character has 8 STR, and since the very beginning of the game, I literally open every single lock with the first crowbar I've found in Klamath. This seems incredibility overpowered to me. If at least there would be a higher chance to fail more and damage yourself, or you destroy the crowbar, etc. it might be different, but the way it is right now, I would be stupid to not keep using it.
In a way, the game was better when using the crowbar was bugged. :D
/Edit: This SAD door is the first one that apparently can't be opened with the crowbar.
(from RPU, but I blindly assume it's the same in UPU :x )
The text was updated successfully, but these errors were encountered: