I preface this by saying that by list I don’t mean something like an array - a way to store variables. That’s NOT what I want.
The List I’m asking is more of a stylstic choice that’s been bothering me for some time.
The big question that interests me is how do you make a list of features, like this:
[Totally Fake ChoiceScript Game] features:
Play as any male, female, or nonbinary!
Romance Cool people!
Be a wizard or a cowboy!
The thing that interest me more are those “dots” listing individual points. They look like unordered list in HTML, but I’m not sure how to achieve a similiar effect. Are those just very small images? Or are there really just part of HTML? Is this part of COG website, or something Choice script can achieve on it’s own?
I know this won’t be very useful in actual development, but I’ve been curious, and wanted to know how this thing is made.
You can create bulleted lists using the unicode bullet symbol: • (U+2022). It’s one of those lesser-documented but useful features of CS.
For instance, this code:
*title Example
This is some normal text. This is some normal text. This is some normal text. This is some normal text.
•Play as male, female, or nonbinary!
•Romance Cool people!
•Be a wizard or a cowboy!
*ending
*title Example
This is some normal text. This is some normal text. This is some normal text. This is some normal text.
• Play as male, female, or nonbinary![n/]
• Romance Cool people![n/]
• Be a wizard or a cowboy!
*ending
Thanks! That was very helpful! I just need to know: what’s the difference between using *line_break and [n/]?
I think dashington should be able to process the former cause it’s a choice script command.
Should someone use one over the other?
They’re pretty much the same — they both insert a carriage return / line break and are both supported on DashingDon.
The main difference is [n/] can be used anywhere, even in the middle of words, while *line_break needs to be on its own line.
If I write Hello w[n/]orld it will output as:
Hello w
orld
Whereas if I use *line_break I’d need to write
Hello w
*line_break
orld
to get the same output. You can use whatever is easier for you. Though in general, it’s best to use line breaks as sparingly as possible, as they can make your game less accessible for screenreaders.
This thread has a good in-depth explanation on how whitespace works behind the scenes: