Era Wiki - User contributions [en]

Main Page

2019-04-18T17:55:59Z

Zergrush:

{| class="wikitable" style="text-align:center; width:100%; background:#FFE6E6"
|<div style="font-size:162%; border:0px solid #000; margin:0; padding:.1em; color:#000;">Era Games''</div>
<div style="top:+0.2em; font-size:95%;">Era games are a group of (usually) Japanese developed text porn games. Some of these games have ongoing translation and modding projects. <br /> This wiki serves as hub to get information on the individual games and various tutorials on contributing. Currently, the wiki is still a heavy WIP. <br/>
<div style="top:+0.2em; font-size:95%;"> [[Getting Started]] '''·''' <span class="plainlinks">[https://wiki.eragames.rip/index.php?title=Category:Games Games] '''·''' [[Common Issues]] '''·''' [[Contributing]] </span></div>
|}

<table style="width: 100%; margin: 2px 0px">
<tr>
<td style="vertical-align: top; width: 50%; border: 1px solid #A9A9A9; background-color:#FFFBFB; padding:10px;">

{| style="width: 100%"
! style="font-size: 120%; text-align: left; border: 1px solid #A9A9A9; background-color: #FFE6E6; padding:0.2em 0.4em"|Recent Activity
|-
| style="display: block; height: 308px; overflow-y: scroll; padding: 4px; font-size: 13px; border-spacing: 0px; padding: 2px;" | <rss max=16 highlight="community wiki foundation">https://gitgud.io/era-games.atom?feed_token=xQEHHudUqxj5yyLU2peU</rss>
|}

Check the [https://gitgud.io/groups/era-games/-/activity Activity] page for more in-depth updates.

<td/>
<td style="vertical-align: top; width: 50%; border: 1px solid #A9A9A9; background-color:#FFFBFB; padding:10px;">

{| style="width: 100%"
! style="font-size: 120%; text-align: left; border: 1px solid #A9A9A9; background-color: #FFE6E6; padding:0.2em 0.4em;"|Useful Links
|-
|

Check [[Getting Started]] if new.

* <span class="plainlinks">[https://8ch.net/hgg/res/328005.html Current 8ch Thread]
* <span class="plainlinks">[https://discord.gg/7MAArwP Discord]
* <span class="plainlinks">[https://gitgud.io/era-games Git Repository]
* <span class="plainlinks">[https://wiki.eragames.rip/bugreport.php Bug Report]
* <span class="plainlinks">[https://wiki.eragames.rip/misc/Emuera-Anchor-Sprite-Blueberry.exe Latest Anchor]


[[File:welcome.png|right|400px|:fist:]]

'''Japanese Uploads''' <br />
(User/Pass is era/era)
* <span class="plainlinks">[http://era.moe.hm/cgi/era2/upload.php General Games]
* <span class="plainlinks">[http://eratoho.dyndns.dk/cgi/up2/upload.php Touhou Games]

'''Former Japanese Uploads''' <br />
* <span class="plainlinks">[http://era.moe.hm/cgi/era/up.html General Games]
* <span class="plainlinks">[http://eratoho.dyndns.dk/cgi/up1/ Touhou Games]

|}
</td>
</tr>
</table>
<table style="width: 100%; margin: 2px 0px">
<tr>
<td style="vertical-align: top; width: 100%; border: 1px solid #A9A9A9; background-color:#FFFBFB; padding:10px;">
{| style="width: 100%"
! style="font-size: 120%; text-align: left; border: 1px solid #A9A9A9; background-color: #FFE6E6; padding:0.2em 0.4em;"|Latest builds
|-
| style="display: block; height: 308px; overflow-y: scroll; padding: 4px; font-size: 12px; border-spacing: 0px; padding: 2px;" | <dirlist sortby='timestamp'>zips</dirlist>
|}

Contributing

2019-03-15T19:22:58Z

Zergrush:

=Overview=
[[File:Settings.PNG|thumb|200px|right|Make sure the clipboard settings look like above for Chiitrans and TA to work.]]
The era translation group lacks organization by design as it removes nearly all overhead. How each game is translated depends on the maintainer, but generally five tools are used. <br />
;Git
: Git is a revision control software that lets people work on one or more files at the same time without having to deal with manually merging the changes.
;Text editor
: A program for editing text on a more advanced level than Notepad. Desired features include searching all open files, searching via REGEX etc.
;Diffing tool
: A dedicated non-git tool for comparing two or more files.
;Shift-jis converter
: Some text editors and Git clients cannot handle shift-jis very well, and converting them manually to UTF-8-BOM is unpractical.
;Translation tools
: For understanding Japanese.
Details about each section follows.
=Git=
Git revolves around repositories, with the point being that it should be possible to know exactly when a particular line in a file was modified. By viewing changes and updates on a line-by-line basis, it becomes possible for several people to work on a file without having to communicate with the others exactly what they are doing. <br />
Here are some common terms that will be used when working with git:
;Repository
: A self-contained project. A repository contains every state of a project at once.
;Branch
: A state of a project with its own diverging history. It is easy to move from one branch to another, and to merge them.
;Merge
: Merging is when the accumulated changes in one branch is applied to another. It only applies the changes not present.
;Merge conflict
: The result of two parallel commits changing one line, this requires human intervention.
;Clone
: The act of copying a repository while still maintaining references to it, so that changes applied to one can be applied to the other as well.
;Remote
: The repository a clone links to. Typically hosted online.
;Unstaged
: Pure line-by-line changes with no distinction.
;Staged
: An explicitly selected change.
;Commit
: A set of changes, typically along with a descriptive message. All staged changes are added to a commit when it is created.
;Push
: This sends all unsent commits to the remote repository.
;Pull
: This retrieves all new commits from the remote repository and merges them into the local state.
;Collaborator
: Someone with write access to a repository.
;Maintainer
: Someone in charge of handling and managing one or more repositories.

The current Git repositories are located [https://gitgud.io/era-games here]. <br />
Git can be used either via the command line or through clients. The recommended one is [https://www.gitkraken.com/ GitKraken].

=Text Editor=
There are myriad of text editors available, but the one suggested by this guide is [https://visualstudio.microsoft.com/ Visual Studio Code]. (Note: Not just Visual Studio, but Visual Studio '''Code'''.) <br />
Three plugins are recommended.
* [https://marketplace.visualstudio.com/items?itemName=streetsidesoftware.code-spell-checker Code Spell Checker] - Useful for finding spelling errors.
* [https://marketplace.visualstudio.com/items?itemName=sasami.erabasic EraBasic] - For getting highlighted text and the ability to jump to where functions are defined.
* [https://marketplace.visualstudio.com/items?itemName=eamodio.gitlens GitLens — Git supercharged] - Uses the .git folder in the game directory to tell which commit made which line, as it is done automatically it does not require linking the program to Git.

=Diffing Tool=
Git will only merge updates not already merged. Because of this external tools are needed to compare things larger in scope, for instance entire games. <br />
The recommended one is [http://kdiff3.sourceforge.net/ KDiff3]. It can be linked to GitKraken but that is not recommended as it requires further tweaking.

=Shift-jis Converter=
Era can only run files with certain encodings, two of them being Shift JIS and the other being UTF-8 BOM. The difference is that some programs like GitKraken and node.js (Visual Studio Code uses that for searching unopened files) cannot decode Shift JIS. Because of this games are converted to UTF-8 BOM instead. <br />
There are three methods.
* [https://github.com/vickyorlo/SHIFTJIS-B-Gone SHIFTJIS-B-Gone] - Python 3 script used with the command line.
* [https://gitgud.io/era-games/translation-tools/tree/c%23-shift-jis-solution/base ShiftJisFuckOff] - Pre-compiled c# executable used by dropping a folder on top of it. It is easier to use than the above one but might be incompatible with anything that is not Windows.
* Manually converting it using a text editor - As the process has to be done file-by-file it is not recommended. It does have merits though in case the above two fail.

=Translation Tools=
[[File:MTL_Guide.png|thumbnail|A quick guide to MTL. Translation Aggregator (left) and ChiiTrans (right)]]
To translate games, often more than one program is used as Japanese and English are very far apart in terms of grammar and vocabulary. Most use the clipboard to read input, meaning copied text is instantly transfered and translated to the output window.
* [https://mega.nz/#!7bQAgaCJ!D2kFihq2zQY1xG7jp5-uDnWqsO7ratKM7wZXvAV1xmc%20 Translation Aggregator] - Aggregator for translation services including Google, Bing, Yandex etc.
* [https://mega.nz/#!qpNAXC7R!hJyxXV3umjbqP7zvxR7-8kahaGGRrWgN_FhU7g8QBdM Chiitrans Lite] - Has a benefit over Translation Aggregator by linking up against [https://jisho.org jisho] and getting the definitions of words that way.
* [https://mega.nz/#!zsVgxIbZ!gAdr3d7n_rjXC-KpmgJv_7A4eRvrryESNcEAWXKljDQ ATLAS v14] - Offline dictionary for use by Chiitrans Lite or Translation Aggregator.

;Note on translating
This will need an entire page for itself, but here are a few pointers about machine translation.

* '''Never trust anything''' Just because Google Translate says something that does not make it true. This might be good enough for playing but not for translating. It is often impossible to map anything between English and Japanese 1-to-1. Some concepts and words might mean different things, several things, or might not exist.

* '''Learn the grammar''' If studied an hour per day it will take about a week or so to get to levels where Chiitrans Lite becomes helpful. Once the sentences are reduced to particles, verbs, nouns, and adjectives, translation will be easier.

* '''Learn hiragana and katakana''' Coming across "ローター" in the code and having to look that up takes time, with just katakana it becomes "rootaa" instead - rotor. Learning hiragana makes it easier to tell sentences apart at a glance - it goes from scribbles to something recognized if not known.

* '''Never use search and replace''' Just avoid it entirely, it is a dangerous tool that more easily does harm than good.

* '''Learn the Text Editor''' This involves selecting multiple lines, using REGEX, and other particularities of the program.

For a more complete guide, go here ''[[/Computer-assisted translation/]]''.

=Workflow=
[[File:Eragames Git Workflow.png|thumbnail|right|Current workflow all games are encouraged to follow.]]
Here the complete workflow is described, from Japanese updates to English releases. First each branch is described.
;game/japanese
Japanese games are released in three versions, standalone, character dialog, and patches. Unless there has been a considerable amount of time since the last standalone - months or years - the latter two are ignored.
Standalone versions contain everything required to run the game, and the latest standalone version of a game can be found in the game/japanese branch of that game.
;game/japanese-utf-8
If the game is not in UTF-8 BOM from the start it is converted and put in the game/japanese-utf-8 branch manually. The game/japanese-utf-8 branch should never be merged into another branch, nor should any branch merge into it.
;game/eng-translation
Initially a branch of game/japanese-utf-8, and should optimally contain as few modifications as possible, preferably only the text itself. Additions are not a big problem but should be commented, while removing something warrants a good reason. If something is needed for the game to make sense in English, it naturally goes here. <br />
They should contain a changelog with entries based on commits describing what has been done.
;feature/*
To change the game in ways other than pure text, feature branches are made. They are all branched off game/eng-translation and sit there self-contained until merged into eng-development. They should contain a readme or changelog describing what the feature does, how, and where.
;game/eng-development
Whenever a new update to game/eng-translation is made or a feature branch is in a ready state, they get merged into game/eng-development. But the branch itself should not contain original changes.
;game/release
When game/eng-development has been stable for a while the contents game/release is replaced with that of game/eng-development. The history of this branch should not contain any other branch.

;Japanese updates
When Japanese updates are released game/japanese and game/japanese-utf-8 are updated as listed above. Then game/japanese-utf-8 is diffed with tool into game/eng-translation. It it because tools often lack git integration that game/eng-translation should contain as few differences as possible.

'''Tips:'''
* Having a git client open to see which files and lines have been changed in game/japanese-utf-8 makes it easier to avoid diffing unnecessary files.
* Using comments like ";Custom code" also makes it clearer when to not overwrite code.
* Keeping a changelog of all new things helps, and doing that when diffing is easy.

After the game/eng-translation has been updated it is time to update game/eng-development. The problem here is that some feature branches might contradict what the update just added. To avoid having to care about backward compatibility game/eng-development is simply deleted. A new game/eng-development is then created by branching game/eng-translation and applying the feature branches to that.<br />
Should any merge conflict emerge then it can be fixed in game/eng-development if it is minor, but it would be better to fix it in the feature branch itself.

There are three separate guides, one for [http://eragames.referata.com/wiki/Contributing/GitKraken GitKraken], one for [http://eragames.referata.com/wiki/Contributing/eralang Eralang], and one for [http://eragames.referata.com/wiki/Contributing/Diffing Diffing].

'''Eralang syntax:''' Eralang syntax and basics can be found [http://eragames.referata.com/wiki/Contributing/eralang here]. Recommended to look at if it's your first time working with era.

=Setting up a new project=
The Japanese uploads are [http://eratoho.dyndns.dk/cgi/upload.php?andor=and&sword=%5B%CB%DC%C2%CE%5D&mode=ret here for touhou] and [http://era.moe.hm/cgi/era/upload.php?andor=and&sword=%5B%CB%DC%C2%CE%5D&mode=ret here for other things]. Account for both is era/era. It is there that new games are found. <br />
Generally, Namanicha will add whatever new games are uploaded to the Git, so making new projects does not make sense.

=Contributing to an ongoing project=
Begin by reading the above to understand what the process entails. Then ask in the discord.

Main Page

2019-02-24T18:24:34Z

Zergrush:

{| class="wikitable" style="text-align:center; width:100%; background:#FFE6E6"
|<div style="font-size:162%; border:0px solid #000; margin:0; padding:.1em; color:#000;">Era Games''</div>
<div style="top:+0.2em; font-size:95%;">Era games are a group of (usually) Japanese developed text porn games. Some of these games have ongoing translation and modding projects. <br /> This wiki serves as hub to get information on the individual games and various tutorials on contributing. Currently, the wiki is still a heavy WIP. <br/>
<div style="top:+0.2em; font-size:95%;"> [[Getting Started]] '''·''' <span class="plainlinks">[https://wiki.eragames.rip/index.php?title=Category:Games Games] '''·''' [[Common Issues]] '''·''' [[Contributing]] </span></div>
|}

<table style="width: 100%; margin: 2px 0px">
<tr>
<td style="vertical-align: top; width: 50%; border: 1px solid #A9A9A9; background-color:#FFFBFB; padding:10px;">

{| style="width: 100%"
! style="font-size: 120%; text-align: left; border: 1px solid #A9A9A9; background-color: #FFE6E6; padding:0.2em 0.4em"|Recent Activity
|-
| style="display: block; height: 308px; overflow-y: scroll; padding: 4px; font-size: 13px; border-spacing: 0px; padding: 2px;" | <rss max=16 highlight="community wiki foundation">https://gitgud.io/era-games.atom?feed_token=xQEHHudUqxj5yyLU2peU</rss>
|}

Check the [https://gitgud.io/groups/era-games/-/activity Activity] page for more in-depth updates.

<td/>
<td style="vertical-align: top; width: 50%; border: 1px solid #A9A9A9; background-color:#FFFBFB; padding:10px;">

{| style="width: 100%"
! style="font-size: 120%; text-align: left; border: 1px solid #A9A9A9; background-color: #FFE6E6; padding:0.2em 0.4em;"|Useful Links
|-
|

Check [[Getting Started]] if new.

* <span class="plainlinks">[https://8ch.net/hgg/res/313864.html Current 8ch Thread]
* <span class="plainlinks">[https://discord.gg/7MAArwP Discord]
* <span class="plainlinks">[https://gitgud.io/era-games Git Repository]
* <span class="plainlinks">[https://wiki.eragames.rip/bugreport.php Bug Report]
* <span class="plainlinks">[https://wiki.eragames.rip/misc/Emuera-Anchor-Sprite-Blueberry.exe Latest Anchor]


[[File:welcome.png|right|400px|:fist:]]

'''Japanese Uploads''' <br />
(User/Pass is era/era)
* <span class="plainlinks">[http://era.moe.hm/cgi/era2/upload.php General Games]
* <span class="plainlinks">[http://eratoho.dyndns.dk/cgi/up2/upload.php Touhou Games]

'''Former Japanese Uploads''' <br />
* <span class="plainlinks">[http://era.moe.hm/cgi/era/up.html General Games]
* <span class="plainlinks">[http://eratoho.dyndns.dk/cgi/up1/ Touhou Games]

|}
</td>
</tr>
</table>
<table style="width: 100%; margin: 2px 0px">
<tr>
<td style="vertical-align: top; width: 100%; border: 1px solid #A9A9A9; background-color:#FFFBFB; padding:10px;">
{| style="width: 100%"
! style="font-size: 120%; text-align: left; border: 1px solid #A9A9A9; background-color: #FFE6E6; padding:0.2em 0.4em;"|Latest builds
|-
| style="display: block; height: 308px; overflow-y: scroll; padding: 4px; font-size: 12px; border-spacing: 0px; padding: 2px;" | <dirlist sortby='filename'>zips</dirlist>
|}

Contributing

2019-01-16T11:05:03Z

Zergrush:

=Overview=
[[File:Settings.PNG|thumb|200px|right|Make sure the clipboard settings look like above for Chiitrans and TA to work.]]
The era translation group lacks organization by design as it removes nearly all overhead. How each game is translated depends on the maintainer, but generally four tools are used. <br />
;Git
: Git is a revision control software that lets people work on one or more files at the same time without having to deal with manually merging the changes.
;Text editor
: A program for editing text on a more advanced level than Notepad. Desired features include searching all open files, searching via REGEX etc.
;Diffing tool
: A dedicated non-git tool for comparing two or more files.
;Shift-jis converter
: Some text editors and Git clients cannot handle shift-jis very well, and converting them manually to UTF-8-BOM is unpractical.
;Translation tools
: For understanding Japanese.
Details about each section follows.
=Git=
Git revolves around repositories, with the point being that it should be possible to know exactly when a particular line in a file was modified. By viewing changes and updates on a line-by-line basis, it becomes possible for several people to work on a file without having to communicate with the others exactly what they are doing. <br />
Here are some common terms that will be used when working with git:
;Repository
: A self-contained project. A repository contains every state of a project at once.
;Branch
: A state of a project with its own diverging history. It is easy to move from one branch to another, and to merge them.
;Merge
: Merging is when the accumulated changes in one branch is applied to another. It only applies the changes not present.
;Merge conflict
: The result of two parallel commits changing one line, this requires human intervention.
;Clone
: The act of copying a repository while still maintaining references to it, so that changes applied to one can be applied to the other as well.
;Remote
: The repository a clone links to. Typically hosted online.
;Unstaged
: Pure line-by-line changes with no distinction.
;Staged
: An explicitly selected change.
;Commit
: A set of changes, typically along with a descriptive message. All staged changes are added to a commit when it is created.
;Push
: This sends all unsent commits to the remote repository.
;Pull
: This retrieves all new commits from the remote repository and merges them into the local state.
;Collaborator
: Someone with write access to a repository.
;Maintainer
: Someone in charge of handling and managing one or more repositories.

The current Git repositories are located [https://gitgud.io/era-games here]. <br />
Git can be used either via the command line or through clients. The recommended one is [https://www.gitkraken.com/ GitKraken].

=Text Editor=
There are myriad of text editors available, but the one suggested by this guide is [https://visualstudio.microsoft.com/ Visual Studio Code]. (Note: Not just Visual Studio, but Visual Studio '''Code'''.) <br />
Three plugins are recommended.
* [https://marketplace.visualstudio.com/items?itemName=streetsidesoftware.code-spell-checker Code Spell Checker] - Useful for finding spelling errors.
* [https://marketplace.visualstudio.com/items?itemName=sasami.erabasic EraBasic] - For getting highlighted text and the ability to jump to where functions are defined.
* [https://marketplace.visualstudio.com/items?itemName=eamodio.gitlens GitLens — Git supercharged] - Uses the .git folder in the game directory to tell which commit made which line, as it is done automatically it does not require linking the program to Git.

=Diffing Tool=
Git will only merge updates not already merged. Because of this external tools are needed to compare things larger in scope, for instance entire games. <br />
The recommended one is [http://kdiff3.sourceforge.net/ KDiff3]. It can be linked to GitKraken but that is not recommended as it requires further tweaking.

=Shift-jis Converter=
Era can only run files with certain encodings, two of them being Shift JIS and the other being UTF-8 BOM. The difference is that some programs like GitKraken and node.js (Visual Studio Code uses that for searching unopened files) cannot decode Shift JIS. Because of this games are converted to UTF-8 BOM instead. <br />
There are three methods.
* [https://github.com/vickyorlo/SHIFTJIS-B-Gone SHIFTJIS-B-Gone] - Python 3 script used with the command line.
* [https://gitgud.io/era-games/translation-tools/tree/c%23-shift-jis-solution/base ShiftJisFuckOff] - Pre-compiled c# executable used by dropping a folder on top of it. It is easier to use than the above one but might be incompatible with anything that is not Windows.
* Manually converting it using a text editor - As the process has to be done file-by-file it is not recommended. It does have merits though in case the above two fail.

=Translation Tools=
[[File:MTL_Guide.png|thumbnail|A quick guide to MTL. Translation Aggregator (left) and ChiiTrans (right)]]
To translate games, often more than one program is used as Japanese and English are very far apart in terms of grammar and vocabulary. Most use the clipboard to read input, meaning copied text is instantly transfered and translated to the output window.
* [https://mega.nz/#!7bQAgaCJ!D2kFihq2zQY1xG7jp5-uDnWqsO7ratKM7wZXvAV1xmc%20 Translation Aggregator] - Aggregator for translation services including Google, Bing, Yandex etc.
* [https://mega.nz/#!qpNAXC7R!hJyxXV3umjbqP7zvxR7-8kahaGGRrWgN_FhU7g8QBdM Chiitrans Lite] - Has a benefit over Translation Aggregator by linking up against [https://jisho.org jisho] and getting the definitions of words that way.
* [https://mega.nz/#!zsVgxIbZ!gAdr3d7n_rjXC-KpmgJv_7A4eRvrryESNcEAWXKljDQ ATLAS v14] - Offline dictionary for use by Chiitrans Lite or Translation Aggregator.

;Note on translating
This will need an entire page for itself, but here are a few pointers about machine translation.

* '''Never trust anything''' Just because Google Translate says something that does not make it true. This might be good enough for playing but not for translating. It is often impossible to map anything between English and Japanese 1-to-1. Some concepts and words might mean different things, several things, or might not exist.

* '''Learn the grammar''' If studied an hour per day it will take about a week or so to get to levels where Chiitrans Lite becomes helpful. Once the sentences are reduced to particles, verbs, nouns, and adjectives, translation will be easier.

* '''Learn hiragana and katakana''' Coming across "ローター" in the code and having to look that up takes time, with just katakana it becomes "rootaa" instead - rotor. Learning hiragana makes it easier to tell sentences apart at a glance - it goes from scribbles to something recognized if not known.

* '''Never use search and replace''' Just avoid it entirely, it is a dangerous tool that more easily does harm than good.

* '''Learn the Text Editor''' This involves selecting multiple lines, using REGEX, and other particularities of the program.

For a more complete guide, go here ''[[/Computer-assisted translation/]]''.

=Workflow=
[[File:Eragames Git Workflow.png|thumbnail|right|Current workflow all games are encouraged to follow.]]
Here the complete workflow is described, from Japanese updates to English releases. First each branch is described.
;game/japanese
Japanese games are released in three versions, standalone, character dialog, and patches. Unless there has been a considerable amount of time since the last standalone - months or years - the latter two are ignored.
Standalone versions contain everything required to run the game, and the latest standalone version of a game can be found in the game/japanese branch of that game.
;game/japanese-utf-8
If the game is not in UTF-8 BOM from the start it is converted and put in the game/japanese-utf-8 branch manually. The game/japanese-utf-8 branch should never be merged into another branch, nor should any branch merge into it.
;game/eng-translation
Initially a branch of game/japanese-utf-8, and should optimally contain as few modifications as possible, preferably only the text itself. Additions are not a big problem but should be commented, while removing something warrants a good reason. If something is needed for the game to make sense in English, it naturally goes here. <br />
They should contain a changelog with entries based on commits describing what has been done.
;feature/*
To change the game in ways other than pure text, feature branches are made. They are all branched off game/eng-translation and sit there self-contained until merged into eng-development. They should contain a readme or changelog describing what the feature does, how, and where.
;game/eng-development
Whenever a new update to game/eng-translation is made or a feature branch is in a ready state, they get merged into game/eng-development. But the branch itself should not contain original changes.
;game/release
When game/eng-development has been stable for a while the contents game/release is replaced with that of game/eng-development. The history of this branch should not contain any other branch.

;Japanese updates
When Japanese updates are released game/japanese and game/japanese-utf-8 are updated as listed above. Then game/japanese-utf-8 is diffed with tool into game/eng-translation. It it because tools often lack git integration that game/eng-translation should contain as few differences as possible.

'''Tips:'''
* Having a git client open to see which files and lines have been changed in game/japanese-utf-8 makes it easier to avoid diffing unnecessary files.
* Using comments like ";Custom code" also makes it clearer when to not overwrite code.
* Keeping a changelog of all new things helps, and doing that when diffing is easy.

After the game/eng-translation has been updated it is time to update game/eng-development. The problem here is that some feature branches might contradict what the update just added. To avoid having to care about backward compatibility game/eng-development is simply deleted. A new game/eng-development is then created by branching game/eng-translation and applying the feature branches to that.<br />
Should any merge conflict emerge then it can be fixed in game/eng-development if it is minor, but it would be better to fix it in the feature branch itself.

There are three separate guides, one for [http://eragames.referata.com/wiki/Contributing/GitKraken GitKraken], one for [http://eragames.referata.com/wiki/Contributing/eralang Eralang], and one for [http://eragames.referata.com/wiki/Contributing/Diffing Diffing].

'''Eralang syntax:''' Eralang syntax and basics can be found [http://eragames.referata.com/wiki/Contributing/eralang here]. Recommended to look at if it's your first time working with era.

=Setting up a new project=
The Japanese uploads are [http://eratoho.dyndns.dk/cgi/upload.php?andor=and&sword=%5B%CB%DC%C2%CE%5D&mode=ret here for touhou] and [http://era.moe.hm/cgi/era/upload.php?andor=and&sword=%5B%CB%DC%C2%CE%5D&mode=ret here for other things]. Account for both is era/era. It is there that new games are found. <br />
Generally, Namanicha will add whatever new games are uploaded to the Git, so making new projects does not make sense.

=Contributing to an ongoing project=
Begin by reading the above to understand what the process entails. Then ask in the discord.

Main Page

2018-12-15T22:04:39Z

Zergrush:

{| class="wikitable" style="text-align:center; width:100%; background:#FFE6E6"
|<div style="font-size:162%; border:0px solid #000; margin:0; padding:.1em; color:#000;">Era Games''</div>
<div style="top:+0.2em; font-size:95%;">Era games are a group of (usually) Japanese developed text porn games. Some of these games have ongoing translation and modding projects. <br /> This wiki serves as hub to get information on the individual games and various tutorials on contributing. Currently, the wiki is still a heavy WIP. <br/>
<div style="top:+0.2em; font-size:95%;"> [[Getting Started]] '''·''' <span class="plainlinks">[https://wiki.eragames.rip/index.php?title=Category:Games Games] '''·''' [[Common Issues]] '''·''' [[Contributing]] </span></div>
|}

<table style="width: 100%; margin: 2px 0px">
<tr>
<td style="vertical-align: top; width: 50%; border: 1px solid #A9A9A9; background-color:#FFFBFB; padding:10px;">

{| style="width: 100%"
! style="font-size: 120%; text-align: left; border: 1px solid #A9A9A9; background-color: #FFE6E6; padding:0.2em 0.4em"|Recent Activity
|-
| style="display: block; height: 308px; overflow-y: scroll; padding: 4px; font-size: 13px; border-spacing: 0px; padding: 2px;" | <rss max=16 highlight="community wiki foundation">https://gitgud.io/era-games.atom?feed_token=xQEHHudUqxj5yyLU2peU</rss>
|}

Check the [https://gitgud.io/groups/era-games/-/activity Activity] page for more in-depth updates.

<td/>
<td style="vertical-align: top; width: 50%; border: 1px solid #A9A9A9; background-color:#FFFBFB; padding:10px;">

{| style="width: 100%"
! style="font-size: 120%; text-align: left; border: 1px solid #A9A9A9; background-color: #FFE6E6; padding:0.2em 0.4em;"|Useful Links
|-
|

Check [[Getting Started]] if new.

* <span class="plainlinks">[https://8ch.net/hgg/res/280033.html Current 8ch Thread]
* <span class="plainlinks">[https://discord.gg/7MAArwP Discord]
* <span class="plainlinks">[https://gitgud.io/era-games Git Repository]
* <span class="plainlinks">[https://wiki.eragames.rip/bugreport.php Bug Report]
* <span class="plainlinks">[https://wiki.eragames.rip/misc/Emuera-Anchor-Time-Travel-Edition.exe Latest Anchor]


[[File:welcome.png|right|400px|:fist:]]

'''Japanese Uploads''' <br />
(User/Pass is era/era)
* <span class="plainlinks">[http://era.moe.hm/cgi/era2/upload.php General Games]
* <span class="plainlinks">[http://eratoho.dyndns.dk/cgi/up2/upload.php Touhou Games]

'''Former Japanese Uploads''' <br />
* <span class="plainlinks">[http://era.moe.hm/cgi/era/up.html General Games]
* <span class="plainlinks">[http://eratoho.dyndns.dk/cgi/up1/ Touhou Games]

|}
</td>
</tr>
</table>
<table style="width: 100%; margin: 2px 0px">
<tr>
<td style="vertical-align: top; width: 100%; border: 1px solid #A9A9A9; background-color:#FFFBFB; padding:10px;">
{| style="width: 100%"
! style="font-size: 120%; text-align: left; border: 1px solid #A9A9A9; background-color: #FFE6E6; padding:0.2em 0.4em;"|Latest builds
|-
| style="display: block; height: 308px; overflow-y: scroll; padding: 4px; font-size: 12px; border-spacing: 0px; padding: 2px;" | <dirlist sortby='filename'>zips</dirlist>
|}

Contributing

2018-12-05T08:02:36Z

Zergrush:

=Overview=
[[File:Settings.PNG|thumb|200px|right|Make sure the clipboard settings look like above for Chiitrans and TA to work.]]
The era translation group lacks organization by design as it removes nearly all overhead. How each game is translated depends on the maintainer, but generally four tools are used. <br />
;Git
: Git is a revision control software that lets people work on one or more files at the same time without having to deal with manually merging the changes.
;Text editor
: A program for editing text on a more advanced level than Notepad. Desired features include searching all open files, searching via REGEX etc.
;Diffing tool
: A dedicated non-git tool for comparing two or more files.
;Shift-jis converter
: Some text editors and Git clients cannot handle shift-jis very well, and converting them manually to UTF-8-BOM is unpractical.
;Translation tools
: For understanding Japanese.
Details about each section follows.
=Git=
Git revolves around repositories, with the point being that it should be possible to know exactly when a particular line in a file was modified. By viewing changes and updates on a line-by-line basis, it becomes possible for several people to work on a file without having to communicate with the others exactly what they are doing. <br />
Here are some common terms that will be used when working with git:
;Repository
: A self-contained project. A repository contains every state of a project at once.
;Branch
: A state of a project with its own diverging history. It is easy to move from one branch to another, and to merge them.
;Merge
: Merging is when the accumulated changes in one branch is applied to another. It only applies the changes not present.
;Merge conflict
: The result of two parallel commits changing one line, this requires human intervention.
;Clone
: The act of copying a repository while still maintaining references to it, so that changes applied to one can be applied to the other as well.
;Remote
: The repository a clone links to. Typically hosted online.
;Unstaged
: Pure line-by-line changes with no distinction.
;Staged
: An explicitly selected change.
;Commit
: A set of changes, typically along with a descriptive message. All staged changes are added to a commit when it is created.
;Push
: This sends all unsent commits to the remote repository.
;Pull
: This retrieves all new commits from the remote repository and merges them into the local state.
;Collaborator
: Someone with write access to a repository.
;Maintainer
: Someone in charge of handling and managing one or more repositories.

The current Git repositories are located [https://gitgud.io/era-games here]. <br />
Git can be used either via the command line or through clients. The recommended one is [https://www.gitkraken.com/ GitKraken].

=Text Editor=
There are myriad of text editors available, but the one suggested by this guide is [https://visualstudio.microsoft.com/ Visual Studio Code]. (Note: Not just Visual Studio, but Visual Studio '''Code'''.) <br />
Three plugins are recommended.
* [https://marketplace.visualstudio.com/items?itemName=streetsidesoftware.code-spell-checker Code Spell Checker] - Useful for finding spelling errors.
* [https://marketplace.visualstudio.com/items?itemName=sasami.erabasic EraBasic] - For getting highlighted text and the ability to jump to where functions are defined.
* [https://marketplace.visualstudio.com/items?itemName=eamodio.gitlens GitLens — Git supercharged] - Uses the .git folder in the game directory to tell which commit made which line, as it is done automatically it does not require linking the program to Git.

=Diffing Tool=
Git will only merge updates not already merged. Because of this external tools are needed to compare things larger in scope, for instance entire games. <br />
The recommended one is [http://kdiff3.sourceforge.net/ KDiff3]. It can be linked to GitKraken but that is not recommended as it requires further tweaking.

=Shift-jis Converter=
Era can only run files with certain encodings, two of them being Shift JIS and the other being UTF-8 BOM. The difference is that some programs like GitKraken and node.js (Visual Studio Code uses that for searching unopened files) cannot decode Shift JIS. Because of this games are converted to UTF-8 BOM instead. <br />
There are three methods.
* [https://github.com/vickyorlo/SHIFTJIS-B-Gone SHIFTJIS-B-Gone] - Python 3 script used with the command line.
* [https://gitgud.io/era-games/translation-tools/tree/c%23-shift-jis-solution/base ShiftJisFuckOff] - Pre-compiled c# executable used by dropping a folder on top of it. It is easier to use than the above one but might be incompatible with anything that is not Windows.
* Manually converting it using a text editor - As the process has to be done file-by-file it is not recommended. It does have merits though in case the above two fail.

=Translation Tools=
[[File:MTL_Guide.png|thumbnail|A quick guide to MTL. Translation Aggregator (left) and ChiiTrans (right)]]
To translate games, often more than one program is used as Japanese and English are very far apart in terms of grammar and vocabulary. Most use the clipboard to read input, meaning copied text is instantly transfered and translated to the output window.
* [https://mega.nz/#!7bQAgaCJ!D2kFihq2zQY1xG7jp5-uDnWqsO7ratKM7wZXvAV1xmc%20 Translation Aggregator] - Aggregator for translation services including Google, Bing, Yandex etc.
* [https://mega.nz/#!qpNAXC7R!hJyxXV3umjbqP7zvxR7-8kahaGGRrWgN_FhU7g8QBdM Chiitrans Lite] - Has a benefit over Translation Aggregator by linking up against [https://jisho.org jisho] and getting the definitions of words that way.
* [https://mega.nz/#!zsVgxIbZ!gAdr3d7n_rjXC-KpmgJv_7A4eRvrryESNcEAWXKljDQ ATLAS v14] - Offline dictionary for use by Chiitrans Lite or Translation Aggregator.

;Note on translating
This will need an entire page for itself, but here are a few pointers about machine translation.

* '''Never trust anything''' Just because Google Translate says something that does not make it true. This might be good enough for playing but not for translating. It is often impossible to map anything between English and Japanese 1-to-1. Some concepts and words might mean different things, several things, or might not exist.

* '''Learn the grammar''' If studied an hour per day it will take about a week or so to get to levels where Chiitrans Lite becomes helpful. Once the sentences are reduced to particles, verbs, nouns, and adjectives, translation will be easier.

* '''Learn hiragana and katakana''' Coming across "ローター" in the code and having to look that up takes time, with just katakana it becomes "rootaa" instead - rotor. Learning hiragana makes it easier to tell sentences apart at a glance - it goes from scribbles to something recognized if not known.

* '''Never use search and replace''' Just avoid it entirely, it is a dangerous tool that more easily does harm than good.

* '''Learn the Text Editor''' This involves selecting multiple lines, using REGEX, and other particularities of the program.

For a more complete guide, go here ''[[/Computer-assisted translation/]]''.

=Workflow=
[[File:Eragames Git Workflow.png|thumbnail|right|Current workflow all games are encouraged to follow.]]
Here the complete workflow is described, from Japanese updates to English releases. First each branch is described.
;game/japanese
Japanese games are released in three versions, standalone, character dialog, and patches. Unless there has been a considerable amount of time since the last standalone - months or years - the latter two are ignored.
Standalone versions contain everything required to run the game, and the latest standalone version of a game can be found in the game/japanese branch of that game.
;game/japanese-utf-8
If the game is not in UTF-8 BOM from the start it is converted and put in the game/japanese-utf-8 branch manually. The game/japanese-utf-8 branch should never be merged into another branch, nor should any branch merge into it.
;game/eng-translation
Initially a branch of game/japanese-utf-8, and should optimally contain as few modifications as possible, preferably only the text itself. Additions are not a big problem but should be commented, while removing something warrants a good reason. If something is needed for the game to make sense in English, it naturally goes here. <br />
They should contain a changelog with entries based on commits describing what has been done.
;feature/*
To change the game in ways other than pure text, feature branches are made. They are all branched off game/eng-translation and sit there self-contained until merged into eng-development. They should contain a readme or changelog describing what the feature does, how, and where.
;game/eng-development
Whenever a new update to game/eng-translation is made or a feature branch is in a ready state, they get merged into game/eng-development. But the branch itself should not contain original changes.
;game/release
When game/eng-development has been stable for a while the contents game/release is replaced with that of game/eng-development. The history of this branch should not contain any other branch.

;Japanese updates
When Japanese updates are released game/japanese and game/japanese-utf-8 are updated as listed above. Then game/japanese-utf-8 is diffed with tool into game/eng-translation. It it because tools often lack git integration that game/eng-translation should contain as few differences as possible.

'''Tips:'''
* Having a git client open to see which files and lines have been changed in game/japanese-utf-8 makes it easier to avoid diffing unnecessary files.
* Using comments like ";Custom code" also makes it clearer when to not overwrite code.
* Keeping a changelog of all new things helps, and doing that when diffing is easy.

After the game/eng-translation has been updated it is time to update game/eng-development. The problem here is that some feature branches might contradict what the update just added. To avoid having to care about backward compatibility game/eng-development is simply deleted. A new game/eng-development is then created by branching game/eng-translation and applying the feature branches to that.<br />
Should any merge conflict emerge then it can be fixed in game/eng-development if it is minor, but it would be better to fix it in the feature branch itself.

There are three separate guides, one for [http://eragames.referata.com/wiki/Contributing/GitKraken GitKraken], one for [http://eragames.referata.com/wiki/Contributing/eralang Eralang], and one for [http://eragames.referata.com/wiki/Contributing/Diffing Diffing].

'''Eralang syntax:''' Eralang syntax and basics can be found [http://eragames.referata.com/wiki/Contributing/eralang here]. Recommended to look at if it's your first time working with era.

=Setting up a new project=
The Japanese uploads are [http://eratoho.dyndns.dk/cgi/upload.php?andor=and&sword=%5B%CB%DC%C2%CE%5D&mode=ret here for touhou] and [http://era.moe.hm/cgi/era/upload.php?andor=and&sword=%5B%CB%DC%C2%CE%5D&mode=ret here for other things]. Account for both is era/era. It is there that new games are found. <br />
Generally, Zergrush will add whatever new games are uploaded to the Git, so making new projects does not make sense.

=Contributing to an ongoing project=
Begin by reading the above to understand what the process entails. Then ask in the discord.

Getting Started

2018-11-27T11:54:37Z

Zergrush:

Placeholder.

you wan at the game until it work

=== Era Games History ===

As a whole, the era games are text-based SLGs (simulation games) built around the eramaker engine. The term covers dozens of different games; most of them are built around the idea of raising and sexually training one or several girls and seem to have the most intricate sexual interfaces ever seen before in an H-game.

To understand where the differences and similarities come from, let us sit down a bit for a history lesson. In August 2003, a group known as Circle Baku released its first game called [era], a doujin game with characters from the eroge Kizuato, where the player gives sexual training to a kidnapped Kaede. It was the precursor to the era games, but it was the release of erakanon in 2005 that sparked the Japanese era games development scene.

==== Erakanon ====
Released as a free game by Circle Baku in December 2005, erakanon is a text-based game expanding on the sexual training framework of the original [era] with characters from the Kanon franchise. But most importantly, Circle Baku also freely allowed the modding and redistribution of its base engine, called eramaker. Since then, Circle Baku has released several games on its era series (although not using the eramaker engine itself, keeping to a more visual-oriented style) while the era community has maintained and created several text-based games with the eramaker engine. The Japanese community has also created an emulator for the eramaker engine called Emuera, which corrects some bugs and adds new scripting features allowing for advanced gameplay customization.

As the original eramaker engine only allowed for the modification of its CSV data files, the first fanmade games were basically versions of erakanon with different characters from different franchises. After the release of Emuera, though, the era games became quite diverse, with several different gameplay styles, including RPGs, strategy, management, raising and training simulators.
The western era games community started up in May 2016, with a thread started by the user Coold in the ULMF forums. He did a partial translation of the eraTohoK game – a strategy game with characters from the Touhou franchise. At the beginning of August that translation was posted on 8ch’s /hgg/ boards, and quickly sparked interest not only in eraTohoK itself, but in era games as a whole. Several anonymous users picked up the translation of eraTohoK and some other games, in a loosely organized but surprisingly efficient way.

=== Era Games ===
This section covers some more general info about era games. The information is not accurate for all games, but as they all share the same base they do have similarities. For instance, pretty much all trainer games have the same progression system. Feel free to skip this, but it might give some insight into why things are the way they are.

The games are divided into two sections, '''TRAIN''' and '''BASE'''. '''BASE''' is where the player can save and load, change settings etc. It's often here they go after loading. In trainers the player can buy/sell and items etc. In strategy games like TohoK most of the game takes place in '''BASE'''.<br/>
<br/>
'''TRAIN''' is where the player can actually do things, often being given a bunch of commands. There are often bars and info present to display the status of what's going on. In tohoTW every waking moment is spent in '''TRAIN'''. The important difference is that the player cannot save and load in '''TRAIN''' mode.<br/>
<br/>
This leads to '''SOURCE''', which is generated by commands in '''TRAIN'''. The most common ones across games are C Pleasure, V Pleasure etc. After an action is done, all the '''SOURCE''' is summed up and converted to '''PALAM''', probably an engrish way of saying "param(eter)". The bars present in most games depict '''PALAM''', often with game-specific levels. The amount of '''PALAM''' at the end of '''TRAIN''' creates '''GEMS''', well technically they are called "JUEL", as in jewel, but never mind that. Gems is also translated different in some games, being at times called spheres or similar.<br/>
<br/>
Gems are kept between sessions, and are used to increase '''ABL''', for instance Intimacy, or Obedience. In trainer games these are easy to see as the player is often on a deadline. But in games like TW and TohoK they are not visible. '''ABL''' sometimes need experience to increase as well, these are often generated per-command, so using handjob once gives one handjob exp.

=== First Game ===
As your first game, there are four recommended choices. [https://wiki.eragames.rip/index.php?title=EraTohoK EraTohok], [https://wiki.eragames.rip/index.php?title=EraToho_TheWorld EraTohoTW], [https://wiki.eragames.rip/index.php?title=EraTohoPM EraTohoPM], and [https://wiki.eragames.rip/index.php?title=EraMegaten EraMegaten]. Strategy (and most translated), dating sim, trainer, and RPG respectively.

EraTohoK

2018-11-27T11:53:03Z

Zergrush:

Placeholder

[[Category:Games]] [[Category:K]]

EraTohoK

2018-11-27T11:50:54Z

Zergrush: Created page with "Placeholder"

Placeholder

Getting Started

2018-11-27T11:42:06Z

Zergrush:

Placeholder.

you wan at the game until it work

=== Era Games History ===

As a whole, the era games are text-based SLGs (simulation games) built around the eramaker engine. The term covers dozens of different games; most of them are built around the idea of raising and sexually training one or several girls and seem to have the most intricate sexual interfaces ever seen before in an H-game.

To understand where the differences and similarities come from, let us sit down a bit for a history lesson. In August 2003, a group known as Circle Baku released its first game called [era], a doujin game with characters from the eroge Kizuato, where the player gives sexual training to a kidnapped Kaede. It was the precursor to the era games, but it was the release of erakanon in 2005 that sparked the Japanese era games development scene.

==== Erakanon ====
Released as a free game by Circle Baku in December 2005, erakanon is a text-based game expanding on the sexual training framework of the original [era] with characters from the Kanon franchise. But most importantly, Circle Baku also freely allowed the modding and redistribution of its base engine, called eramaker. Since then, Circle Baku has released several games on its era series (although not using the eramaker engine itself, keeping to a more visual-oriented style) while the era community has maintained and created several text-based games with the eramaker engine. The Japanese community has also created an emulator for the eramaker engine called Emuera, which corrects some bugs and adds new scripting features allowing for advanced gameplay customization.

As the original eramaker engine only allowed for the modification of its CSV data files, the first fanmade games were basically versions of erakanon with different characters from different franchises. After the release of Emuera, though, the era games became quite diverse, with several different gameplay styles, including RPGs, strategy, management, raising and training simulators.
The western era games community started up in May 2016, with a thread started by the user Coold in the ULMF forums. He did a partial translation of the eraTohoK game – a strategy game with characters from the Touhou franchise. At the beginning of August that translation was posted on 8ch’s /hgg/ boards, and quickly sparked interest not only in eraTohoK itself, but in era games as a whole. Several anonymous users picked up the translation of eraTohoK and some other games, in a loosely organized but surprisingly efficient way.

=== Era Games ===
This section covers some more general info about era games. The information is not accurate for all games, but as they all share the same base they do have similarities. For instance, pretty much all trainer games have the same progression system.

The games are divided into two sections, '''TRAIN''' and '''BASE'''. '''BASE''' is where the player can save and load, change settings etc. It's often here they go after loading. In trainers the player can buy/sell and items etc. In strategy games like TohoK most of the game takes place in '''BASE'''.<br/>
<br/>
'''TRAIN''' is where the player can actually do things, often being given a bunch of commands. There are often bars and info present to display the status of what's going on. In tohoTW every waking moment is spent in '''TRAIN'''. The important difference is that the player cannot save and load in '''TRAIN''' mode.<br/>
<br/>
This leads to '''SOURCE''', which is generated by commands in '''TRAIN'''. The most common ones across games are C Pleasure, V Pleasure etc. After an action is done, all the '''SOURCE''' is summed up and converted to '''PALAM''', probably an engrish way of saying "param(eter)". The bars present in most games depict '''PALAM''', often with game-specific levels. The amount of '''PALAM''' at the end of '''TRAIN''' creates '''GEMS''', well technically they are called "JUEL", as in jewel, but never mind that. Gems is also translated different in some games, being at times called spheres or similar.<br/>
<br/>
Gems are kept between sessions, and are used to increase '''ABL''', for instance Intimacy, or Obedience. In trainer games these are easy to see as the player is often on a deadline. But in games like TW and TohoK they are not visible. '''ABL''' sometimes need experience to increase as well, these are often generated per-command, so using handjob once gives one handjob exp.

Common Issues

2018-11-27T11:06:04Z

Zergrush: Created page with ">How do I run on linux? <br/> Wine is supposed to work. <br/> <br/> >How do I hook text?<br/> You do not hook text with era. The anchor automatically outputs text to the clipb..."

>How do I run on linux? <br/>
Wine is supposed to work. <br/>
<br/>
>How do I hook text?<br/>
You do not hook text with era. The anchor automatically outputs text to the clipboard - the place where copied text is stored. Chiitrans, TA, and others read copied text and translates it.<br/>
<br/>
>The game crashes at start.<br/>
This isn't even a question, aside from that, go scream in the discord server or in the thread. Say which game and which branch (eng-release, eng-dev, or master) it is.<br/>
<br/>
>I found a bug, wat do?<br/>
Go [https://wiki.eragames.rip/bugreport.php here] and report it please.<br/>
<br/>
>The text is misaligned.<br/>
Use Japanese locale, or scream enough, I think there exists an anchor somewhere that fixes that, but it crashes old megaten saves so there's that.

Getting Started

2018-11-27T10:57:20Z

Zergrush: Created page with "Placeholder. you wan at the game until it work === Era Games History === As a whole, the era games are text-based SLGs (simulation games) built around the eramaker engine...."

EraToho TheWorld

2018-11-27T10:53:04Z

Zergrush:

{| style="width: 13%; float:right;border:1px solid gray"
! style="font-size: 120%; text-align: center; border: 1px solid #A9A9A9; background-color: #FFE6E6; padding:0.2em 0.4em;"| [[File:Era_toho_tw_title_full.png|300px]]
eraTohoTW
|-
| Genre: Dating Simulator
|-
| Developer(s): ???
|-
| Current Version: 4.633
|-
| Translation Status: Active
|-
| [Contributors]
|-
| [https://gitgud.io/era-games/eratohoTW Repository link]
|-
| [https://wiki.eragames.rip/zips/eratohoTW-eng-dev.zip Latest development build.]
|-
| [https://wiki.eragames.rip/zips/eratohoTW-release-dev.zip Latest release build.]
|-
| [http://wiki.eragames.rip/bugreport.php?game=TW Bug reporter.]
|}
* Dating sim with Touhou character
* Time-stop mechanics
* Not a trainer
* Active translation
* Very love-focused
= Synopsis =
An open-world dating sim featuring the Touhou cast aside from some PC-98 characters. There is no set goal, nor any endings.
= Gameplay =
The game consists of two parts. The first is the sleep or home menu, here some settings can be changed, and progress can be saved. Waking up puts the player in the game proper. They can explore and walk around maps and interact with people.<br/>
More to come.
= State =
The game is being actively translated, some characters even have translated dialog. <br/>
There are two playable branches. Eng-dev and eng-release. The former is the absolute latest and is the recommended one. If that one is unplayable, try eng-release, which is just an outdated eng-dev.
[[Category:Games]] [[Category:TW]]

EraToho TheWorld

2018-11-27T10:47:29Z

Zergrush:

{| style="width: 13%; float:right;border:1px solid gray"
! style="font-size: 120%; text-align: center; border: 1px solid #A9A9A9; background-color: #FFE6E6; padding:0.2em 0.4em;"| [[File:Era_toho_tw_title_full.png|300px]]
eraTohoTW
|-
| Genre: Dating Simulator
|-
| Developer(s): ???
|-
| Current Version: 4.633
|-
| Translation Status: Active
|-
| [Contributors]
|-
| [https://gitgud.io/era-games/eratohoTW Repository link]
|-
| [http://eratoho.dyndns.dk/cgi/upload.php?andor=and&sword=eratohoPM&mode=ret Japanese Uploads]
|}
* Dating sim with Touhou character
* Time-stop mechanics
* Not a trainer
* Active translation
* Very love-focused
= Synopsis =
An open-world dating sim featuring the Touhou cast aside from some PC-98 characters. There is no set goal, nor any endings.
= Gameplay =
The game consists of two parts. The first is the sleep or home menu, here some settings can be changed, and progress can be saved. Waking up puts the player in the game proper. They can explore and walk around maps and interact with people.<br/>
More to come.
= Links =
Link to the repository is [https://gitgud.io/era-games/eratohoTW here].<br />
[https://wiki.eragames.rip/zips/eratohoTW-eng-dev.zip Latest development build.] <br />
[https://wiki.eragames.rip/zips/eratohoTW-release-dev.zip Latest release build.] <br /> <br />
To report bugs, go [http://wiki.eragames.rip/bugreport.php?game=TW here]

[[Category:Games]] [[Category:TW]]

EraToho TheWorld

2018-10-14T12:42:17Z

Zergrush:

[[File:Era_toho_tw_title_full.png|thumbnail]]
* Dating sim with Touhou character
* Time-stop mechanics
* Not a trainer
* Active translation
* Please wait warmly
Link to the repository is [https://gitgud.io/era-games/eratohoTW here].<br />
[https://wiki.eragames.rip/zips/eratohoTW-eng-dev.zip Latest development build.] <br />
[https://wiki.eragames.rip/zips/eratohoTW-release-dev.zip Latest release build.] <br /> <br />
To report bugs, go [http://wiki.eragames.rip/bugreport.php?game=TW here]

[[Category:Games]] [[Category:TW]]

Contributing

2018-10-02T15:10:36Z

Zergrush: Made formal and smaller.

=Overview=
[[File:Settings.PNG|thumb|200px|right|Make sure the clipboard settings look like above for Chiitrans and TA to work.]]
The era translation group lacks organization by design as it removes nearly all overhead. How each game is translated depends on the maintainer, but generally four tools are used. <br />
;Git
: Git is a revision control software that lets people work on one or more files at the same time without having to deal with manually merging the changes.
;Text editor
: A program for editing text on a more advanced level than Notepad. Desired features include searching all open files, searching via REGEX etc.
;Diffing tool
: A dedicated non-git tool for comparing two or more files.
;Shift-jis converter
: Some text editors and Git clients cannot handle shift-jis very well, and converting them manually to UTF-8-BOM is unpractical.
;Translation tools
: For understanding Japanese.
Details about each section follows.
=Git=
Git revolves around repositories, with the point being that it should be possible to know exactly when a particular line in a file was modified. By viewing changes and updates on a line-by-line basis, it becomes possible for several people to work on a file without having to communicate with the others exactly what they are doing. <br />
Here are some common terms that will be used when working with git:
;Repository
: A self-contained project. A repository contains every state of a project at once.
;Branch
: A state of a project with its own diverging history. It is easy to move from one branch to another, and to merge them.
;Merge
: Merging is when the accumulated changes in one branch is applied to another. It only applies the changes not present.
;Merge conflict
: The result of two parallel commits changing one line, this requires human intervention.
;Clone
: The act of copying a repository while still maintaining references to it, so that changes applied to one can be applied to the other as well.
;Remote
: The repository a clone links to. Typically hosted online.
;Unstaged
: Pure line-by-line changes with no distinction.
;Staged
: An explicitly selected change.
;Commit
: A set of changes, typically along with a descriptive message. All staged changes are added to a commit when it is created.
;Push
: This sends all unsent commits to the remote repository.
;Pull
: This retrieves all new commits from the remote repository and merges them into the local state.
;Collaborator
: Someone with write access to a repository.
;Maintainer
: Someone in charge of handling and managing one or more repositories.

The current Git repositories are located [https://gitgud.io/era-games here]. <br />
Git can be used either via the command line or through clients. The recommended one is [https://www.gitkraken.com/ GitKraken].

=Text Editor=
There are myriad of text editors available, but the one suggested by this guide is [https://visualstudio.microsoft.com/ Visual Studio Code]. (Note: Not just Visual Studio, but Visual Studio '''Code'''.) <br />
Three plugins are recommended.
* [https://marketplace.visualstudio.com/items?itemName=streetsidesoftware.code-spell-checker Code Spell Checker] - Useful for finding spelling errors.
* [https://marketplace.visualstudio.com/items?itemName=sasami.erabasic EraBasic] - For getting highlighted text and the ability to jump to where functions are defined.
* [https://marketplace.visualstudio.com/items?itemName=eamodio.gitlens GitLens — Git supercharged] - Uses the .git folder in the game directory to tell which commit made which line, as it is done automatically it does not require linking the program to Git.

=Diffing Tool=
Git will only merge updates not already merged. Because of this external tools are needed to compare things larger in scope, for instance entire games. <br />
The recommended one is [http://kdiff3.sourceforge.net/ KDiff3]. It can be linked to GitKraken but that is not recommended as it requires further tweaking.

=Shift-jis Converter=
Era can only run files with certain encodings, two of them being Shift JIS and the other being UTF-8 BOM. The difference is that some programs like GitKraken and node.js (Visual Studio Code uses that for searching unopened files) cannot decode Shift JIS. Because of this games are converted to UTF-8 BOM instead. <br />
There are three methods.
* [https://github.com/vickyorlo/SHIFTJIS-B-Gone SHIFTJIS-B-Gone] - Python 3 script used with the command line.
* [https://gitgud.io/era-games/translation-tools/tree/c%23-shift-jis-solution/base ShiftJisFuckOff] - Pre-compiled c# executable used by dropping a folder on top of it. It is easier to use than the above one but might be incompatible with anything that is not Windows.
* Manually converting it using a text editor - As the process has to be done file-by-file it is not recommended. It does have merits though in case the above two fail.

=Translation Tools=
[[File:MTL_Guide.png|thumbnail|A quick guide to MTL. Translation Aggregator (left) and ChiiTrans (right)]]
To translate games, often more than one program is used as Japanese and English are very far apart in terms of grammar and vocabulary. Most use the clipboard to read input, meaning copied text is instantly transfered and translated to the output window.
* [https://mega.nz/#!7bQAgaCJ!D2kFihq2zQY1xG7jp5-uDnWqsO7ratKM7wZXvAV1xmc%20 Translation Aggregator] - Aggregator for translation services including Google, Bing, Yandex etc.
* [https://mega.nz/#!qpNAXC7R!hJyxXV3umjbqP7zvxR7-8kahaGGRrWgN_FhU7g8QBdM Chiitrans Lite] - Has a benefit over Translation Aggregator by linking up against [https://jisho.org jisho] and getting the definitions of words that way.
* [https://mega.nz/#!zsVgxIbZ!gAdr3d7n_rjXC-KpmgJv_7A4eRvrryESNcEAWXKljDQ ATLAS v14] - Offline dictionary for use by Chiitrans Lite or Translation Aggregator.

;Note on translating
This will need an entire page for itself, but here are a few pointers about machine translation.

* '''Never trust anything''' Just because Google Translate says something that does not make it true. This might be good enough for playing but not for translating. It is often impossible to map anything between English and Japanese 1-to-1. Some concepts and words might mean different things, several things, or might not exist.

* '''Learn the grammar''' If studied an hour per day it will take about a week or so to get to levels where Chiitrans Lite becomes helpful. Once the sentences are reduced to particles, verbs, nouns, and adjectives, translation will be easier.

* '''Learn hiragana and katakana''' Coming across "ローター" in the code and having to look that up takes time, with just katakana it becomes "rootaa" instead - rotor. Learning hiragana makes it easier to tell sentences apart at a glance - it goes from scribbles to something recognized if not known.

* '''Never use search and replace''' Just avoid it entirely, it is a dangerous tool that more easily does harm than good.

* '''Learn the Text Editor''' This involves selecting multiple lines, using REGEX, and other particularities of the program.

=Workflow=
[[File:Eragames Git Workflow.png|thumbnail|right|Current workflow all games are encouraged to follow.]]
Here the complete workflow is described, from Japanese updates to English releases. First each branch is described.
;game/japanese
Japanese games are released in three versions, standalone, character dialog, and patches. Unless there has been a considerable amount of time since the last standalone - months or years - the latter two are ignored.
Standalone versions contain everything required to run the game, and the latest standalone version of a game can be found in the game/japanese branch of that game.
;game/japanese-utf-8
If the game is not in UTF-8 BOM from the start it is converted and put in the game/japanese-utf-8 branch manually. The game/japanese-utf-8 branch should never be merged into another branch, nor should any branch merge into it.
;game/eng-translation
Initially a branch of game/japanese-utf-8, and should optimally contain as few modifications as possible, preferably only the text itself. Additions are not a big problem but should be commented, while removing something warrants a good reason. If something is needed for the game to make sense in English, it naturally goes here. <br />
They should contain a changelog with entries based on commits describing what has been done.
;feature/*
To change the game in ways other than pure text, feature branches are made. They are all branched off game/eng-translation and sit there self-contained until merged into eng-development. They should contain a readme or changelog describing what the feature does, how, and where.
;game/eng-development
Whenever a new update to game/eng-translation is made or a feature branch is in a ready state, they get merged into game/eng-development. But the branch itself should not contain original changes.
;game/release
When game/eng-development has been stable for a while the contents game/release is replaced with that of game/eng-development. The history of this branch should not contain any other branch.

;Japanese updates
When Japanese updates are released game/japanese and game/japanese-utf-8 are updated as listed above. Then game/japanese-utf-8 is diffed with tool into game/eng-translation. It it because tools often lack git integration that game/eng-translation should contain as few differences as possible.

'''Tips:'''
* Having a git client open to see which files and lines have been changed in game/japanese-utf-8 makes it easier to avoid diffing unnecessary files.
* Using comments like ";Custom code" also makes it clearer when to not overwrite code.
* Keeping a changelog of all new things helps, and doing that when diffing is easy.

After the game/eng-translation has been updated it is time to update game/eng-development. The problem here is that some feature branches might contradict what the update just added. To avoid having to care about backward compatibility game/eng-development is simply deleted. A new game/eng-development is then created by branching game/eng-translation and applying the feature branches to that.<br />
Should any merge conflict emerge then it can be fixed in game/eng-development if it is minor, but it would be better to fix it in the feature branch itself.

There are three separate guides, one for [http://eragames.referata.com/wiki/Contributing/GitKraken GitKraken], one for [http://eragames.referata.com/wiki/Contributing/eralang Eralang], and one for [http://eragames.referata.com/wiki/Contributing/Diffing Diffing].

'''Eralang syntax:''' Eralang syntax and basics can be found [http://eragames.referata.com/wiki/Contributing/eralang here]. Recommended to look at if it's your first time working with era.

=Setting up a new project=
The Japanese uploads are [http://eratoho.dyndns.dk/cgi/upload.php?andor=and&sword=%5B%CB%DC%C2%CE%5D&mode=ret here for touhou] and [http://era.moe.hm/cgi/era/upload.php?andor=and&sword=%5B%CB%DC%C2%CE%5D&mode=ret here for other things]. Account for both is era/era. It is there that new games are found. <br />
Generally, Zergrush will add whatever new games are uploaded to the Git, so making new projects does not make sense.

=Contributing to an ongoing project=
Begin by reading the above to understand what the process entails. Then ask in the discord.

EraToho TheWorld

2018-10-01T16:54:37Z

Zergrush:

[[File:Era_toho_tw_title_full.png|thumbnail]]
[[Media:Test.zip]]
* Dating sim with Touhou character
* Time-stop mechanics
* Not a trainer
* Active translation
* Please wait warmly
Link to the repository is [https://gitgud.io/era-games/eratohoTW here].<br />
Direct link to latest development build as of 19/9/2018 is [https://mega.nz/#!U9hFnSxA!stSBq6IwSujCCBXpdrprQBt-sJSAvkVOdoDVADLk5FY here].
[[Category:Games]] [[Category:TW]]

File:Test.zip

2018-10-01T16:33:21Z

Zergrush:

EraToho TheWorld

2018-10-01T16:19:12Z

Zergrush:

[[File:Era_toho_tw_title_full.png|thumbnail]]
* Dating sim with Touhou character
* Time-stop mechanics
* Not a trainer
* Active translation
* Please wait warmly
Link to the repository is [https://gitgud.io/era-games/eratohoTW here].<br />
Direct link to latest development build as of 19/9/2018 is [https://mega.nz/#!U9hFnSxA!stSBq6IwSujCCBXpdrprQBt-sJSAvkVOdoDVADLk5FY here].
[[Category:Games]] [[Category:TW]]

EraToho TheWorld

2018-10-01T16:15:56Z

Zergrush: Created page with "* Dating sim with Touhou character * Time-stop mechanics * Not a trainer * Active translation * Please wait warmly Link to the repository is [https://gitgud.io/era-games/erato..."

* Dating sim with Touhou character
* Time-stop mechanics
* Not a trainer
* Active translation
* Please wait warmly
Link to the repository is [https://gitgud.io/era-games/eratohoTW here].<br />
Direct link to latest development build as of 19/9/2018 is [https://mega.nz/#!U9hFnSxA!stSBq6IwSujCCBXpdrprQBt-sJSAvkVOdoDVADLk5FY here].
[[Category:Games]] [[Category:TW]]

File:Era toho tw title full.png

2018-10-01T16:13:54Z

Zergrush:

Main Page

2018-10-01T16:09:55Z

Zergrush:

{| class="wikitable" style="text-align:center; width:100%"
|<div style="font-size:162%; border:0px solid #000; margin:0; padding:.1em; color:#000;">Era Games''</div>
<div style="top:+0.2em; font-size:95%;">'''Placeholder'''</div>
<div style="top:+0.2em; font-size:95%;">Wiki is being set up. Please wait warmly.</div>
<div style="top:+0.2em; font-size:95%;"> [[Getting Started]] '''·''' <span class="plainlinks">[https://wiki.eragames.rip/index.php?title=Category:Games Games] '''·''' [[Common Issues]] '''·''' [[Contributing]] </span></div>
|}

<strong>MediaWiki has been installed.</strong>

Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.

== Getting started ==
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]