Connection ErrorBad RequestThis page went staleSession ExpiredSign in requiredForbiddenNot FoundToo Many RequestsServer ErrorBad GatewayService UnavailableGateway TimeoutHTTP Version Not Supported
Session Expired
Your session has expired. Please log in to continue.
Sign in required
You need an account to do that. Sign in or create one — it only takes a minute.
This page went stale
Your security token was rejected, usually because the page sat open too long or you signed in elsewhere. Nothing was saved. Reload the page and try again.
Request Failed
We encountered an issue while processing your request.
Please check your internet connection and try again.
b) The assassin does not create a zone of exclusion around itself that no NPC can enter. If there is additional justification for why it moved there, then that's it, gg. Questions can only arise if the NPC made a completely meaningless move straight toward the assassin.
There is this — what prevents an invisible unit from dodging a passing NPC, I don't know. If it does prevent it, then in that case, I'll repeat once more — invisibility is useless junk. Even Kama might be more useful.
Reposition
A character can move through cells occupied by allies. In exchange for 1 AP, it can swap places with one of them.
Небо – мольбы не ждёт Небо – угроз не слышит Небо – ведёт особый счёт Небо – тебя найдёт
Guys, we've been playing by these rules for ages and Revan never metagamed with invis. You're making a mountain out of a molehill. Yes, it's unpleasant that Lester got spotted. Hard to deny. But here everything is perfectly logical as to how and why. Speaking as an invis user, I see no problems in this situation. Hell, I've also messed up with my moves in battles and just took it as it was. Relax.
There's no need to overcomplicate things. If there was a move with a heal toward the invisibility user — the heal was applied, the movement was prematurely ended, the invisibility user was revealed. Actions like "well, if that's the case, actually I moved differently" are obviously not accepted.
The issue here isn't whether he was originally going somewhere or not, but that Yashchur messed up, and in the end the player's character suffers. That's unfair.
From what was written in the thread, I understand the situation as follows:
- The character was moving to point X, which fell within the route of the NPC's next turn that led to the end of the invisibility.
- Yashchur mistakenly placed the character at point Y (because it seemed to him that he was going there), which was not part of that route, but he promptly corrected it and placed him at the originally stated point X.
If that's really how it happened, then I don't understand what the problem is. If not, then someone will have to explain what exactly the issue is.
Well, basically that's how it was. I placed Lester under Ferlutz (that's how it seemed at first). Lorican, having almost zero HP, retreats to heal in a relatively safe spot. That's a perfectly logical action. He moves in a straight line down, not in some "fancy" trajectories with the purpose of deliberately exposing Lester. He moves 8 tiles, passes by Lester, all OK. Then I saw that Lock had actually placed Lester to the right of Ferlutz, not below him as it seemed to me. And it turns out that he blocked Lorican's path, who runs into him along the way. The invisibility is revealed. I don't understand where "Yashchur wanted to win even not for himself" comes from? They're really making a mountain out of a molehill. How long has Lester been in invisibility already? How many opportunities have I had to "deliberately" expose him, knowing his real location? Yet everything was OK until now for some reason...
Ничто не возникает из ничего и ничто не пропадает бесследно. Если где-то чего-то убудет, то в другом месте добавится. (Закон сохранения).
Not to mention that even a strategically healed Lorican > removing Lester's invisibility. It's harder to find a counter for Axel with a wyvern than for a debuffed Vargas with evasion cut to zero.
No need to overcomplicate things. If there was a move with a heal toward the invisibility user — the heal was applied, the movement was prematurely ended, the invisibility user was revealed. Actions like "well, if that's the case, actually I moved differently" are obviously not accepted.
The issue here isn't whether he was initially moving somewhere or not, but that Yashchur messed up, and in the end the player's character suffers. That's unfair.
Yashchur only messed up in terms of incorrectly positioning Lester. Even if I had placed Lester where he needed to be right away, Lorican would have revealed him anyway. Because retreating to heal IN A STRAIGHT LINE, damn it, is hardly "Yashchur deliberately exposed me," sorry...
Ничто не возникает из ничего и ничто не пропадает бесследно. Если где-то чего-то убудет, то в другом месте добавится. (Закон сохранения).
And Yashchur didn't even mess up here. Loken did initially write that he was siding with Ferlyuts. Then he edited the post. Edited it before Yashchur posted the results, mind you.
And Lizard wasn't even at fault here. Loken initially did write that he was siding with Ferlyuts. Then he edited his post. He edited it before Lizard posted the results.
So that's how it is, damn it. So I wasn't imagining things at all, and Lok himself changed his mind and set himself up for exposure while I was posting the results... And now Lizard is to blame too...😡
Ничто не возникает из ничего и ничто не пропадает бесследно. Если где-то чего-то убудет, то в другом месте добавится. (Закон сохранения).
There are two problems with Locken's judgment that the battle host might deliberately expose him:
a) the GM can do this too, and aside from trusting in their integrity, there's simply no other option
b) the assassin doesn't create an exclusion zone around himself that no NPC can enter. If there's additional reasoning for why he moved there, then that's it, gg. Questions can only arise if an NPC made a completely pointless move straight at the assassin
A retreat in a straight line to heal is not a "completely pointless move straight at the assassin" meant to spite the player...
Ничто не возникает из ничего и ничто не пропадает бесследно. Если где-то чего-то убудет, то в другом месте добавится. (Закон сохранения).
And Lizard didn't even mess up here. Locken did initially write that he was siding with Ferlutz. Then he edited the post. Edited it before Lizard posted the results, mind you.
😱
Well, let's hope Lester doesn't get killed and manages to vanish into invisibility one more time.
The thing is, Lok and I had planned to take down Whitecalm carefully, from invisibility. And this threw all our plans off. I also hope Lester will hold on, but it looks like we'll have to find another way to deal with that depressed Mikujian.
Небо
Ple-Sen
