Enhance Note bit for more readbility. and better freature using from quarts

Author: VR-Rathod

pages/Celery.md

@@ -7,7 +7,7 @@ displayTitle: Game Design
 
 > [!info] About This Page
 > This page covers **game design theory and practice** — from foundational concepts to advanced AAA and indie techniques.
-> For technical implementation see [[Game Development]]. For engine scripting see [[Godot]], [[Unity]], [[Unreal Engine]].
+> For technical implementation see [[Game Development]]. For engine scripting see [[Godot]], [[Unity]] (including its advanced rendering, networking, performance patterns, and DOTS details), [[Unreal Engine]].
 
 - # History
   collapsed:: true
@@ -317,6 +317,8 @@ displayTitle: Game Design
 		  | Secondary | Supporting actions | Dodge, Reload, Craft, Block |
 		  | Meta | Progression rules | Level up, Unlock, Prestige, Season pass |
 		  | Social | Multiplayer rules | Trade, Vote, Cooperate, Compete |
+		- > [!note] Technical Implementation
+		  > For multiplayer/social mechanics, see RPC and state syncing patterns in [[Unity]] #Remote Procedure Calls (RPCs) and [[Unity]] #NetworkVariable & Syncing.
 	-
 	- ## Good Mechanic Checklist
 	  collapsed:: true
@@ -714,6 +716,8 @@ displayTitle: Game Design
 		- > [!tip] Coyote Time & Input Buffering
 		  > These two techniques alone make a platformer feel **dramatically better**.
 		  > Without them, players constantly say "I pressed jump!" — with them, controls feel responsive and fair.
+		- > [!note] Technical Implementation
+		  > In Unity, implementing juice like squash-and-stretch, screen shake, and visual feedback is commonly achieved via tweening libraries like [[DOTween]] and particle setups like [[Unity#Core Concepts — GameObjects & Components]] (under the `ParticleSystem` component) without allocating garbage memory (see [[Unity#Garbage Collection (GC) Optimization]]).
 	-
 	- ## Camera Design
 	  collapsed:: true
@@ -731,6 +735,8 @@ displayTitle: Game Design
 		  | Trauma system | Accumulate trauma value, shake based on it |
 		  | Zoom on action | Zoom in for precision, zoom out for overview |
 		  | Rule of thirds | Player at 1/3 of screen, not center |
+		- > [!note] Technical Tooling
+		  > In Unity, advanced camera techniques like lead space, camera shake, and smart dampening are implemented out of the box using [[Cinemachine]] (see [[Unity#Library & Frameworks]]).
 -
 - # UI/UX Design for Games
   collapsed:: true
@@ -971,6 +977,8 @@ displayTitle: Game Design
 		- > [!info] Systemic Games
 		  > Deus Ex, Dishonored, Prey, Hitman, Breath of the Wild
 		  > Player action cascades through interconnected systems → emergent solutions
+		- > [!tip] Decoupling Systemic Interactions
+		  > For building decoupled, scriptable systemic events that allow objects to respond to triggers without hard references, see [[Unity]]'s ScriptableObject-based Variables & Events.
 	-
 	- ## Procedural Generation Design
 	  collapsed:: true
@@ -987,6 +995,8 @@ displayTitle: Game Design
 		  > 2. Constrained randomness — random within designer-set bounds
 		  > 3. Guarantee fun — ensure minimum quality floor
 		  > 4. Curated + procedural — hand-craft key moments, proc-gen the rest
+		- > [!tip] Technical Implementation (Performance)
+		  > For high-performance voxel, terrain, or dungeon generation (e.g. generating millions of tiles/entities), you can offload calculations to multithreaded systems like the C# Job System and Burst Compiler. See [[Unity#Data-Oriented Technology Stack (DOTS)]].
 	-
 	- ## Live Service Design (GaaS)
 	  collapsed:: true