比较提交
合并到: unity-tech-cn:main
unity-tech-cn:/main
unity-tech-cn:/fix-mtt-493
拉取从: unity-tech-cn:fix-mtt-493
unity-tech-cn:/main
unity-tech-cn:/fix-mtt-493
此合并请求有变更与目标分支冲突。
/Assets/BossRoom/Prefabs/Character/CharacterSet.prefab
/Assets/BossRoom/Scenes/DungeonTest.unity
/Assets/BossRoom/Scripts/Client/Game/Character/ModelSwap.cs
/Assets/BossRoom
4 次代码提交
main
...
fix-mtt-493
| 作者 | SHA1 | 备注 | 提交日期 |
|---|---|---|---|
eheimburg
|
934cfc7e | changes to address PR problems | 4 年前 |
|
eheimburg
|
429bd773 | comment/logging cleanup | 4 年前 |
|
eheimburg
|
59528a23 |
Update EmptySliceBehavior.cs
Putting this back the way I found it (commented it out because I can't get standalone builds to run with it enabled, local issue) |
4 年前 |
|
eheimburg
|
2b8c0818 | Character-select screen basic functionality | 4 年前 |
共有 327 个文件被更改，包括 6065 次插入 和 1701 次删除
-
2Packages/manifest.json
-
47Packages/packages-lock.json
-
2ProjectSettings/ProjectSettings.asset
-
116ProjectSettings/GraphicsSettings.asset
-
2Assets/BossRoom/Prefabs/Dungeon/Dungeon Pieces/Door.prefab
-
7Assets/BossRoom/Prefabs/Dungeon/Dungeon Pieces/torch.prefab
-
3Assets/BossRoom/Prefabs/Character/Boss.prefab
-
5Assets/BossRoom/Prefabs/Character/Imp.prefab
-
514Assets/BossRoom/Prefabs/Character/CharacterSet.prefab
-
13Assets/BossRoom/Prefabs/Enemy.prefab
-
13Assets/BossRoom/Prefabs/Imp.prefab
-
2Assets/BossRoom/Material/Characters/Enemy_Eyes_sheet.mat
-
9Assets/BossRoom/Material/Characters/Enemy_Mouth_sheet.mat
-
3Assets/BossRoom/Material/Characters/Hero_Eyes_sheet.mat
-
8Assets/BossRoom/Material/Characters/Hero_Mouth_sheet.mat
-
9Assets/BossRoom/Material/Characters/ToonTest/Hair_Archer_Boy.mat
-
9Assets/BossRoom/Material/Characters/ToonTest/Hair_Archer_Girl.mat
-
13Assets/BossRoom/Material/Characters/ToonTest/Hair_Mage_Boy.mat
-
11Assets/BossRoom/Material/Characters/ToonTest/Hair_Mage_Girl.mat
-
13Assets/BossRoom/Material/Characters/ToonTest/Hair_Rogue_Boy.mat
-
9Assets/BossRoom/Material/Characters/ToonTest/Hair_Rogue_Girl.mat
-
11Assets/BossRoom/Material/Characters/ToonTest/Hair_Tank_Boy.mat
-
9Assets/BossRoom/Material/Characters/ToonTest/Hair_Tank_Girl.mat
-
11Assets/BossRoom/Material/Characters/ToonTest/Head_Archer_Boy.mat
-
11Assets/BossRoom/Material/Characters/ToonTest/Head_Archer_Girl.mat
-
10Assets/BossRoom/Material/Characters/ToonTest/Head_Boss.mat
-
10Assets/BossRoom/Material/Characters/ToonTest/Head_Imp.mat
-
11Assets/BossRoom/Material/Characters/ToonTest/Head_Mage_Boy.mat
-
11Assets/BossRoom/Material/Characters/ToonTest/Head_Mage_Girl.mat
-
11Assets/BossRoom/Material/Characters/ToonTest/Head_Rogue_Boy.mat
-
11Assets/BossRoom/Material/Characters/ToonTest/Head_Rogue_Girl.mat
-
11Assets/BossRoom/Material/Characters/ToonTest/Head_Tank_Boy.mat
-
13Assets/BossRoom/Material/Characters/ToonTest/Head_Tank_Girl.mat
-
13Assets/BossRoom/Material/Characters/ToonTest/Torso_Archer.mat
-
9Assets/BossRoom/Material/Characters/ToonTest/Torso_Boss.mat
-
12Assets/BossRoom/Material/Characters/ToonTest/Torso_Imp.mat
-
11Assets/BossRoom/Material/Characters/ToonTest/Torso_Mage_Boy.mat
-
11Assets/BossRoom/Material/Characters/ToonTest/Torso_Mage_Girl.mat
-
11Assets/BossRoom/Material/Characters/ToonTest/Torso_Rogue.mat
-
7Assets/BossRoom/Material/Characters/ToonTest/Torso_Tank.mat
-
13Assets/BossRoom/Material/Characters/ToonTest/Weapons_Archer.mat
-
13Assets/BossRoom/Material/Characters/ToonTest/Weapons_Mage.mat
-
13Assets/BossRoom/Material/Characters/ToonTest/Weapons_Rogue.mat
-
7Assets/BossRoom/Material/Characters/ToonTest/Weapons_Tank.mat
-
3Assets/BossRoom/Material/Dungeon/lava.mat
-
3Assets/BossRoom/Material/Dungeon/deco_dungeon.mat
-
958Assets/BossRoom/Models/DungeonPieces.FBX
-
25Assets/BossRoom/Models/BossSetController.controller
-
27Assets/BossRoom/Models/CharacterSet.fbx.meta
-
548Assets/BossRoom/Models/CharacterSetController.controller
-
8Assets/BossRoom/PostProcessing/PostProcessVolume Profile.asset
-
2Assets/BossRoom/Textures/Characters/Tank_Weapon_CLR.tga
-
4Assets/BossRoom/Textures/Environment/deco_dungeon.png
-
942Assets/BossRoom/Scenes/DungeonTest.unity
-
992Assets/BossRoom/Scenes/CharSelect.unity
-
22Assets/BossRoom/Scripts/Server/Game/Action/Action.cs
-
52Assets/BossRoom/Scripts/Server/Game/Action/ActionPlayer.cs
-
42Assets/BossRoom/Scripts/Server/Game/Action/ChaseAction.cs
-
80Assets/BossRoom/Scripts/Server/Game/Action/MeleeAction.cs
-
56Assets/BossRoom/Scripts/Server/Game/Character/AIBrain.cs
-
120Assets/BossRoom/Scripts/Server/Game/Character/ServerCharacter.cs
-
44Assets/BossRoom/Scripts/Server/Game/State/ServerBossRoomState.cs
-
189Assets/BossRoom/Scripts/Server/Game/State/ServerCharSelectState.cs
-
5Assets/BossRoom/Scripts/Shared/BossRoom.Shared.asmdef
-
126Assets/BossRoom/Scripts/Shared/Game/Action/ActionRequestData.cs
-
135Assets/BossRoom/Scripts/Shared/Game/State/CharSelectData.cs
-
4Assets/BossRoom/Scripts/Shared/Game/State/GameStateBehaviour.cs
-
10Assets/BossRoom/Scripts/Client/Game/Character/ClientCharacter.cs
-
11Assets/BossRoom/Scripts/Client/Game/Character/ModelSwap.cs
-
45Assets/BossRoom/Scripts/Client/Game/State/ClientCharSelectState.cs
-
76.editorconfig
-
39README.md
-
0InitCodeMarker
-
8Packages/com.unity.multiplayer.samples.coop/.npmignore
-
11Packages/com.unity.multiplayer.samples.coop/CHANGELOG.md
-
7Packages/com.unity.multiplayer.samples.coop/CHANGELOG.md.meta
-
315Packages/com.unity.multiplayer.samples.coop/Documentation~/images/example.png
-
67Packages/com.unity.multiplayer.samples.coop/Documentation~/images/gitlab_ci_secret_variables.png
-
555Packages/com.unity.multiplayer.samples.coop/Documentation~/images/gitlab_pipeline_download.png
-
483Packages/com.unity.multiplayer.samples.coop/Documentation~/images/gitlab_pipelines.png
-
448Packages/com.unity.multiplayer.samples.coop/Documentation~/images/template_in_new_project.png
-
137Packages/com.unity.multiplayer.samples.coop/Documentation~/index.md
-
5Packages/com.unity.multiplayer.samples.coop/LICENSE.md
-
7Packages/com.unity.multiplayer.samples.coop/LICENSE.md.meta
-
26Packages/com.unity.multiplayer.samples.coop/QAReport.md
-
7Packages/com.unity.multiplayer.samples.coop/QAReport.md.meta
-
39Packages/com.unity.multiplayer.samples.coop/README.md
-
7Packages/com.unity.multiplayer.samples.coop/README.md.meta
-
8Packages/com.unity.multiplayer.samples.coop/Tests.meta
-
8Packages/com.unity.multiplayer.samples.coop/Tests/Editor.meta
116
ProjectSettings/GraphicsSettings.asset
文件差异内容过多而无法显示
查看文件
文件差异内容过多而无法显示
查看文件
958
Assets/BossRoom/Models/DungeonPieces.FBX
文件差异内容过多而无法显示
查看文件
文件差异内容过多而无法显示
查看文件
2
Assets/BossRoom/Textures/Characters/Tank_Weapon_CLR.tga
文件差异内容过多而无法显示
查看文件
文件差异内容过多而无法显示
查看文件
4
Assets/BossRoom/Textures/Environment/deco_dungeon.png
文件差异内容过多而无法显示
查看文件
文件差异内容过多而无法显示
查看文件
942
Assets/BossRoom/Scenes/DungeonTest.unity
文件差异内容过多而无法显示
查看文件
文件差异内容过多而无法显示
查看文件
992
Assets/BossRoom/Scenes/CharSelect.unity
文件差异内容过多而无法显示
查看文件
文件差异内容过多而无法显示
查看文件
76
.editorconfig
文件差异内容过多而无法显示
查看文件
文件差异内容过多而无法显示
查看文件
|
|||
# TODOs (trimmed down version of tasks listed at: https://github.cds.internal.unity3d.com/unity/com.unity.template-starter-kit) |
|||
|
|||
##### Fill in your project template's package information |
|||
|
|||
Update the following required fields in `Packages/com.unity.template.mytemplate/package.json`: |
|||
- `name`: Project template's package name, it should follow this naming convention: `com.unity.template.[your-template-name]` |
|||
(Example: `com.unity.template.3d`) |
|||
- `displayName`: Package user friendly display name. (Example: `"First person shooter"`). <br>__Note:__ Use a display name that will help users understand what your project template is intended for. |
|||
- `version`: Package version `X.Y.Z`, your project **must** adhere to [Semantic Versioning](http://semver.org/spec/v2.0.0.html). |
|||
- `unity`: Minimum Unity Version your project template is compatible with. (Example: `2018.3`) |
|||
- `description`: This is the description for your template which will be displayed to the user to let them know what this template is for. This description shouldn't include anything version-specific and should stay pretty consistent across template versions. |
|||
- `dependencies`: Specify the dependencies the template requires. If you add a package to your project, you should also add it here. We try to keep this list as lean as possible to avoid conflicts as much as possible. |
|||
|
|||
##### Update **README.md** |
|||
|
|||
The README.md file should contain all pertinent information for template developers, such as: |
|||
* Prerequisites |
|||
* External tools or development libraries |
|||
* Required installed Software |
|||
|
|||
The Readme file at the root of the project should be the same as the one found in the template package folder. |
|||
|
|||
##### Prepare your documentation |
|||
|
|||
Rename and update **Packages/com.unity.template.mytemplate/Documentation~/your-package-name.md** documentation file. |
|||
|
|||
Use this documentation template to create preliminary, high-level documentation for the _development_ of your template's package. This document is meant to introduce other developers to the features and sample files included in your project template. |
|||
|
|||
Your template's documentation will be made available online and in the editor during publishing to guide our users. |
|||
|
|||
##### Update the changelog |
|||
|
|||
**Packages/com.unity.template.mytemplate/CHANGELOG.md**. |
|||
|
|||
Every new feature or bug fix should have a trace in this file. For more details on the chosen changelog format, see [Keep a Changelog](http://keepachangelog.com/en/1.0.0/). |
|||
|
|||
Changelogs will be made available online to inform users about the changes they can expect when downloading a project template. As a consequence, the changelog content should be customer friendly and present clear, meaningful information. |
|||
|
|||
#### Complete the rest of the steps in the link regarding Legal & Testing |
|||
|
|||
ProjectData~/ProjectSettings/ProjectVersion.txt |
|||
ProjectData~/Assets/Scenes.meta |
|||
.npmrc |
|||
.npmignore |
|||
.gitignore |
|||
QAReport.md |
|||
QAReport.md.meta |
|||
.gitlab-ci.yml |
|||
|
|||
# Changelog |
|||
All notable changes to this project template will be documented in this file. |
|||
|
|||
The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/) |
|||
and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html). |
|||
|
|||
## [0.1.0] - 2020-10-09 |
|||
|
|||
### This is the first release of *Unity Package com.unity.template.mytemplate*. |
|||
|
|||
*Short description of this release* |
|||
|
|||
fileFormatVersion: 2 |
|||
guid: 6f00b2d43a7ad4286a00be8b13f4a499 |
|||
TextScriptImporter: |
|||
externalObjects: {} |
|||
userData: |
|||
assetBundleName: |
|||
assetBundleVariant: |
|||
| 之前 | 之后 |
|---|---|
|
|
| 宽度: 748 | 高度: 249 | 大小: 51 KiB |
| 之前 | 之后 |
|---|---|
|
|
| 宽度: 990 | 高度: 283 | 大小: 16 KiB |
| 之前 | 之后 |
|---|---|
|
|
| 宽度: 2518 | 高度: 160 | 大小: 53 KiB |
| 之前 | 之后 |
|---|---|
|
|
| 宽度: 796 | 高度: 1168 | 大小: 101 KiB |
| 之前 | 之后 |
|---|---|
|
|
| 宽度: 1990 | 高度: 1082 | 大小: 123 KiB |
|
|||
>>> |
|||
**_Project Template Documentation_** |
|||
|
|||
Use this template to create preliminary, high-level documentation meant to introduce users to the feature and the sample files included in this project template. When writing your documentation, do the following: |
|||
|
|||
1. Follow instructions in blockquotes. |
|||
|
|||
2. Replace angle brackets with the appropriate text. For example, replace "<template name>" with the official name of the project template. |
|||
|
|||
3. Delete sections that do not apply to your project template. For example, a template containing only sample files does not have a "Using <template name>" section, so this section can be removed. |
|||
|
|||
4. After documentation is completed, make sure you delete all instructions and examples in blockquotes including this preamble and its title: |
|||
|
|||
``` |
|||
>>> |
|||
Delete all of the text between pairs of blockquote markdown. |
|||
>>> |
|||
``` |
|||
>>> |
|||
|
|||
# About <template name> |
|||
|
|||
>>> |
|||
Name the heading of the first topic after the **displayName** of the project template as it appears in the template's manifest. Check with your Product Manager to ensure that the template is named correctly. |
|||
|
|||
This first topic includes a brief, high-level explanation of the project template and, if applicable, provides links to Unity Manual topics. |
|||
>>> |
|||
|
|||
**_Example:_** |
|||
|
|||
>>> |
|||
Here is an example for reference only. Do not include this in the final documentation file: |
|||
|
|||
*The First Persion Shooter project template includes examples of First Person Shooter assets, First Person Shooter Instances, animation, GameObjects, game mechanics and scripts that will help you get started quickly with creating your own first person shooter game.* |
|||
>>> |
|||
|
|||
<a name="UsingProjectTemplate"></a> |
|||
# Using <template name> |
|||
>>> |
|||
|
|||
The contents of this section depends on the type of project template. |
|||
|
|||
* At a minimum, this section should include reference documentation that describes the assets, structure, and properties that makes up the project template's content. This reference documentation should include screen grabs (see how to add screens below), a list of assets or settings, an explanation of what each asset or setting does, and the default values of each asset or setting. |
|||
* Ideally, this section should also include a workflow: a list of steps that the user can easily follow that demonstrates how to use the project template. This list of steps should include screen grabs (see how to add screens below) to better describe how to use the feature. |
|||
|
|||
For project templates that include sample files, this section may include detailed information on how the user can use these sample files. Workflow diagrams or illustrations could be included if deemed appropriate. |
|||
|
|||
## How to add images |
|||
|
|||
*(This section is for reference. Do not include in the final documentation file)* |
|||
|
|||
If the [Using <template name>](#UsingProjectTemplate) section includes screen grabs or diagrams, a link to the image must be added to this MD file, before or after the paragraph with the instruction or description that references the image. In addition, a caption should be added to the image link that includes the name of the screen or diagram. All images must be PNG files with underscores for spaces. No animated GIFs. |
|||
|
|||
An example is included below: |
|||
|
|||
 |
|||
|
|||
Notice that the example screen shot is included in the images folder. All screen grabs and/or diagrams must be added and referenced from the images folder. |
|||
|
|||
For more on the Unity documentation standards for creating and adding screen grabs, see this confluence page: https://confluence.hq.unity3d.com/pages/viewpage.action?pageId=13500715 |
|||
>>> |
|||
|
|||
|
|||
|
|||
# Technical details |
|||
## Requirements |
|||
|
|||
>>> |
|||
This subtopic includes a bullet list with the compatible versions of Unity. This subtopic may also include additional requirements or recommendations for 3rd party software or hardware. If you need to include references to non-Unity products, make sure you refer to these products correctly and that all references include the proper trademarks (tm or r) |
|||
>>> |
|||
|
|||
This version of <template name> is compatible with the following versions of the Unity Editor: |
|||
|
|||
* 2018.3 and later (recommended) |
|||
|
|||
To use this project template, you must have the following 3rd party products: |
|||
|
|||
* <product name and version with trademark or registered trademark.> |
|||
* <product name and version with trademark or registered trademark.> |
|||
* <product name and version with trademark or registered trademark.> |
|||
|
|||
## Known limitations |
|||
>>> |
|||
This section lists the known limitations with this version of the project template. If there are no known limitations, or if the limitations are trivial, exclude this section. An example is provided. |
|||
>>> |
|||
|
|||
<template name> template version <template version> includes the following known limitations: |
|||
|
|||
* <brief one-line description of first limitation.> |
|||
* <brief one-line description of second limitation.> |
|||
* <and so on> |
|||
|
|||
>>> |
|||
*Example (For reference. Do not include in the final documentation file):* |
|||
|
|||
The First Person Shoot template version 1.0 has the following limitations:* |
|||
|
|||
* The First Person Shooter template does not support sound. |
|||
* The First Person Shooter template's Recorder properties are not available in standalone players. |
|||
* MP4 encoding is only available on Windows. |
|||
>>> |
|||
|
|||
## Project template contents |
|||
>>> |
|||
This section includes the location of important files you want the user to know about. For example, if this project template containing user interface, models, and materials separated by groups, you may want to provide the folder location of each group. |
|||
>>> |
|||
|
|||
The following table indicates the <describe the breakdown you used here>: |
|||
|
|||
|Location|Description| |
|||
|---|---| |
|||
|`<folder>`|Contains <describe what the folder contains>.| |
|||
|`<file>`|Contains <describe what the file represents or implements>.| |
|||
|
|||
>>> |
|||
*Example (For reference. Do not include in the final documentation file):* |
|||
|
|||
The following table indicates the root folder of each type of sample in this project template. Each sample's root folder contains its own folders: |
|||
|
|||
|Folder Location|Description| |
|||
|---|---| |
|||
|`WoodenCrate_Orange`|Root folder containing the assets for the orange crates.| |
|||
|`Characters`|Root folder containing the assets and animators for the characters.| |
|||
|`Levels`|Root folder containing scenes for the sample game's levels.| |
|||
>>> |
|||
|
|||
## Document revision history |
|||
>>> |
|||
This section includes the revision history of the document. The revision history tracks when a document is created, edited, and updated. If you create or update a document, you must add a new row describing the revision. The Documentation Team also uses this table to track when a document is edited and its editing level. An example is provided: |
|||
|
|||
|Date|Reason| |
|||
|---|---| |
|||
|Sept 12, 2017|Unedited. Published to production.| |
|||
|Sept 10, 2017|Document updated for project template version 1.1.<br>New features: <li>audio support for capturing MP4s.<li>Instructions on saving Recorder prefabs| |
|||
|Sept 5, 2017|Limited edit by Documentation Team. Published to production.| |
|||
|Aug 25, 2017|Document created. Matches project template version 1.0.| |
|||
>>> |
|||
|
|||
com.unity.multiplayer.samples.coop copyright © 2020 Unity Technologies ApS |
|||
|
|||
Licensed under the Unity Companion License for Unity-dependent projects--see [Unity Companion License](http://www.unity3d.com/legal/licenses/Unity_Companion_License). |
|||
|
|||
Unless expressly provided otherwise, the Software under this license is made available strictly on an “AS IS” BASIS WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. Please review the license for details on these and other terms and conditions. |
|||
|
|||
fileFormatVersion: 2 |
|||
guid: e1f27ba539e634ffa814b5977253d779 |
|||
TextScriptImporter: |
|||
externalObjects: {} |
|||
userData: |
|||
assetBundleName: |
|||
assetBundleVariant: |
|||
|
|||
# Quality Report |
|||
Use this file to outline the test strategy for this project template. |
|||
|
|||
## Version tested: [*package version*] |
|||
|
|||
## QA Owner: [*Add Name*] |
|||
## UX Owner: [*Add Name*] |
|||
|
|||
## Test strategy |
|||
*Use this section to describe how this feature was tested.* |
|||
* A link to the Test Plan (Test Rails, other) |
|||
* Results from the project template's editor and runtime test suite. |
|||
* Link to automated test results (if any) |
|||
* Manual test Results, [here's an example](https://docs.google.com/spreadsheets/d/12A76U5Gf969w10KL4Ik0wC1oFIBDUoRrqIvQgD18TFo/edit#gid=0) |
|||
* Scenario test week outcome |
|||
* etc. |
|||
|
|||
## Package Status |
|||
Use this section to describe: |
|||
* UX status/evaluation results |
|||
* package stability |
|||
* known bugs, issues |
|||
* performance metrics, |
|||
* etc |
|||
|
|||
In other words, a general feeling on the health of this project template. |
|||
|
|||
fileFormatVersion: 2 |
|||
guid: 38e03a401f2e04237aa2d319d824266c |
|||
TextScriptImporter: |
|||
externalObjects: {} |
|||
userData: |
|||
assetBundleName: |
|||
assetBundleVariant: |
|||
|
|||
# TODOs (trimmed down version of tasks listed at: https://github.cds.internal.unity3d.com/unity/com.unity.template-starter-kit) |
|||
|
|||
##### Fill in your project template's package information |
|||
|
|||
Update the following required fields in `Packages/com.unity.template.mytemplate/package.json`: |
|||
- `name`: Project template's package name, it should follow this naming convention: `com.unity.template.[your-template-name]` |
|||
(Example: `com.unity.template.3d`) |
|||
- `displayName`: Package user friendly display name. (Example: `"First person shooter"`). <br>__Note:__ Use a display name that will help users understand what your project template is intended for. |
|||
- `version`: Package version `X.Y.Z`, your project **must** adhere to [Semantic Versioning](http://semver.org/spec/v2.0.0.html). |
|||
- `unity`: Minimum Unity Version your project template is compatible with. (Example: `2018.3`) |
|||
- `description`: This is the description for your template which will be displayed to the user to let them know what this template is for. This description shouldn't include anything version-specific and should stay pretty consistent across template versions. |
|||
- `dependencies`: Specify the dependencies the template requires. If you add a package to your project, you should also add it here. We try to keep this list as lean as possible to avoid conflicts as much as possible. |
|||
|
|||
##### Update **README.md** |
|||
|
|||
The README.md file should contain all pertinent information for template developers, such as: |
|||
* Prerequisites |
|||
* External tools or development libraries |
|||
* Required installed Software |
|||
|
|||
The Readme file at the root of the project should be the same as the one found in the template package folder. |
|||
|
|||
##### Prepare your documentation |
|||
|
|||
Rename and update **Packages/com.unity.template.mytemplate/Documentation~/your-package-name.md** documentation file. |
|||
|
|||
Use this documentation template to create preliminary, high-level documentation for the _development_ of your template's package. This document is meant to introduce other developers to the features and sample files included in your project template. |
|||
|
|||
Your template's documentation will be made available online and in the editor during publishing to guide our users. |
|||
|
|||
##### Update the changelog |
|||
|
|||
**Packages/com.unity.template.mytemplate/CHANGELOG.md**. |
|||
|
|||
Every new feature or bug fix should have a trace in this file. For more details on the chosen changelog format, see [Keep a Changelog](http://keepachangelog.com/en/1.0.0/). |
|||
|
|||
Changelogs will be made available online to inform users about the changes they can expect when downloading a project template. As a consequence, the changelog content should be customer friendly and present clear, meaningful information. |
|||
|
|||
#### Complete the rest of the steps in the link regarding Legal & Testing |
|||
|
|||
fileFormatVersion: 2 |
|||
guid: 0a4025153e1d8462296108e234c57e9a |
|||
TextScriptImporter: |
|||
externalObjects: {} |
|||
userData: |
|||
assetBundleName: |
|||
assetBundleVariant: |
|||
|
|||
fileFormatVersion: 2 |
|||
guid: 1977828ca0ab3cf409d003e816121b85 |
|||
folderAsset: yes |
|||
DefaultImporter: |
|||
externalObjects: {} |
|||
userData: |
|||
assetBundleName: |
|||
assetBundleVariant: |
|||
|
|||
fileFormatVersion: 2 |
|||
guid: 638e0ab1bfc544e57b3cbfdeab499e95 |
|||
folderAsset: yes |
|||
DefaultImporter: |
|||
externalObjects: {} |
|||
userData: |
|||
assetBundleName: |
|||
assetBundleVariant: |
|||
部分文件因为文件数量过多而无法显示
撰写
预览
正在加载...
取消
保存
Reference in new issue