Board Thread:Wiki discussion/@comment-18014300-20200527214426/@comment-4801149-20200529010552 - Revision history

imported>RShepard227 at 05:56, 29 May 2020

2020-05-29T05:56:49Z

← Older revision		Revision as of 07:56, 29 May 2020
Line 5:		Line 5:
	Another matter, which subheadings, categories—not sure about the correct word to use—would take priority when listing all of the information in BtS? E.g. [[Captain's Chest]]—which I recall creating the page for, so it's salient to me—I made note of how the grade of the armor changes according to player action, which is gameplay information assuming the preceding logic. However, it also shares modeling with the Athenian Breastplate, which is... lore? Developer's design convention? In short, when information doesn't fit under the same "hat," and therefore requires its own, how should the proverbial hats be arranged?		Another matter, which subheadings, categories—not sure about the correct word to use—would take priority when listing all of the information in BtS? E.g. [[Captain's Chest]]—which I recall creating the page for, so it's salient to me—I made note of how the grade of the armor changes according to player action, which is gameplay information assuming the preceding logic. However, it also shares modeling with the Athenian Breastplate, which is... lore? Developer's design convention? In short, when information doesn't fit under the same "hat," and therefore requires its own, how should the proverbial hats be arranged?

	In short, I'm wondering how much of this type of information (still) qualifies, and if so, ~~how~~ to present it going forward.		In short, I'm wondering how much of this type of information (still) qualifies, and if so, the best way to present it going forward.

imported>RShepard227 at 05:56, 29 May 2020

2020-05-29T05:56:29Z

← Older revision		Revision as of 07:56, 29 May 2020
Line 5:		Line 5:
	Another matter, which subheadings, categories—not sure about the correct word to use—would take priority when listing all of the information in BtS? E.g. [[Captain's Chest]]—which I recall creating the page for, so it's salient to me—I made note of how the grade of the armor changes according to player action, which is gameplay information assuming the preceding logic. However, it also shares modeling with the Athenian Breastplate, which is... lore? Developer's design convention? In short, when information doesn't fit under the same "hat," and therefore requires its own, how should the proverbial hats be arranged?		Another matter, which subheadings, categories—not sure about the correct word to use—would take priority when listing all of the information in BtS? E.g. [[Captain's Chest]]—which I recall creating the page for, so it's salient to me—I made note of how the grade of the armor changes according to player action, which is gameplay information assuming the preceding logic. However, it also shares modeling with the Athenian Breastplate, which is... lore? Developer's design convention? In short, when information doesn't fit under the same "hat," and therefore requires its own, how should the proverbial hats be arranged?

	In short, I'm wondering how much of this (still) qualifies, and if so, how to present it going forward~~. My concern is having to discard information like this for the sake of adhering to the BtS system, or if the BtS system is just not built for it in the first place~~.		In short, I'm wondering how much of this type of information (still) qualifies, and if so, how to present it going forward.

imported>RShepard227 at 05:54, 29 May 2020

2020-05-29T05:54:45Z

← Older revision		Revision as of 07:54, 29 May 2020
Line 3:		Line 3:
	Should such information be ordered according to the moment in the memory the action takes place? And what about when an action in Memory A doesn't have an effect until realized in Memory B? Would we cite the action in Memory A as affecting Memory B at the end of A's BtS, then re-state in Memory B how Memory A affected it at the top of the order in B's BtS?		Should such information be ordered according to the moment in the memory the action takes place? And what about when an action in Memory A doesn't have an effect until realized in Memory B? Would we cite the action in Memory A as affecting Memory B at the end of A's BtS, then re-state in Memory B how Memory A affected it at the top of the order in B's BtS?

	Another matter, which subheadings, categories—not sure about the correct word to use—would take priority when listing all of the information in BtS? E.g. [[Captain's Chest]]—which I recall creating the page for, so it's salient to me—I made note of how the grade of the armor changes according to player action, which is gameplay information assuming the preceding logic. However, it also shares modeling with the Athenian Breastplate, which is... lore? Developer's design convention? In short, ~~for~~ information ~~that~~ doesn't fit under ~~that~~ same "hat," how should the proverbial hats be arranged?		Another matter, which subheadings, categories—not sure about the correct word to use—would take priority when listing all of the information in BtS? E.g. [[Captain's Chest]]—which I recall creating the page for, so it's salient to me—I made note of how the grade of the armor changes according to player action, which is gameplay information assuming the preceding logic. However, it also shares modeling with the Athenian Breastplate, which is... lore? Developer's design convention? In short, when information doesn't fit under the same "hat," and therefore requires its own, how should the proverbial hats be arranged?

	In short, I'm wondering how much of this (still) qualifies, and if so, how to present it going forward. My concern is having to discard information like this for the sake of adhering to the BtS system, or if the BtS system is just not built for it in the first place.		In short, I'm wondering how much of this (still) qualifies, and if so, how to present it going forward. My concern is having to discard information like this for the sake of adhering to the BtS system, or if the BtS system is just not built for it in the first place.

imported>RShepard227 at 01:13, 29 May 2020

2020-05-29T01:13:22Z

← Older revision		Revision as of 03:13, 29 May 2020
Line 5:		Line 5:
	Another matter, which subheadings, categories—not sure about the correct word to use—would take priority when listing all of the information in BtS? E.g. [[Captain's Chest]]—which I recall creating the page for, so it's salient to me—I made note of how the grade of the armor changes according to player action, which is gameplay information assuming the preceding logic. However, it also shares modeling with the Athenian Breastplate, which is... lore? Developer's design convention? In short, for information that doesn't fit under that same "hat," how should the proverbial hats be arranged?		Another matter, which subheadings, categories—not sure about the correct word to use—would take priority when listing all of the information in BtS? E.g. [[Captain's Chest]]—which I recall creating the page for, so it's salient to me—I made note of how the grade of the armor changes according to player action, which is gameplay information assuming the preceding logic. However, it also shares modeling with the Athenian Breastplate, which is... lore? Developer's design convention? In short, for information that doesn't fit under that same "hat," how should the proverbial hats be arranged?

	In short, I'm wondering how much of this (still) qualifies, and if so, how to present it going forward. My concern is having to discard information like this for the sake of adhering to the BtS system, or if the BtS system is just not built for it in the first place~~. If this were Origins, the politician dying would've been a simple desync and reload~~.		In short, I'm wondering how much of this (still) qualifies, and if so, how to present it going forward. My concern is having to discard information like this for the sake of adhering to the BtS system, or if the BtS system is just not built for it in the first place.

imported>RShepard227 at 01:12, 29 May 2020

2020-05-29T01:12:51Z

← Older revision		Revision as of 03:12, 29 May 2020
Line 5:		Line 5:
	Another matter, which subheadings, categories—not sure about the correct word to use—would take priority when listing all of the information in BtS? E.g. [[Captain's Chest]]—which I recall creating the page for, so it's salient to me—I made note of how the grade of the armor changes according to player action, which is gameplay information assuming the preceding logic. However, it also shares modeling with the Athenian Breastplate, which is... lore? Developer's design convention? In short, for information that doesn't fit under that same "hat," how should the proverbial hats be arranged?		Another matter, which subheadings, categories—not sure about the correct word to use—would take priority when listing all of the information in BtS? E.g. [[Captain's Chest]]—which I recall creating the page for, so it's salient to me—I made note of how the grade of the armor changes according to player action, which is gameplay information assuming the preceding logic. However, it also shares modeling with the Athenian Breastplate, which is... lore? Developer's design convention? In short, for information that doesn't fit under that same "hat," how should the proverbial hats be arranged?

	In short, I'm wondering how much of this (still) qualifies. My concern is having to discard information like this for the sake of adhering to the BtS system, or if the BtS system is just not built for it in the first place. If this were Origins, the politician dying would've been a simple desync and reload.		In short, I'm wondering how much of this (still) qualifies, and if so, how to present it going forward. My concern is having to discard information like this for the sake of adhering to the BtS system, or if the BtS system is just not built for it in the first place. If this were Origins, the politician dying would've been a simple desync and reload.

imported>RShepard227 at 01:12, 29 May 2020

2020-05-29T01:12:30Z

← Older revision		Revision as of 03:12, 29 May 2020
Line 5:		Line 5:
	Another matter, which subheadings, categories—not sure about the correct word to use—would take priority when listing all of the information in BtS? E.g. [[Captain's Chest]]—which I recall creating the page for, so it's salient to me—I made note of how the grade of the armor changes according to player action, which is gameplay information assuming the preceding logic. However, it also shares modeling with the Athenian Breastplate, which is... lore? Developer's design convention? In short, for information that doesn't fit under that same "hat," how should the proverbial hats be arranged?		Another matter, which subheadings, categories—not sure about the correct word to use—would take priority when listing all of the information in BtS? E.g. [[Captain's Chest]]—which I recall creating the page for, so it's salient to me—I made note of how the grade of the armor changes according to player action, which is gameplay information assuming the preceding logic. However, it also shares modeling with the Athenian Breastplate, which is... lore? Developer's design convention? In short, for information that doesn't fit under that same "hat," how should the proverbial hats be arranged?

	In short, I'm wondering how much of this qualifies. My concern is having to discard information like this for the sake of adhering to the BtS system, or if the BtS system is just not built for it in the first place. If this were Origins, the politician dying would've been a simple desync and reload.		In short, I'm wondering how much of this (still) qualifies. My concern is having to discard information like this for the sake of adhering to the BtS system, or if the BtS system is just not built for it in the first place. If this were Origins, the politician dying would've been a simple desync and reload.

imported>RShepard227 at 01:08, 29 May 2020

2020-05-29T01:08:04Z

← Older revision		Revision as of 03:08, 29 May 2020
Line 5:		Line 5:
	Another matter, which subheadings, categories—not sure about the correct word to use—would take priority when listing all of the information in BtS? E.g. [[Captain's Chest]]—which I recall creating the page for, so it's salient to me—I made note of how the grade of the armor changes according to player action, which is gameplay information assuming the preceding logic. However, it also shares modeling with the Athenian Breastplate, which is... lore? Developer's design convention? In short, for information that doesn't fit under that same "hat," how should the proverbial hats be arranged?		Another matter, which subheadings, categories—not sure about the correct word to use—would take priority when listing all of the information in BtS? E.g. [[Captain's Chest]]—which I recall creating the page for, so it's salient to me—I made note of how the grade of the armor changes according to player action, which is gameplay information assuming the preceding logic. However, it also shares modeling with the Athenian Breastplate, which is... lore? Developer's design convention? In short, for information that doesn't fit under that same "hat," how should the proverbial hats be arranged?

	In short, I'm wondering how much of this qualifies. My concern is having to discard information like this for the sake of adhering to the BtS system, or if the BtS system is just not built for it in the first place.		In short, I'm wondering how much of this qualifies. My concern is having to discard information like this for the sake of adhering to the BtS system, or if the BtS system is just not built for it in the first place. If this were Origins, the politician dying would've been a simple desync and reload.

imported>RShepard227: Created page with "So, while writing out dialogue, I've been writing out notes in the Trivia about how a memory's events progress depending on player actions, outside of simple dialogue choices,..."

2020-05-29T01:05:52Z

Created page with "So, while writing out dialogue, I've been writing out notes in the Trivia about how a memory's events progress depending on player actions, outside of simple dialogue choices,..."

Páàjì titun

So, while writing out dialogue, I've been writing out notes in the Trivia about how a memory's events progress depending on player actions, outside of simple dialogue choices, where the player action needs or seems to need further elaboration and cannot be adequately reduced to a tabber in the Dialogue section itself. An example, saving the politician in [[Designated Rider]] when he himself has... pretty low resilience under the right gameplay circumstances. Would this count as "gameplay information" under BtS rules?

Should such information be ordered according to the moment in the memory the action takes place? And what about when an action in Memory A doesn't have an effect until realized in Memory B? Would we cite the action in Memory A as affecting Memory B at the end of A's BtS, then re-state in Memory B how Memory A affected it at the top of the order in B's BtS?

Another matter, which subheadings, categories—not sure about the correct word to use—would take priority when listing all of the information in BtS? E.g. [[Captain's Chest]]—which I recall creating the page for, so it's salient to me—I made note of how the grade of the armor changes according to player action, which is gameplay information assuming the preceding logic. However, it also shares modeling with the Athenian Breastplate, which is... lore? Developer's design convention? In short, for information that doesn't fit under that same "hat," how should the proverbial hats be arranged?

In short, I'm wondering how much of this qualifies. My concern is having to discard information like this for the sake of adhering to the BtS system, or if the BtS system is just not built for it in the first place.