I have strong preference against further complicating the interface of an already overcrowded screen, especially when the added function is just a shortcut, not a new feature.
This is a very relevant concern. However, if the same key functions differently during different parts of the raid, it should be communicated somehow. By the way, should S key be disconnected entirely when there's an encounter? There is no point at waiting during one, unless you want to grind your dodge, first aid and last rites.
I would just display a text message, perhaps replacing the one for a new encounter. Alternatively, don't communicate it, and make the effect subtle by having it only increase the spawn rate -- say, raise the chance of an encounter to 1/3 per turn when waiting. It's clear that wait is just stand around, but we make it much easier to recruit without waiting too long.
By the way, should S key be disconnected entirely when there's an encounter? There is no point at waiting during one, unless you want to grind your dodge, first aid and last rites.
Or perhaps you're trying to suicide your characters. I would lean toward leaving it there, and giving the player the freedom to do what they want. There's not much reason to do it, but I don't think we'd gain much by graying it out either.
I suggested earlier the possibility that waiting removes the encounter if you're pre-alarm. I actually think it would be much better if there's a 1/4 or 1/5 chance of this happening.
You don't have to act all hostile just because someone dares to raise the question and make sure that the game mechanics are logically consistent.
I apologize that I come across as hostile, or trying to discourage you from "daring to raise the question". My intent is to debate the point, not bludgeon you.
I take the civility of this forum very seriously. If I seem to be rude or insulting, please tell me. It's easier to identify it in others than myself.
Have you been paying attention? They wouldn't, because how long it takes from the site to go from "somewhat suspicious" to alarm status actually depends on a number of turns taken, not just encounter count.
This is only partially true. The site never goes into alarm based on a timer, it only goes into "conservatives suspicious" based on a timer, and that's if you've already had someone glance at you suspiciously. "Conservatives suspicious" means that your stealth actions are at sudden death; even the slightest suspicious will raise an alarm. Rushing extra encounters during this time will speed up the pace that you go to conservatives suspicious too, since additional suspicious glances from the additional encounters will rush the timer.
However, as I mentioned before, the length of this timer is quite insignificant from a gameplay standpoint. If people are glancing at you suspiciously, you'll get an alarm soon. If they aren't, you won't. How long the suspiciousness timer runs between the first and last glance isn't that big of a deal unless you're doing some kind of smash and dash site action that involves running into a secure area, doing something, and running out, with neither heavy weapons nor a disguise. This isn't relevant for recruiting, since you can stand at the entrance. Even with the smash and dash type actions, the timer could be pulled out entirely without affecting game balance greatly; it would just allow you to survive a couple extra suspicious glances before hell breaks loose.
Here is a save file:
http://www.mediafire.com/?kymkyk7u6crcebt
Can someone help me? Can someone dissolve the squads without anything crashing? Can someone figure out why the [heck] this [nice] bug happens?
Thank you!
It's very unlikely that I could fix the save file. I -might- be able to identify the bug, but despite my activity on the forum, I'm on hiatus from actual development of LCS. If another developer is interested in taking a look, my process for looking at broken saves is actually very simple, no black magic involved. I just run the game in debug mode in Visual Studio, load the save, and then crash it. Since I'm running through Visual Studio, I can do a stack trace. (Actually, I take it back, that does sound like black magic.)
Author
Topic: Bugs, UI issues and Minor Suggestions (Read 27479 times)