Skip to content

Latest commit

 

History

History
124 lines (82 loc) · 5.58 KB

CHANGELOG.md

File metadata and controls

124 lines (82 loc) · 5.58 KB
Raw

CHANGELOG

This document is the update log for UCT, which typically outlines short-term plans and arrangements.

For long-term update plans regarding UCT, please refer to PLAN.md, PLAN_zh-CN.md, or PLAN_zh-TW.md.

For specific update logs regarding UCT, please consult CHANGELOG.md, CHANGELOG_zh-CN.md, or CHANGELOG_zh-TW.md.

Updates in Simplified Chinese are prioritized, while other languages will be translated using GPT during version number changes.

v1.0.5 -> v1.0.6 UI Optimization and Expansion

  • Add zoomed view 640x480. (See update plan for details)
  • Separate rendering logic and execution logic for the MENU scene.
  • Separate rendering logic and execution logic for the OW save page.
  • Store existing UI data into ScriptableObject.
  • Add a UI manager.
  • Add Dr style MENU interface.
  • Add Dr style settings interface.
  • Add Dr style OW save interface.
  • Merge this version into Main.

2024/11/12 Plan (1-9)

v1.0.4 -> v1.0.5 Settings Page Reconstruction and Expansion

  • Add pixel-perfect post-processing.
  • Separate rendering logic and execution logic for the settings page.
  • Refine setting items: audio settings, video settings, etc., along with specific toggle options for post-processing/effects.
  • Enhance the extensibility of the settings page and add several new setting options.
  • Add a historical text system.

2024/11/4 Plan (2-4)

2024/11/19 Plan (1, 5)

v1.0.3 -> v1.0.4 UI Display Fixes and Naming Scene Expansion

  • Change the pivot points of the UI frames in the OW scene to be centered.
  • Place the main camera in DontDestroyOnLoad, generated by MainControlSummon. (Similar to the generation methods of MainControl and BGMControl)
  • Check and fix the UI positions and sizes in the Rename scene.
  • Check and fix the UI positions and sizes in the Menu scene.
  • Check and fix the UI positions and sizes in the PPT and Start scenes.
  • Check and fix the UI positions and sizes in the OW scene.
  • Check and fix the UI positions and sizes in the Gameover scene.
  • Check and fix the UI positions and sizes in the Battle scene.
  • Replace transparent character indentation with <indent>.
  • Adjust English fonts to fix character overlap issues.
  • Introduce Fusion 8px font.
  • Expand the number of characters in the naming interface, categorized into basic letters, numbers and symbols, Latin letters, Cyrillic letters, Greek letters, etc.
  • Introduce spelling libraries for Chinese, Japanese, and Korean languages.
  • Add Chinese input support in the naming interface.
  • Add Japanese input support in the naming interface.
  • Add Korean input support in the naming interface.
  • Automatically translate PLAN.md and CHANGELOG.md using GitHub Actions and ChatGPT API.
  • Merge this version into Main.

2024/11/4 Plan (1-2)

2024/11/6 Plan (3-9)

2024/11/7 Plan (10-16)

2024/11/11 Plan (17)

2024/11/12 Plan (18)

v1.0.2 -> v1.0.3 BUG Fixes

  • Fix the issue in the Battle scene where enemy dialogue freezes after executing Fight.
  • Fix the issue in the Battle scene where using an item crashes the game/editor.
  • Fix the issue in the Battle scene where the typewriter still displays ButtonLayer text when using an item without completing typing.
  • Fix the issue in the OW scene where deprecated frame UI is still used.
  • Fix the typewriter's inability to recognize <X> rich text.
  • Add a new rich text <JumpText> to skip entering long texts with a typewriter.

2024/11/4 Plan (1-2, 4-5)

2024/11/5 Plan (3, 6)

2024/11/6 Completed

Note: The UI fixes in the OW scene are currently only effective in the corridor scene and will be fixed in v1.0.4.

v1.0.2 - Foreword

First of all, I made a big mistake—since UCT updated to v1.0.2, there have been numerous updates, but its version number has remained at v1.0.2. This is the result of long-term neglect of the update log.

In fact, initially updating UCT to version 1.0.0 was a mistake in some sense—I thought my template was completed, but it now seems far from it. Nevertheless, changing the version number back would be more troublesome. So for now, let it be.

In the last update of v1.0.2, I created this file—CHANGELOG.md—as a record of every update's contents and the plans for the next update.

The version number updates will follow these rules:

  1. When a PATCH update occurs (1.0.X, where X is changed), it usually means this update involves bug fixes or modifications/refactoring of existing functionalities, without adding new features or content.
  2. When a MINOR update occurs (1.X.0, where X is changed), it typically means this update adds new features or content.
  3. When a MAJOR update occurs (X.0.0, where X is changed), it usually implies... Alright, I guess MAJOR will never change.
  4. Before moving to the next version, the version number will have a suffix -part X. X represents the number of completed tasks.

The format for updates is as follows:

vX.X.0 -> vX.X.1 Summary of Updates

  • Task 1 (Completed)
  • Task 2 (Completed)

XX Year/XX Month/XX Day Plan

XX Year/XX Month/XX Day Completed

vX.X.1 -> vX.X.2 Summary of Updates

  • Task 1 (Not Completed)
  • Task 2 (Not Completed)

XX Year/XX Month/XX Day Plan (x-x items)

XX Year/XX Month/XX Day Completed

The completion time refers to the time when the last item was finished, and that’s all.

2024/11/4 Plan

2024/11/4 Completed