rimuwu/dinogochi

Purpose and Entry Points

DinoGochi is a Python Telegram RPG/tamagotchi bot: users own dinosaurs, manage needs and activities, travel, craft, trade, fight, and participate in social/game systems. Process startup is main.py, with bot construction/runtime wiring in bot/bot_instance.py and executable/bootstrap logic in bot/exec.py. Configuration is generated/read through bot/config.py.

Telegram Request Pipeline

Telegram updates are routed into the extensive handler layer, organized by product domain: live activities, menus, combat, market, quests, crafting, arena, and inline interactions. Authorization, chat/type/state gating occur before handlers via filters; middleware provides cross-cutting antiflood, callback antiflood, logging, and worker-pass behavior.

• bot/handlers/actions_live/

• bot/handlers/main_menu/

• bot/filters/

• bot/middlewares/

Persistent Game State

MongoDB is the primary required datastore, accessed through dedicated database management code. Domain models represent persisted users, dinosaurs, groups, activities, items, market listings, arena, tavern, and tracking data. Redis is also materially present through a separate manager and Redis-backed user/tavern facilities, likely supporting cache or ephemeral coordination boundaries.

• bot/dbmanager.py

• bot/redismanager.py

• bot/models/user.py

• bot/models/dinosaur.py

• bot/models/activity/

Game Domain and Content Definition

The game’s durable rules/data boundary combines Python item/activity dataclasses and static JSON catalogs. Item classes encode behavior/categories; models represent active timed work such as collecting, crafting, journey, sleep, games, and training. JSON supplies dinosaurs, eggs, mobs, quests, shops, journey configuration, recipes, and item definitions, enabling content changes independently of much handler code.

• bot/dataclasess/items/

• bot/models/activity/

• bot/json/items/

• bot/json/dinosaurs.json

Domain Services and Gameplay Modules

Handlers delegate core operations to reusable modules for dinosaur state, inventory/items/crafting, combat strategy, market flows, quests, groups, dialogs, notifications, localization, and user features. This layer is the key boundary between Telegram-facing interaction code and database/content-backed game mutations.

• bot/modules/dinosaur/

• bot/modules/items/

• bot/modules/combat/

• bot/modules/market/

• bot/modules/quests.py

Timed Processing and Background Control Flow

A task subsystem advances time-dependent simulation independently of user messages: dinosaur states, incubation, journeys, sleep, collecting, crafting, games, market expiration, arena, events, notifications, subscriptions, backups, and reporting. Task orchestration/queue abstractions sit alongside these scheduled job implementations.

• bot/taskmanager.py

• bot/modules/task_queue.py

• bot/tasks/

• bot/tasks/dino_states.py

Integrations, Delivery, and Assets

The bot integrates Telegram as its primary external platform, MongoDB and Redis for state, plus payment/advertising-related modules (CryptoBot, Telegram Stars/invoices, donations, ads). Docker Compose packages the runtime; Nginx configuration and a webhook server module indicate deployment may support reverse-proxied webhook delivery rather than only polling. Localized UI strings and image/font assets support multilingual, media-rich responses.

• docker-compose.yml

• nginx/nginx.conf.template

• bot/modules/webhook_server.py

• bot/modules/cryptobot.py

• bot/localization/