Skip to content

Commit

Permalink
fix(i18n): convert remaining Experimental to Nightly (#5463)
Browse files Browse the repository at this point in the history 
* fix(i18n): update motd to use `nightly`

* docs: use term `nightly`

* docs: increase cmake priority

* ci(i18n): wait for `Nightly Release`

* ci(i18n): run manually

* chore: do not format pnpm lockfiles

* style: deno now formats css
  • Loading branch information
@scarf005
scarf005 authored Sep 29, 2024
1 parent a0a4346 commit 975f7fb
Show file tree
Hide file tree
Showing 9 changed files with 35 additions and 34 deletions.
3 changes: 2 additions & 1 deletion .github/workflows/push-translation-template.yml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -3,8 +3,9 @@ name: "Push translation template"
concurrency: push_transifex

on:
workflow_dispatch:
workflow_run:
workflows: ["Experimental Release"]
workflows: ["Nightly Release"]
types:
- completed

Expand Down
4 changes: 2 additions & 2 deletions README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ Find a way to stop the Cataclysm ... or become one of its strongest monsters.
[![Source Code][source-badge]][source] [![Zip Archive][clone-badge]][clone]

[stable-releases]: https://github.com/cataclysmbnteam/Cataclysm-BN/releases/latest "Download stable executable"
[stable-releases-badge]: https://img.shields.io/github/v/release/cataclysmbnteam/Cataclysm-BN?style=for-the-badge&color=success&label=stable "Download experimental executable"
[stable-releases-badge]: https://img.shields.io/github/v/release/cataclysmbnteam/Cataclysm-BN?style=for-the-badge&color=success&label=stable
[all-releases]: https://github.com/cataclysmbnteam/Cataclysm-BN/releases?q=prerelease%3Atrue&expanded=true
[all-releases-badge]: https://img.shields.io/github/v/release/cataclysmbnteam/Cataclysm-BN?style=for-the-badge&color=important&label=Latest%20Release&include_prereleases&sort=date
[source]: https://github.com/cataclysmbnteam/Cataclysm-BN/archive/master.zip "The source can be downloaded as a .zip archive"
Expand All @@ -49,11 +49,11 @@ Find a way to stop the Cataclysm ... or become one of its strongest monsters.

## Building

- [with cmake](doc/src/content/docs/en/dev/guides/building/cmake.md)
- [with makefile](doc/src/content/docs/en/dev/guides/building/makefile.md): supports Linux, macOS,
and BSD.
- [with MSYS2](doc/src/content/docs/en/dev/guides/building/msys.md)
- [with vcpkg](doc/src/content/docs/en/dev/guides/building/vs_vcpkg.md)
- [with cmake](doc/src/content/docs/en/dev/guides/building/cmake.md)
- [which compilers we support](doc/src/content/docs/en/dev/reference/compiler_support.md)

Please read the [official docs](https://docs.cataclysmbn.org/en/dev/guides/building/cmake/) for
Expand Down
22 changes: 11 additions & 11 deletions data/motd/en.motd
View file
Original file line number Diff line number Diff line change
Expand Up @@ -22,29 +22,29 @@
<color_light_gray>In game you can access the options via the main menu (<color_yellow>Esc</color>).</color>

<color_light_red>******************************************************************************</color>
<color_light_red> Disclaimer for the experimental builds:</color>
<color_light_red> Disclaimer for the nightly builds:</color>
<color_light_red>******************************************************************************</color>

<color_white>Q: </color><color_yellow>What is an experimental build?</color>
<color_white>Q: </color><color_yellow>What is a nightly build?</color>

<color_white>A: </color><color_light_gray>The goal of the experimental builds is to be a second tier of quality control. It's the frontline where new content is released to be tested and balanced after initial quality control. Be aware that by choosing to play the latest experimental builds you are participating in the development process by literally playtesting the new content, and it is prone to bugs and underdeveloped features.</color>
<color_white>A: </color><color_light_gray>The goal of the nightly builds is to be a second tier of quality control. It's the frontline where new content is released to be tested and balanced after initial quality control. Be aware that by choosing to play the latest nightly builds you are participating in the development process by literally playtesting the new content, and it is prone to bugs and underdeveloped features.</color>

<color_white>Q: </color><color_yellow>Why are experimental builds even a thing?</color>
<color_white>Q: </color><color_yellow>Why are nightly builds even a thing?</color>

<color_white>A: </color><color_light_gray>Consider it like playing an alpha/beta version - bugs and underdeveloped features are part of it. Due to continuous integration rigors, experimental builds are always in a state of a constant work in progress. Experimental is a sandbox where the bug detecting and feature polishing takes place. Big and small features are constantly released to those builds to be checked for overall stability and balance. Because of that, experimentals are not under the rigor of guaranteeing balance and stability. In fact, nothing is guaranteed in the experimental builds.</color>
<color_white>A: </color><color_light_gray>Consider it like playing an alpha/beta version - bugs and underdeveloped features are part of it. Due to continuous integration rigors, nightly builds are always in a state of a constant work in progress. Nightly is a sandbox where the bug detecting and feature polishing takes place. Big and small features are constantly released to those builds to be checked for overall stability and balance. Because of that, nightlies are not under the rigor of guaranteeing balance and stability. In fact, nothing is guaranteed in the nightly builds.</color>

<color_white>Q: </color><color_yellow>Are experimental builds playable then?</color>
<color_white>Q: </color><color_yellow>Are nightly builds playable then?</color>

<color_white>A: </color><color_light_gray>Yes. But while experimental builds overall are stable, it is also not guaranteed as features may be introduced in an underdeveloped state, in parts; and may introduce bugs, including severe ones that may crash the game or corrupt savegames. It's rare, but due to the complexity of the game, the initial quality control before merging with experimental build may be inadequate, and there is always room for human error. This is why experimental builds exist in the first place.</color>
<color_white>A: </color><color_light_gray>Yes. But while nightly builds overall are stable, it is also not guaranteed as features may be introduced in an underdeveloped state, in parts; and may introduce bugs, including severe ones that may crash the game or corrupt savegames. It's rare, but due to the complexity of the game, the initial quality control before merging with nightly build may be inadequate, and there is always room for human error. This is why nightly builds exist in the first place.</color>

<color_white>Q: </color><color_yellow>Should I play experimental builds then, or stick to stable build?</color>
<color_white>Q: </color><color_yellow>Should I play nightly builds then, or stick to stable build?</color>

<color_white>A: </color><color_light_gray>The reward is instant access to the newest content, the risk is losing your game progress if a nasty bug emerges. It is always your choice to play experimental builds, with a stable build available, so play at your own discretion. You take all of the burden if something goes wrong, so be warned. Take precautions, make backups. Sometimes it's even best to postpone updating for few days until a big feature has been stabilized or a significant bug has been removed.</color>
<color_white>A: </color><color_light_gray>The reward is instant access to the newest content, the risk is losing your game progress if a nasty bug emerges. It is always your choice to play nightly builds, with a stable build available, so play at your own discretion. You take all of the burden if something goes wrong, so be warned. Take precautions, make backups. Sometimes it's even best to postpone updating for few days until a big feature has been stabilized or a significant bug has been removed.</color>

<color_white>Q: </color><color_yellow>Should I be aware of anything else?</color>

<color_white>A: </color><color_light_gray>Yes. Remember that everything you see and are about to see is potentially subject to change. All features, including newly implemented, are a work in progress and may change in the course of game development. And, as said previously, nothing is guaranteed, including balance and stability.</color>

<color_white>Q: </color><color_yellow>What if I find the risk of playing experimental build unacceptable?</color>
<color_white>Q: </color><color_yellow>What if I find the risk of playing nightly build unacceptable?</color>

<color_white>A: </color><color_light_gray>If the risk is unacceptable - play the stable version. If you are willing to take the risk - enjoy the newly added content of the experimental builds and partake in development - report bugs, submit suggestions, or even contribute your own content to the game. Good luck.</color>
<color_white>A: </color><color_light_gray>If the risk is unacceptable - play the stable version. If you are willing to take the risk - enjoy the newly added content of the nightly builds and partake in development - report bugs, submit suggestions, or even contribute your own content to the game. Good luck.</color>
22 changes: 11 additions & 11 deletions data/motd/ko.motd
View file
Original file line number Diff line number Diff line change
Expand Up @@ -23,29 +23,29 @@
<color_light_gray>메인 메뉴(<color_yellow>Esc</color>)를 통해 옵션에 접근할 수 있습니다.</color>

<color_light_red>******************************************************************************</color>
<color_light_red> 실험판에 대한 면책 사항:</color>
<color_light_red> 일일판에 대한 면책 사항:</color>
<color_light_red>******************************************************************************</color>

<color_white>Q: </color><color_yellow>실험판은 무엇인가요?</color>
<color_white>Q: </color><color_yellow>일일판은 무엇인가요?</color>

<color_white>A: </color><color_light_gray>실험판은 게임의 품질 관리중 둘째 단계 입니다. 첫 품질 관리 이후 추가된 컨텐츠들을 테스트하고 밸런스를 맞추는 단계이죠. 유의할 점은 최신 실험 빌드를 플레이하는 것은 말 그대로 베타 테스터로 개발 과정에 참여하는 것이기 때문에 버그와 미완성 컨텐츠로 가득 찰 수밖에 없다는 것입니다.</color>
<color_white>A: </color><color_light_gray>일일판은 게임의 품질 관리중 둘째 단계 입니다. 첫 품질 관리 이후 추가된 컨텐츠들을 테스트하고 밸런스를 맞추는 단계이죠. 유의할 점은 최신 실험 빌드를 플레이하는 것은 말 그대로 베타 테스터로 개발 과정에 참여하는 것이기 때문에 버그와 미완성 컨텐츠로 가득 찰 수밖에 없다는 것입니다.</color>

<color_white>Q: </color><color_yellow>대체 실험판 같은 건 왜 있는 건가요?</color>
<color_white>Q: </color><color_yellow>대체 일일판 같은 건 왜 있는 건가요?</color>

<color_white>A: </color><color_light_gray>게임의 알파나 베타 버전을 하는 거라고 생각해주세요. 미완성인 기능과 버그도 함께 들어있죠. 이런 것들을 메인 버전에 통합하려면 엄밀한 검증이 필요하기 때문에, 실험판은 영원한 개발 상태에 놓여 있다고 볼 수 있습니다. 실험판은 버그를 발견하고 기능을 갈고닦는 샌드박스 모드인 셈이죠. 크고 작은 기능들도 실험판 빌드에 끊임없이 추가되면서 안정성과 밸런스를 확인합니다. 그렇기 때문에, 실험판에서 밸런스와 안정성을 보장하지 않습니다. 사실, 실험판에서는 아무것도 보장할 수 없습니다.</color>
<color_white>A: </color><color_light_gray>게임의 알파나 베타 버전을 하는 거라고 생각해주세요. 미완성인 기능과 버그도 함께 들어있죠. 이런 것들을 메인 버전에 통합하려면 엄밀한 검증이 필요하기 때문에, 일일판은 영원한 개발 상태에 놓여 있다고 볼 수 있습니다. 일일판은 버그를 발견하고 기능을 갈고닦는 샌드박스 모드인 셈이죠. 크고 작은 기능들도 일일판 빌드에 끊임없이 추가되면서 안정성과 밸런스를 확인합니다. 그렇기 때문에, 일일판에서 밸런스와 안정성을 보장하지 않습니다. 사실, 일일판에서는 아무것도 보장할 수 없습니다.</color>

<color_white>Q: </color><color_yellow>그러면 실험판을 플레이할수는 있나요?</color>
<color_white>Q: </color><color_yellow>그러면 일일판을 플레이할수는 있나요?</color>

<color_white>A: </color><color_light_gray>네. 하지만 실험판이 전체적으로 안정적이기는 해도 새 기능들이 미완성 상태로 일부분씩 들어올 수 있습니다. 그 과정에서 게임에 크래시를 일으키거나 세이브파일을 오염시키는 심각한 버그가 생길 수 있습니다. 드문 경우이지만 첫 번째 품질 관리가 완벽하지 못했거나, 게임의 복잡도 때문에, 또는 늘 그렇듯이 인간적인 실수 때문에 생길 수 있는 일이죠. 그래서 실험판이 있는 것입니다.</color>
<color_white>A: </color><color_light_gray>네. 하지만 일일판이 전체적으로 안정적이기는 해도 새 기능들이 미완성 상태로 일부분씩 들어올 수 있습니다. 그 과정에서 게임에 크래시를 일으키거나 세이브파일을 오염시키는 심각한 버그가 생길 수 있습니다. 드문 경우이지만 첫 번째 품질 관리가 완벽하지 못했거나, 게임의 복잡도 때문에, 또는 늘 그렇듯이 인간적인 실수 때문에 생길 수 있는 일이죠. 그래서 일일판이 있는 것입니다.</color>

<color_white>Q: </color><color_yellow>그러면 실험판과 안정판 중에 어떤 것을 해야 할까요?</color>
<color_white>Q: </color><color_yellow>그러면 일일판과 안정판 중에 어떤 것을 해야 할까요?</color>

<color_white>A: </color><color_light_gray>실험판의 장점은 신규 컨텐츠에 즉각 접근할 수 있다는 것이지만 단점은 심각한 버그로 게임 진행사항을 날릴 수 있다는 것입니다. 안정판이 있는 상황에서, 실험판을 하는 것은 여러분의 선택이니 충분한 고민 후에 결정해주세요. 선택은 여러분이 한 것이기 때문에 개발팀에서는 책임을 질 수 없습니다! 시작하기 전에 백업을 만들어두세요. 때로는 대규모 기능이 안정화되거나 큰 버그가 해결될 때까지 업데이트를 며칠 미루는 것이 나을 수도 있습니다.</color>
<color_white>A: </color><color_light_gray>일일판의 장점은 신규 컨텐츠에 즉각 접근할 수 있다는 것이지만 단점은 심각한 버그로 게임 진행사항을 날릴 수 있다는 것입니다. 안정판이 있는 상황에서, 일일판을 하는 것은 여러분의 선택이니 충분한 고민 후에 결정해주세요. 선택은 여러분이 한 것이기 때문에 개발팀에서는 책임을 질 수 없습니다! 시작하기 전에 백업을 만들어두세요. 때로는 대규모 기능이 안정화되거나 큰 버그가 해결될 때까지 업데이트를 며칠 미루는 것이 나을 수도 있습니다.</color>

<color_white>Q: </color><color_yellow>그밖에 더 알아야 할 것이 있을까요?</color>

<color_white>A: </color><color_light_gray>네. 지금 보고, 볼 모든 것들이 변경될 여지가 있습니다. 새로 추가된 것들을 포함한 모든 기능들은 작업 중인 상태이기 때문에 개발 중에 언제건 변경될수 있습니다. 앞서 이야기했지만, 밸런스와 안정성을 포함해 어떤 것도 수정될 수 있습니다.</color>

<color_white>Q: </color><color_yellow>실험판이 너무 위험해서 하지 못하겠다면요?</color>
<color_white>Q: </color><color_yellow>일일판이 너무 위험해서 하지 못하겠다면요?</color>

<color_white>A: </color><color_light_gray>너무 위험한 것 같다면 안정판을 해주세요. 하지만 위험을 감수할 수 있다면 실험판의 새 컨텐츠를 즐기고 개발 과정에 참여해주세요. 버그 제보, 건의사항 요청, 여러분의 컨텐츠를 게임에 추가할 수도 있습니다. 행운을 빕니다.</color>
<color_white>A: </color><color_light_gray>너무 위험한 것 같다면 안정판을 해주세요. 하지만 위험을 감수할 수 있다면 일일판의 새 컨텐츠를 즐기고 개발 과정에 참여해주세요. 버그 제보, 건의사항 요청, 여러분의 컨텐츠를 게임에 추가할 수도 있습니다. 행운을 빕니다.</color>
2 changes: 1 addition & 1 deletion deno.jsonc
View file
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@
"test": { "include": ["scripts"] },
"lint": { "include": ["scripts"] },
"fmt": {
"exclude": ["doc/dist", "doc/.astro"],
"exclude": ["doc/dist", "doc/.astro", "pnpm-lock.yaml"],
"include": ["scripts", "doc", "*.md"],
"semiColons": false,
"lineWidth": 100
Expand Down
2 changes: 1 addition & 1 deletion doc/src/content/docs/en/contribute/issues.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ Your bug report may include:

Bonus points for:

- Checking if the bug exists under latest experimental build
- Checking if the bug exists under latest nightly build
- Checking if it is OS specific

The OS and BN version are very important - with the pace of changes here it is possible the bug you
Expand Down
6 changes: 3 additions & 3 deletions doc/src/content/docs/en/dev/guides/building/makefile.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ You have three major choices here: GCC, Clang and MXE.

- GCC is almost always the default on Linux systems so it's likely you already have it
- Clang is usually faster than GCC, so it's worth installing if you plan to keep up with the latest
experimentals
nightlies.
- MXE is a cross-compiler, so of any importance only if you plan to compile for Windows on your
Linux machine

Expand Down Expand Up @@ -47,8 +47,8 @@ you go (if any).

Besides the essentials you will need `git`.

If you plan on keeping up with experimentals you should also install `ccache`, which will
considerably speed-up partial builds.
If you plan on keeping up with nightlies you should also install `ccache`, which will considerably
speed-up partial builds.

## Dependencies

Expand Down
6 changes: 3 additions & 3 deletions doc/src/styles/capitalize.css
View file
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
details summary>h2.large,
details li>a>span,
details summary > h2.large,
details li > a > span,
main h1,
aside>p {
aside > p {
text-transform: capitalize;
}
2 changes: 1 addition & 1 deletion doc/src/styles/theme.css
View file
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@
}

/* Light mode colors. */
:root[data-theme='light'] {
:root[data-theme="light"] {
--sl-color-accent-low: #d7d7d7;
--sl-color-accent: #6b6b6b;
--sl-color-accent-high: #323232;
Expand Down

0 comments on commit 975f7fb

Please sign in to comment.