# \*Line\_break vs \[n/\] **URL:** \ **Category:** ChoiceScript Help\ **Created:** [September 4, 2018, 8:30pm UTC](https://forum.choiceofgames.com/t/line-break-vs-n/43516 "2018-09-04T20:30:07Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![Fawkes](https://sea3.discourse-cdn.com/choiceofgames/user_avatar/forum.choiceofgames.com/fawkes/32/66518_2.png) [@Fawkes](https://forum.choiceofgames.com/u/Fawkes)\ **Post date:** [September 4, 2018, 8:30pm UTC](https://forum.choiceofgames.com/t/line-break-vs-n/43516/1 "2018-09-04T20:30:07Z")
So, I was looking through the startup.txt code for an official CoG game, and I noticed that for the unordered list that’s on the first page of the game, they used `[n/]` **after** each line rather than inserting a `*line_break` **under** each line. Example (from Blood Money): ``` • Play as male, female, or non-binary; gay, straight, bi, or ace.[n/] • Embrace your unearthly gifts and build connections with the dead, or banish ghosts to the underworld to protect the living[n/] • Look for love, or manipulate your friends and allies; Betray those who trust you, or maintain family loyalty no matter the cost[n/] • Fight a gang war for your family, defect to your rivals, or reject a life of crime[n/] • Negotiate volatile family relations: resolve squabbles, fall in line as a loyal lieutenant, or sharpen your knife for backstabbing[n/] • Influence citywide politics: exploit the Mayor’s office for your own ends, or use your connections for a greater cause ``` This intrigued me, so I tried it out in CSIDE with one of my open files. It works. It doesn’t need to be between lines or part of an unordered (or ordered) list, and it can be used several times in a row, like `*line_break` can. I’m wondering, what are the limits of `[n/]`? Can you forego `*line_break` entirely in favor of the shorter `[n/]`? Does anyone else use `[n/]`? Sorry if this has been asked about already. I tried searching the forums, but apparently the search function only looked for the letter “n” rather than `[n/]`. ---
**Author:** ![Szaal](https://sea3.discourse-cdn.com/choiceofgames/user_avatar/forum.choiceofgames.com/szaal/32/112202_2.png) [@Szaal](https://forum.choiceofgames.com/u/Szaal)\ **Post date:** [September 4, 2018, 8:32pm UTC](https://forum.choiceofgames.com/t/line-break-vs-n/43516/2 "2018-09-04T20:32:47Z")
[n/] all the way. AFAIK, there’s no disadvantage of [n/] over the `*line_break` except it might be harder to spot in your code. ---
**Author:** ![Fawkes](https://sea3.discourse-cdn.com/choiceofgames/user_avatar/forum.choiceofgames.com/fawkes/32/66518_2.png) [@Fawkes](https://forum.choiceofgames.com/u/Fawkes)\ **Post date:** [September 4, 2018, 8:38pm UTC](https://forum.choiceofgames.com/t/line-break-vs-n/43516/3 "2018-09-04T20:38:52Z")
Why do you think `[n/]` isn’t included in the ChoiceScript documentation on the COG website or (as far as I can tell) the Wiki? It seems like it’s far better than `*line_break`, so I’m curious as to why it’s not officially mentioned. ---
**Author:** ![MichaelCrank](https://sea3.discourse-cdn.com/choiceofgames/user_avatar/forum.choiceofgames.com/michaelcrank/32/95879_2.png) [@MichaelCrank](https://forum.choiceofgames.com/u/MichaelCrank)\ **Post date:** [September 4, 2018, 8:45pm UTC](https://forum.choiceofgames.com/t/line-break-vs-n/43516/4 "2018-09-04T20:45:58Z")
I was not aware of this. I’ll have to try that in my WIP, and thanks for the heads up! ---
**Author:** ![Szaal](https://sea3.discourse-cdn.com/choiceofgames/user_avatar/forum.choiceofgames.com/szaal/32/112202_2.png) [@Szaal](https://forum.choiceofgames.com/u/Szaal)\ **Post date:** [September 4, 2018, 9:09pm UTC](https://forum.choiceofgames.com/t/line-break-vs-n/43516/5 "2018-09-04T21:09:22Z")
Rachel is still working on the documentation of all the new features implemented thus far, which will also include the multireplace and `*implicit_control_flow`. As for the wiki, well… 😗 🎶 ---
**Author:** ![Eiwynn](https://sea3.discourse-cdn.com/choiceofgames/user_avatar/forum.choiceofgames.com/eiwynn/32/221334_2.png) [@Eiwynn](https://forum.choiceofgames.com/u/Eiwynn)\ **Post date:** [September 4, 2018, 10:57pm UTC](https://forum.choiceofgames.com/t/line-break-vs-n/43516/6 "2018-09-04T22:57:22Z")
I guess being curious is a good thing at times 🙂 ---
**Author:** ![Samuel\_H\_Young](https://sea3.discourse-cdn.com/choiceofgames/user_avatar/forum.choiceofgames.com/samuel_h_young/32/268356_2.png) [@Samuel\_H\_Young](https://forum.choiceofgames.com/u/Samuel_H_Young)\ **Post date:** [September 5, 2018, 12:29am UTC](https://forum.choiceofgames.com/t/line-break-vs-n/43516/7 "2018-09-05T00:29:38Z")
To be honest, although [n/] is technically shorter, \*line\_break seems easier and quicker to type, at least for me. ---
**Author:** ![RETowers](https://sea3.discourse-cdn.com/choiceofgames/user_avatar/forum.choiceofgames.com/retowers/32/21477_2.png) [@RETowers](https://forum.choiceofgames.com/u/RETowers)\ **Post date:** [September 5, 2018, 1:16am UTC](https://forum.choiceofgames.com/t/line-break-vs-n/43516/8 "2018-09-05T01:16:26Z")
`[n/]` is an undocumented feature (ala the purchase code and save code). It’s not actually intended for use by authors (although yea, it’s just a `
` same as `*line_break`, they’re effectively duplicate commands, do whatever, it doesn’t matter which one you use). When it comes to documentation, and general expected use though, ChoiceScript usually prioritizes being human readable and easy to learn over being highly efficient, and a `*line_break` is (for I believe most people) readily readable and easy to learn, while I doubt many people will know how to read `\n` on sight. (Or to put it another way, I’d speculate that Dan got annoyed with writing `*line_break` a bunch in between bullet points in the game descriptions and made `[n/]` to just make things simpler.) ---
**Author:** ![CJW](https://sea3.discourse-cdn.com/choiceofgames/user_avatar/forum.choiceofgames.com/cjw/32/111787_2.png) [@CJW](https://forum.choiceofgames.com/u/CJW)\ **Post date:** [September 5, 2018, 1:39am UTC](https://forum.choiceofgames.com/t/line-break-vs-n/43516/9 "2018-09-05T01:39:26Z")
He made a forum post about it a while back. IIRC the primary reason for [n/] was to allow for string values to contain line breaks (which is impossible with the line\_break command). ---
**Author:** ![RETowers](https://sea3.discourse-cdn.com/choiceofgames/user_avatar/forum.choiceofgames.com/retowers/32/21477_2.png) [@RETowers](https://forum.choiceofgames.com/u/RETowers)\ **Post date:** [September 5, 2018, 1:41am UTC](https://forum.choiceofgames.com/t/line-break-vs-n/43516/10 "2018-09-05T01:41:45Z")
Ah, makes sense. Sounds like one of the things I’d argue with Dan about. ---
**Author:** ![Chris\_Conley](https://sea3.discourse-cdn.com/choiceofgames/user_avatar/forum.choiceofgames.com/chris_conley/32/199055_2.png) [@Chris\_Conley](https://forum.choiceofgames.com/u/Chris_Conley)\ **Post date:** [September 5, 2018, 5:03am UTC](https://forum.choiceofgames.com/t/line-break-vs-n/43516/11 "2018-09-05T05:03:17Z")
Ooh. That means it could also be used inside **`@{multireplace}`**.