How ranviermud/core works
Main Components Identification
The system can be broken down into several core subsystems:
a. Entity Management Layer
• Account/Player Management (Account.js, Player.js, PlayerManager.js)
• NPC/Mob Management (Npc.js, MobFactory.js, MobManager.js)
• Item Management (Item.js, ItemFactory.js, ItemManager.js)
b. World Management Layer
• Area Management (Area.js, AreaManager.js, AreaFactory.js)
• Room Management (Room.js, RoomManager.js, RoomFactory.js)
• Party System (Party.js, PartyManager.js)
c. Game Mechanics Layer
• Combat/Skills (Skill.js, SkillManager.js, Damage.js, Heal.js)
• Effects System (Effect.js, EffectFactory.js, EffectList.js)
• Quest System (Quest.js, QuestFactory.js, QuestTracker.js)
d. Communication Layer
• Channel System (Channel.js, ChannelManager.js)
• Broadcast System (Broadcast.js)
• Various Audience Types (WorldAudience.js, RoomAudience.js, etc.)
Inner Circle: Core Systems
• Event Management (EventManager.js)
• Command Processing (CommandManager.js, CommandQueue.js)
• Data Management (Data.js, DataSourceRegistry.js)
Middle Circle: Game Logic
• Entity Management
• World Management
• Game Mechanics
Outer Circle: Interface Layer
• Communication Systems
• Player Interface
• Transport Layer (TransportStream.js)
Component Relationships
Key relationships:
• Manager-to-Entity relationships (e.g., PlayerManager → Player)
• Factory-to-Entity relationships (e.g., ItemFactory → Item)
• Event flow through the EventManager
• Command processing pipeline
• Data flow through the broadcast system