暫無描述

Quick-Bolt 25b10d29af BT18 merge 1 年之前
.github a181a7c2e8 Update issue templates 2 年之前
.idea 7f6d49f116 Updated Cards 1 年之前
.vscode abef5ff901 .idea, .vscode 2 年之前
Assets 54ac256ea9 Merge branch 'BT18' into BT18-Yellow 1 年之前
Packages 296dcbb8df Fix for desync issue + Added Splash Screen 2 年之前
ProjectSettings 4ada2c5e30 BT18-19 (2.0) green cards 1 年之前
hooks 5dceb81a7b Create scriptable objects for bt15 2 年之前
lfs 25b10d29af BT18 merge 1 年之前
.editorconfig 9ccea0e086 git files, editor config 2 年之前
.gitattributes 9ccea0e086 git files, editor config 2 年之前
.gitignore 093456799b Add level 5 cardEffects 1 年之前
.vsconfig abef5ff901 .idea, .vscode 2 年之前
README.md abef5ff901 .idea, .vscode 2 年之前

README.md

DCGO

List of implemented cards

  • BT1~BT14
  • ST1~ST16
  • EX1~EX5
  • RB1
  • P01~P130

Operating rules

  • The repository should be kept private for now. This is because the code contains paid assets or is not completely safe from a security standpoint.
  • Mimichan is the main developer, with support from wwmonkey. Other members should never edit or push the code.
  • We have a template for creating issues, so please use it. Please fill in all the fields of the template if possible, but for the time being, it is acceptable to leave some fields blank.
  • Please write your issue in as much detail as possible and in an easy-to-understand manner. Card names should always include the card ID or card set ID. Please use words that are common or officially used, and avoid slang as much as possible.
  • The created issue will be viewable in Project, and Mimichan will be in charge of moving the status of the issue. Mimichan will close issues that are deemed resolved in the development environment. Bugs and requests with a status of "Done" have already been resolved and fixed in the latest version.
  • Discussion of individual bugs and feature requests should be done in issue comments. This way it will be easier to keep a log and check. Other topics will be discussed in Discord chat.
  • If you find that a bug that should have been fixed has not yet been resolved, please reopen the closed issue and add a comment to the issue to that effect.