![[PukiWiki]](./skin/BAKIN_logo_92.png "[PukiWiki]"){kind=logo}
#author("2022-10-19T01:51:16+00:00","default:admin","admin") #author("2023-04-13T09:08:02+00:00","default:admin","admin") *Multiple launch [#c28ba950] You can launch two or more Bakin programs at the same time and copy and paste between the game files loaded in each. Multiple launches consume memory, so if multiple launches are made with well-developed data, the process may become slow. In addition, multiple launches can only be used after Bakin is launched and before any of the game data is loaded. **Copy data between game files [#a16dcdc5] Copying data that has already been created between game files. Currently some data cannot be copied, but this will be planned to be addressed in an update. ***''Copyable Data'' [#xe00fea7] **''Map Editor'' [#na475c88] ***''Maps'' [#qfc826df] You can copy what is used on maps by copying maps from the Map List. Terrain, objects, lights, particles, events, some map settings, and cameras are copied. (However, resources specified in events that exist on maps are not copied, and must be copied separately.) -''All assets in Resources'' -''Map Settings'' When a map is copied, the Basic, Rendering and Enemy Distribution are also copied with it. --Basis If a camera is specified, this will also be copied. -''Maps'' Terrain, objects, lights, particles, and events are copied. However, resources specified in events that exist on the map will not be copied, and must be copied separately. --Rendering Settings The rendering used will be copied. -''Rendering Settings in Map Settings'' --Enemy Distribution The properties of the Enemy Distribution List and Selected Appearance Area are copied. (However, the Database is not copied, so enemy casts must be specified separately.) -''Events'' However, resources specified in the events will not be copied, so they must be copied separately. Also, please note that at this time, if variables with the same name other than local variables exist at the paste destination, they will not be separated into different variables with separate prefixes/suffixes, but will be pasted as they are. -''Events'' You can copy them together by copying maps. Event templates and custom events can be copied by individual events. The event sheets, sheet conditions, graphic settings, and command scripts are also copied in custom events. (However, resources specified in events are not copied and must be copied separately. For example, images and sprites used in the Display Conversation panel will not be copied.) (Also, please note that at this time, if a variable with the same name other than a local variable exists at the paste destination, it will not be isolated to a variable with a separate prefix/suffix, but will be pasted as is.) -''Camera Tool'' **''Resources'' [#ld40a2ba] -''All assets in the Resources'' All assets can be copied individually or as a multiple selection. -''Resources on maps'' Copying maps copies the resources on maps as well. **''Camera Tool'' [#w95c40ca] By copying maps, camera data belonging to that map can also be copied together. -''Cameras'' The camera can also be copied individually. When copying an individual camera, select the map folder from the Map List and then paste. **''Database'' [#t5a62951] -''Database'' The specified resources specified in the custom events are not copied and must be copied separately. Each entry can be copied. However, resources specified in the cast custom event are not copied and must be copied separately. -''Sprites'' Sprites can be copied by following the steps below. ++The image used for the sprite must be copied (or imported) to the paste destination. (If this step is not done, information other than the image will be copied, but the specified picture will not appear because the image does not exist.) ++If an image is prepared, it can be copied using the copy and paste buttons in the sprite list. -''Layouts'' Layouts can be copied by following the steps below. ++Prepare the images and sprites used in the layout by importing or copying them to the destination project. ++Right-click in the layout tool preview of the source project to open the context menu and select "Save Layouts to File".(Any screen will do.) ++Right-click in the layout tool preview of the destination project to open the context menu and select "Load Layouts from File". **''Layouts'' [#r553bbd2] -''Individual Layout'' Copy the layout in the Layout to be Assigned column at the source and paste it at the destination. The resources used in the layout are also copied together. --Notes: The layout of all patterns of all screens of the source project will be copied. (Individual screens cannot be copied.) It takes time for the layouts to reflect the loading. -''Export/Import layout data'' ++Right-click on the layout preview of the source project to open the context menu and select "Save Layouts to File". ++Select any layout you wish to export and save them as a .lyrbr file. The .lyrbr file will also contain the resources contained in the layouts. ++Right-click on the layout preview of the destination project to open the context menu and select "Load Layouts from File". Load the saved .lyrbr file.
