by WorkerDrone » Sun Mar 01, 2015 5:31 am
A lot of code seems to be funneled into the after effects of being shot with an arrow in these requests, it seems, but for good reason. Getting shot with an arrow should generally just SUCK ASS. But at the same time, shields should definitely block arrows. That was a component in the old engine, not the engine that came of the likes of Atonement that we're currently using today. So I'm not sure how exactly feasible that is, but it's probably semi-feasible.
And in addition to that, perhaps the amount of sheer "oh gawd arrows" doesn't need to be toned down that much. Perhaps a nerf here, a nerf there, but overall what we need when dealing with arrows are deterrents. Sure, yeah, the ability to continue roleplaying despite coming under arrow fire would be swanky, but then thinking about it, you have absurd situations where you and possibly a group of people are standing around while arrows are whizzing by, possibly having a casual conversation about something unrelated, because the level of danger has lessened enough for players to break immersion.
Because yes, when players can do something that in reality would probably be unwise but ingame can be easily gotten away with, they will typically do it without thinking. I wouldn't even necessarily blame the player, at times you need code to necessitate action in such a way that people remain motivated to both do the IC thing, and the immersing thing.
So how do you get people to still freak out about arrows, but only freak out to an EXACTING degree, a CAREFULLY calculated amount of freak out that allows them to continue roleplaying without stoppage for coded command spamming out of reflex?
The only thing I can think of is coded "breaks" or "gaps" where the code announces to everyone involved that "a something something person here is about to be shot with an arrow through the shin!" The damage doesn't happen right away, but the rolls have been done, and the arrow is in the air, and there's nothing anyone can really do to stop it from what it's going to do. When that character would be moved out of the room, bam, the damage goes through.
Any directionals, essentially, and maybe other non-emote-related commands, allowing them, and basically everyone else involved, to roleplay the situation out without thinking they have to act IMMEDIATELY or ELSE ALL IS LOST. Which is admittedly, again, a knee-jerk reaction to being shot with arrows.
Something something. I dunno. This is pointless rambling. I hate pointless rambling. Whenever Rivean did it I felt like picking on him just because. It all sounds difficult to code in, and totally not within the time-resources of the staff to implement, but it's pretty damn clear the RPI engine is not only a shit-pile, but it's a shit-pile outside the wants and even the basic demands that the community needs of it.
I hope you die right now, will you drink my chemical?
Brian wrote:See, the thing that I admire about WorkerDrone is that he's an optimist!
