- Jul 29, 2022
- 11
- 5
Wait, what? What do you mean "see research window"?Could you remind me of one or two events where this was mentioned? As far as I've found, Syra and Melos are "sister goddesses" with Melos being the younger, more compassionate one (see research window).
Wait, WHAT? When was the lore section added? It's still greyed out for me! How do I activate it? This was never mentioned in a changelog. Did you somehow glitch your way into an unfinished section of the UI that's supposed to be blocked off?Also, I noticed the lore sections for Syra are quite empty upon starting a NG+ and I forget if they were supposed to fill out over the course of the game or if they had yet to be written.
TFW Lucette accidentally becomes an Acolyte just because she can't supress her inner nerd around a fellow nerd.Lore said:"Instead, already existing Acolytes are encouraged to tutor those who display interest or aptitude, allowing the knowledge and faith to spread out naturally through connections between people."
You know shit's good when ppl are discussing the lore and character motivations in the F95 thread.
NRFB: "But I don't want people to argue about the lore! I want them to argue about the meta!"Hey, NRFB, how does it feel to know you have fans invested enough to "um, achtually" each other over your work?
Unfortunately, no. First, I do not want to toggle filters on and off as a part of my workflow. Second, I do leave some scrolls to imprint directly, without memorization. Third,So to confirm: [potentially learnable] skills are those whose scrolls you own and skills you've memorised. However, I note that of those scrolls you own, some are either instantly blanked or instantly memorised. These are the new or [unmemorised scrolls] from the [scroll count > 0] filter, blanked or memorised depending on if you like the skill or not. Thus the remaining common denominator to what you deem [potentially learnable] I see is skills which are [memorised], and at minimum that would require a filter to [hide unmemorised].
Because after memorising or blanking your [unmemorised scrolls] via [scroll count > 0], which you doinstantlyimmediately, [hide unmemorised] should exclude all leftover undesirable skills of which there should no longer be scrolls of because you've blanked them, and instead show you all skills you have memorised including those you have scrolls of and those you have not researched. Would that be correct?
"Oh no, people think me a better writer and worldbuilder than I a gamedesigner! Oh whatever shall I do?"NRFB: "But I don't want people to argue about the lore! I want them to argue about the meta!"
Icky. Not sure how to start tracking it down though.You know shit's good when ppl are discussing the lore and character motivations in the F95 thread. Anyways I wanted to report this UI breaking bug that've consistently encountered since alpha 11, I think it happens when scrying an unexplored room.
I've started writing parts of it here and there but didn't have enough done to leave it available. You finding it is an unintentional oopsie but whatever I guess.Wait, WHAT? When was the lore section added? It's still greyed out for me! How do I activate it? This was never mentioned in a changelog. Did you somehow glitch your way into an unfinished section of the UI that's supposed to be blocked off?
...Motherfucker, there IS a glitch that lets you see the unfinished Lore section! The "Melos" and "Syra" sections of the research log are visible under certain conditions(?), but then disappear if you uncheck "show tutorial info" (which makes everything disappear) and then recheck it (which makes only the non-lore section reappear). I'm thinking that wasn't supposed to be visible yet at all. Especially since almost all of the entries are just placeholder text. "Syra: Syra. Knights: Knights." Even the last written section, High Acolytes, has some word salad in the beginning.
Sister goddesses would be an informal way of referring to them as the two deities of the Syra+Melos duotheistic structure, but there's no indication of them being actually related (if such a thing would even be possible for goddesses).No mention of them being "sister goddesses", though, just a line comparing their relative age and disposition.
This is all correct.Ahem... At any rate, the conflict in question is mentioned (at least) twice in the game and once by the dev in this thread (just pointing to one of the game instances, but with extra context). The most prominent mention is at the end of the current content for the "Experiments" route, where the knights find a book in a language they don't recognize. But the Inquisitor recognizes it as a cipher that was used during the [Name] Conflict, which he/she has studied and should be able to decipher. I'm not sure, but I think it was even mentioned that it was specifically a cipher used by Melos's followers. I don't think it's immediately clear from this dialogue that the conflict was between followers of Melos and Syra, though, so if you missed the other clue then you could easily overlook it.
The other reference is actually from camp chatter with Lucette. She mentions wanting to learn more about the followers of Melos, and is reading a book about them, but says that it's full of "pre-conflict bias". This pretty clearly hints at a conflict between Melos and Syra followers, and how their current alliance is a "post-conflict" situation. This is backed up by NRFB mentioning that "I think Lucette says something about a pre-conflict era at some point" when I was speculating on the backstory of the gods and how they might have fought against each other.
Both is fine, though on a lore scale that looks like:NRFB: "But I don't want people to argue about the lore! I want them to argue about the meta!"
Putting my vote that most of it stays here. What's already in the game is neat and pretty interesting, but I think the story would be much better served by keeping these details light and strictly to what's relevant to the gameplay. The mystique of the dungeon is what's most interesting imo, and mystique is usually more engaging than whatever the author comes up with anyway.Ideas
idk lol
Very hard disagree here. If there's one thing I hate, it's deliberately leaving questions unanswered and leaving them "up to interpretation". Speculation is only fun if there's actually the possibility of it going somewhere, and a question with no answer is just... asfdgfakds. Especially if it's on purpose. It doesn't matter if the canon answer isn't ideal.Putting my vote that most of it stays here. What's already in the game is neat and pretty interesting, but I think the story would be much better served by keeping these details light and strictly to what's relevant to the gameplay. The mystique of the dungeon is what's most interesting imo, and mystique is usually more engaging than whatever the author comes up with anyway.
So if it's possible to not reveal something, I'd recommend not doing so. Just my two cents.
Phew! So first, why aren't you willing to to use toggling as part of your workflow? Not that I think it's unreasonable or uncommon, but to me it seems so minor yet a major point for yourself that I'd like to understand more the reasoning as to why not.First, I do not want to toggle filters on and off as a part of my workflow. Second, I do leave some scrolls to imprint directly, without memorization. Third,
View attachment 2751941
What does fulfil my needs is [show memorized] and [show >0 scroll count], and then maybe some extras like [show skills with requirements fulfilled], [show skills with requirements & desires fulfilled]. But again extras are just that, extras, luxury. Minor improvements.
{skill|scroll number > 0} ∪ {skill|memorized}. This is what I'd like to see.
Putting aside the Skyrim/Elder Scrolls which I know next to nothing about, I think the Dark Souls community definitely shows there's a large number of people who appreciate the ambiguity and mystery of a writer who keeps their cards close to the chest.Very hard disagree here. If there's one thing I hate, it's deliberately leaving questions unanswered and leaving them "up to interpretation". Speculation is only fun if there's actually the possibility of it going somewhere, and a question with no answer is just... asfdgfakds. Especially if it's on purpose. It doesn't matter if the canon answer isn't ideal.
There's also a large number of people who very much do not like that, and there are definitely a lot of examples of very failed attempts at "being just like Dark Souls", but I don't want to drag out a debate on the subject for too long. I'm just casting my vote for "please, at least don't intentionally leave things ambiguous".Putting aside the Skyrim/Elder Scrolls which I know next to nothing about, I think the Dark Souls community definitely shows there's a large number of people who appreciate the ambiguity and mystery of a writer who keeps their cards close to the chest.
I think I understand what you mean by "intentional". In the popularity of the Dark Souls style of "show but don't tell," people who try to copy it think it works just as well to pretend they have a card they're not playing because they are still at surface level imitation. They don't bother thinking about what the answer behind the ambiguity is. Without that card in hand, they can't make good plays or need to be really good at bluffing, which requires experience with holding a good hand. Whereas a lot of good ambiguity only develops when the writer themselves have an answer so they can best know what to show and what to hide.I'm just casting my vote for "please, for the love of god, at least don't intentionally leave things ambiguous".
No, see, that's one thing I *don't* want to be intentionally done. But I'd rather not dwell on this subject too long, because the thought of arguing it really stresses me out. That's part of why I can't really articulate it well.I think I understand what you mean by "intentional". [...] Whereas a lot of good ambiguity only develops when the writer themselves have an answer so they can best know what to show and what to hide.
Are you trying to load an Alpha 12 or earlier save in Alpha 13? Active saves should generally be assumed to be incompatible between versions, but meta saves will still work. If you load up the save in the previous version, go to the options, and choose "abandon run", you should be able to start a NG+ in the latest version.Hello, I consistently crash while trying to load a save. This is the cfg file. I would like to provide the save file too but I do not know how to read the content to check there is no personal information first inside.
Alpha 13.1, it's a fresh run, after failing a previous run on 11 or something. You're right I should have mentioned that!Are you trying to load an Alpha 12 or earlier save in Alpha 13? Active saves should generally be assumed to be incompatible between versions, but meta saves will still work. If you load up the save in the previous version, go to the options, and choose "abandon run", you should be able to start a NG+ in the latest version.
If you started your run in Alpha 13 and still can't load it in Alpha 13, then ignore what I just said. I don't think there should be any personal data in your save file, though. The only reason I could see that happening is if the dev intentionally and maliciously set it up that way, which I highly doubt is the case.
Because I know the filter setup that gets me what I want with zero toggles. Less clicks = better.Phew! So first, why aren't you willing to to use toggling as part of your workflow
Because imprinting bypasses desires. Honestly, I consider this part well-balanced. There are three ways you can utilize a scroll, and all three have pronounced advantages and disadvantages, making them all valid.Second, why do you not memorise certain skills you would consider fit for imprinting? Wouldn't you want that skill available for the next playthrough?
Mostly to familiarize myself with what options are out there, theoretically, given a scroll is found (yeah, that is random, but still it's useful to have an idea of a build). Hence why it's an extra, it's not important.Is there a time when you would want to know [requirements & desires met] for an unmemorised skill?
I should have used the word potentially, or theoretically; my bad.did you actually mean you wanted to use a [teachable or imprintable] filter separately from {skill|scroll number > 0} ∪ {skill|memorized} on occasion?
I can't really glean anything from a cfg, as it only contains the configuration options you have selected and saved.Hello, I consistently crash while trying to load a save. This is the cfg file. I would like to provide the save file too but I do not know how to read the content to check there is no personal information first inside.
This is fair, and probably a safe decision to make. For what it's worth, I COULD list out all of the variables that are saved in the various save files, but you'd be trusting me to be honest about it.I prefer to double check, there might some stuff that is not supposed to be malicious (but that you do not want to give to random dudes) like folder location with user names, your windows language, your pc specs etc...
This doesn't actually mean very much. The experiments start cutscene can happen at the end of any floor >= 5, and whether you accept to go along with it or not, that doesn't guarantee the floor after it be the reference floor or not.EDIT: To give a bit more details: this is the floor just after accepting the witch proposal to investigate.
Should probably follow this up by saying that, if the floor itself isn't doing it but the crash is consistently happening at the beginning of the floor, then the most likely culprit is something related to the knights or the Inquisitor. In other words, some combination of skills, curses, and spells. Although, now that I think about it, you can't really check what those are, can you? Hrm.This doesn't actually mean very much. The experiments start cutscene can happen at the end of any floor >= 5, and whether you accept to go along with it or not, that doesn't guarantee the floor after it be the reference floor or not.EDIT: To give a bit more details: this is the floor just after accepting the witch proposal to investigate.
The only difference between floors is a set of data which tells the map script the details of what should be contained in that floor (You must be registered to see the links). They all access the same dungeon generation code reusing the same script, so the floor number that something happens will rarely, if ever, matter.
Thanks for both of you. It's when I click continue from the main menu, I see a black screen, hear some noises, then the app crashes. It might be trying to load a cutscene, or it is from the fact I decided to investigate the event before. As far as skills are concerned, I have a shit ton amount of lvl1 skills and non-rejected/accepted curses: this was supposed to be a quick run to try to unlock as many spells/curses/scenes as possible by deliberately letting autoplay take the wheel and get shit ton of corruption from the get go (and eventually fast loss). I stop at the camp between each floor, to check if there's some new research/memorization to do. If there is nothing to learn I barely interact with the knights, just skip time to the next floor.Should probably follow this up by saying that, if the floor itself isn't doing it but the crash is consistently happening at the beginning of the floor, then the most likely culprit is something related to the knights or the Inquisitor. In other words, some combination of skills, curses, and spells. Although, now that I think about it, you can't really check what those are, can you? Hrm.
Edit: Oh, here's a thought. Does it only happen when loading a save, or did you crash at the beginning of the floor while actively playing and then keep crashing when you tried to load? If the latter, we could attempt to reproduce this by loading up a whole suite of skills and curses and moving between floors, instead of closing out and reloading. Come to think of it, did you stop at the camp between floors as well, or progress immediately from one floor to the next? Carrying over status effects from the previous floor could matter as well.