Make reusable objects with map-specific parameters in RPG Developer Bakin! Generate custom template events using this website by simply adding commentary events in your event export!
RPG Developer Bakinでマップ固有のパラメーターを持つ再利用可能なオブジェクトを作成します！イベント・エクスポートに解説イベントを追加するだけで、このウェブサイトを使用してカスタム・テンプレート・イベントを生成できます！。
Warning
Website is in BETA, a lot of features aren't supported. If you encounter bugs, please submit an issue here, or contact me on X (@MeringueRouge). Thanks, and hopefully this tool helps you out!
They're useful for creating events that need to be as reusable as a Cast object, but you need to pass on very specific parameters to each instance of the object. Without it, copying and pasting an event by hand is tedious, requires modifying multiple instances of a variable, and if you need to a fix a bug in the logic, then it'll mean that modifying one means you need to edit each and every one of them.
Castオブジェクトのように再利用可能である必要があるイベントを作成するのに便利ですが、オブジェクトの各インスタンスに非常に特定のパラメータを渡す必要があります。また、ロジックのバグを修正する必要がある場合、1つを修正することは、1つ1つを編集することを意味します。
Some kinds of use cases that work well include treasure chests, doors, and anything really that requires passing parameters on a map basis.
宝箱やドアなど、マップ単位でパラメータを渡す必要があるものであれば、どんなものでもよい。
- For most cases, add a Note (a comment) event just above the event you want to use as a parameter in your event template. The format is generally
#keyword, and using the same keyword multiple times in the same object will only create a single field in the event template. - Export the object events into a TXT, by clicking the button in the top-right.
- Load the TXT into the web tool.
- All detected keywords are shown. Edit the descriptions if needed to make it more readable, leave information for your level designers on functionality, etc.
- Before exporting, edit the export number and name, and then press export.
- Drop the downloaded file in
Program Files (x86)\Steam\steamapps\common\BAKIN\data\en\templates. You can also make it a common event template by dropping it intoProgram Files (x86)\Steam\steamapps\common\BAKIN\data\en\common_templates. - Duplicate any BMP image in the folder and rename it to the exact same name as your exported file (just as a BMP file instead). Feel free to edit it in an image editing software if needed.
- Launch Bakin, and then find a "Event" folder under the event palette.
- Place on map, fill in some properties to your liking. Double-check the template is working properly by editing it again (click on the object placed on the map twice), and convert it into a custom event, and check that the values you set were properly updated.
- ほとんどの場合、イベントテンプレートのパラメータとして使用したいイベントのすぐ上に Note（コメント）イベントを追加します。書式は一般的に
#keywordで、同じオブジェクトの中で同じキーワードを複数回使用しても、イベントテンプレートのフィールドは1つしか作成されません。 - 右上のボタンをクリックして、オブジェクトイベントをTXTにエクスポートします。
- TXTをウェブツールにロードします。
- 検出されたキーワードがすべて表示されます。必要であれば、説明を編集して、より読みやすくしたり、レベル・デザイナーのために機能に関する情報を残したりしてください。
- エクスポートする前に、エクスポート番号と名前を編集し、エクスポートを押してください。
- ダウンロードしたファイルを「Program Files (x86)」にドロップする。また、ダウンロードしたファイルを「Program Files (x86)◆Steamsteamapps◆common◆BAKIN◆data◆encommon◆templates◆」にドロップして、共通イベントテンプレートにすることもできる。
- フォルダ内の任意のBMP画像を複製して、エクスポートしたファイルと全く同じ名前にリネームする（代わりにBMPファイルとして）。必要であれば、画像編集ソフトで自由に編集してください。
- Bakinを起動し、イベントパレットの下にある "Event "フォルダを見つけます。
- マップ上に配置し、お好みでプロパティを記入してください。テンプレートが正しく動作しているか、もう一度編集して（マップ上に配置したオブジェクトを2回クリック）、カスタムイベントに変換し、設定した値が正しく更新されているか確認してください。
These events can have a "note" event placed just over the event you want to be able to change through the UI in Bakin. The format of the note must be #keyword, with keyword being any word you want that you can understand (like a variable of sorts). This will only apply to the event immediately under it.
Using unique keywords (no two keywords are the same) throughout an event will create a template UI object for each keyword.
Using the exact same keyword multiple times throughout an event and it's sheets will only result in one template UI object, but will apply to all the events concerned. Don't share the same keyword for events with different subject matters (it's fine to use the same keyword for an Increase/Decrease Item event and a Check Items Possessed event, but you can't use that same keyword for a teleport event).
これらのイベントには、BakinのUIから変更したいイベントのすぐ上に "note "イベントを置くことができます。noteのフォーマットは#keywordで、keywordはあなたが理解できる任意の単語（変数のようなもの）です。*これはその直下のイベントにのみ適用されます。
イベント全体でユニークなキーワード（2つとして同じキーワードはありません）を使用すると、キーワードごとにテンプレートUIオブジェクトが作成されます。
イベントとそのシート全体を通して、全く同じキーワードを複数回使用すると、1つのテンプレートUIオブジェクトにしかなりませんが、関係するすべてのイベントに適用されます。異なる主題を持つイベントに同じキーワードを共有しないでください（アイテムの増減イベントと所持アイテムのチェックイベントに同じキーワードを使用することは問題ありませんが、テレポートイベントに同じキーワードを使用することはできません）。
- Increase/Decrease Item / アイテムを増やす／減らす
- Check Items Possessed / 持っているアイテムの確認
Usage: Create a note just over each event that you want a template for, in the format of #keyword, with keyword being a word of your choice.
使い方： 使用方法**: テンプレートが必要な各イベントのすぐ上に、#keywordの形式でメモを作成します。
If you are only checking for a single type of item, then using the same keyword for different events will only result in one template entry on the UI. Ex: Use the same note keyword over both a Check Items Possessed Event and the Increase/Decrease Item event to check if the player has the item in question before giving said item.
アイテムの種類を1つだけチェックする場合、異なるイベントに同じキーワードを使用すると、UI上のテンプレート項目は1つになります。 例: アイテムを渡す前に、プレイヤーがアイテムを持っているかどうかをチェックするために、アイテム所持チェックイベントとアイテム増減イベントの両方で同じノートキーワードを使用します。
- Event Switch On/Off / イベントスイッチのON/OFF
- Check Event Switch / イベントスイッチの確認
Tip
The exact switches that have a #keyword do not matter, as they are replaced by the template's selection, so long as the #keywords you use make sense.
Usage: Create a note just over each event that you want a template for, in the format of #keyword, with keyword being a word of your choice.
If you are only checking for a single switch, then using the same keyword for different events will only result in one template entry on the UI. Ex: Use the same note keyword over both a Check Event Switch Event and the Event Switch On/Off event to check if the switch is on or off, before turning that same switch on or off.
- Variable Box Assignment and Calculation / 変数ボックスへの代入と計算
- Assign to String Variable / 文字列変数への代入
Usage: Create a note just over each event that you want a template for, in the format of #keyword, with keyword being a word of your choice.
Warning
This only applies to the value being assigned to a variable (user can define the value but not the variable to receive said value outside of what was defined in the event). You cannot (at this time) assign the variable box to change.
If you are only checking for a single switch, then using the same keyword for different events will only result in one template entry on the UI. Ex: Use the same note keyword over both a Check Event Switch Event and the Event Switch On/Off event to check if the switch is on or off, before turning that same switch on or off.
- Increase/Decrease Money / お金を増やす／減らす
Usage: Create a note just over each event that you want a template for, in the format of #keyword, with keyword being a word of your choice.
If you are only checking for a single switch, then using the same keyword for different events will only result in one template entry on the UI. Ex: Use the same note keyword over both a Check Event Switch Event and the Event Switch On/Off event to check if the switch is on or off, before turning that same switch on or off.
- Teleport Player / プレイヤーを他の場所に移動
- Teleport Event / イベントを瞬間移動
Usage: Create a note just over each event that you want a template for, in the format of #keyword, with keyword being a word of your choice.
Note
This will create both a map position and orientation template object on the website UI, per unique keyword. Note: In Bakin, using more than one teleport template object will result in only the last one having the map rendered. Entities will still be rendered on the other ui map.
Use the same keyword if you have multiple teleport events that need to go to the same position. Ex: Use the same note keyword over both a Check Event Switch Event and the Event Switch On/Off event to check if the switch is on or off, before turning that same switch on or off.
- Execute Battle and Check Results / バトル実行と結果の確認
Usage: Create a note just over each event that you want a template for, in the format of #keyword, with keyword being a word of your choice.
Note
This will create both an enemy and a battle map template object on the website UI, per unique keyword. Additionally, only one enemy is currently supported. To get around this without converting the event, make an enemy without a model, make a common event that runs at the start of battle checking if this modeless enemy is present, and if it is, spawn and replace the enemy with the enemies of your choice.
Use the same keyword if you have multiple events with the same encounter. However, to change background between two keyword created encounters, you'll need two different keywords.
- Display Message / メッセージを表示
Usage: Create a note just over each event that you want a template for, in the format of #keyword, with keyword being a word of your choice.
- Display Conversation / 会話を表示
Conversations are a bit more complicated to set up.
- For each character model you want to be able to replace, you'll need to create a Note event in the format of
C#keyword, with keyword being any word of your choice. - Above the conversation event, create a Note event in the format of
#keyword[CL,CR,eventL,eventR].- Replace CL with the C#keyword (without C#) for the left character in this event.
- Replace CR with the C#keyword (without C#) for the right character in this event.
- If you wish to keep the original animation assigned to the left character in this dialogue event (as the GUI offers an animation that will override this animation by default), keep eventL, otherwise delete theword but keep the structure intact (so don't delete the comma).
- If you wish to keep the original animation assigned to the right character in this dialogue event (as the GUI offers an animation that will override this animation by default), keep eventR, otherwise remove eventR.
The initial #keyword for the event will dictate the dialogue's word contents, so remember to use a different #keyword for each dialogue event, otherwise you'll have duplicate conversations.
- EventSheet Graphics
- Change Event Graphic / イベントのグラフィックを変更
Usage (EventSheet Graphics Specific): For every EventSheet (but not parallel sheets) that you want to be able to modify the graphics, but not through an event, create a note written in the format of G#keyword, with keyword being a word of your choice.
Warning
Do not place a G#keyword inside a parallel event, it will cause Bakin to convert it into a normal sheet and cause major issues for your event.
Usage (Change Event Graphic): Create a note just over each event that you want a template for, in the format of #keyword, with keyword being a word of your choice.
Only one G#keyword per eventsheet allowed. You can reuse the same G#keyword on different sheets if you want different sheets to share the same changable model.
- Switch
You can make the switches contained within an eventsheet's run conditions. Since there's no way to leave comments inside of eventsheet conditions, by default, ALL eventsheet switches are displayed on the website, and if you don't turn on the "Enable Export" button on them, they will not be turned into parameters when exported. Eventsheets conditions referring to the same switch will be merged into one template object on the website and bakin.
Important
For the website to distinguish the different switches, unlike standard events in your sheet, in which the #keyword would handle the process (thus making whatever switch you used not important), here you NEED to make sure the switches are different according to your logic (in other words, you can't use one switch for every eventsheet switch condition and replace each one individually on the website).
Unfortunately, I won't be able to support every event or element automatically, since I'm working on this tool while working on my game. However, there are a few additional things you could look into and edit the output from the editor manually to greatly improve your template events.
First, it's worth checking out the official templates' TXT files, and seeing how they're formatted. This is how I was able to use AI (Grok 3 in this case) to build out the website to automate the process in building one's own template events.
Each template event can have at the start of the TXT, before everything else, two lines that "categorize" the event.
スタンプ Stamp カテゴリ Category
I'm not sure what the Stamp label does in the engine, however, the Category will define which folder the template will appear in. For example, if I write カテゴリ Hard Magic, then the template event will be in a folder called "Hard Magic".
テンプレート定義 Title 設定ボックス 説明文 デフォルト文字列 Description 設定ID 説明 設定ボックス終了 改行 設定ボックス キャラクターグラフィック ... 設定ボックス終了 設定ボックス 文章 ... 設定ボックス終了 テンプレート定義終了
At the top of a template file, the contents of the template are defined by テンプレート定義 and end at テンプレート定義終了.
Each object on the UI are declared by 設定ボックス, followed by the type of UI element it is in japanese, and end by 設定ボックス終了.
You can reorder the order of these objects and everything inside to re-order the UI order, useful to keep elements related to the same thing closer together.