Helika Docs

Knowledge Base Uploads

Suggest Edits

Overview

The Knowledge Base is the informational backbone of every AI character in the Helika Content Creation Engine (CCE).

It provides the contextual data the character uses to generate content, respond to mentions, and stay consistent with your game’s lore, updates, and brand voice. Without a properly configured Knowledge Base, your AI will rely solely on its Character Sheet, limiting its ability to reference in-universe events, technical changes, or narrative details.

This section will cover:

  • Purpose and Benefits of the Knowledge Base
  • Supported Data Sources
  • Uploading Files
  • Connecting Feeds
  • Cloud Storage Integration
  • Managing and Organizing Knowledge Sources
  • Avoiding and Handling Conflicting Information
  • Updating the Knowledge Base Over Time
  • Best Practices
  • Troubleshooting Common Issues

Purpose and Benefits of the Knowledge Base

The Knowledge Base serves to:

  • Ground the AI’s outputs in real, up-to-date information about your game or IP.
  • Provide narrative continuity between posts.
  • Enable factual accuracy for technical changes, such as patch notes or gameplay adjustments.
  • Allow the AI to reference and react to events without manual prompting.
  • Support in-universe authenticity so content feels like it’s written from inside the game world.

Example:
If you upload a patch note indicating that Zeus’s lightning bolt damage increased from 65 to 80, the AI can directly reference this in posts:

"The new patch buffed my lightning bolts from 65 to 80. Mortals, prepare yourselves."

Supported Data Sources

The CCE supports multiple types of content ingestion for Knowledge Bases:

Document Uploads

  • Formats: PDF, DOCX, TXT (UTF-8 encoding recommended)
  • Common use cases:
    • Patch notes
    • Lore compendiums
    • Character backstories
    • Event briefs

RSS Feeds

  • Real-time content ingestion from selected news or community sources.
  • Ideal for:
    • Gaming news
    • Esports updates
    • Official development blogs

Cloud Storage Integration

  • Google Drive (initially)
  • Ingests files from a designated folder automatically.

Internal Wiki Exports (Planned)

  • Integration with Confluence, Notion, or studio intranets.

Uploading Files

Step-by-Step File Upload

  1. Navigate to your chosen character’s Knowledge Base section (bottom-left panel in Character Settings).
  2. Click Upload Document.
  3. Drag and drop your file or use the file picker.
  4. Add a brief Description (optional but recommended for clarity in multi-file setups).
  5. Confirm upload. The system processes and indexes the document for future content generation.

File Guidelines

  • Use descriptive filenames (e.g., PatchNotes_1.3.0_Feb2025.pdf).
  • Keep file sizes under platform limits (typically 10MB for PDFs).
  • For PDFs, ensure text is selectable (scanned images of text may not parse correctly).

Connecting Feeds (RSS)

Benefits of RSS Integration

  • Automatically keeps the AI informed about external events.
  • Reduces the need for manual uploads for ongoing news sources.

Setup Steps

  1. In the Knowledge Base panel, select Add RSS Feed.
  2. Paste the RSS feed URL.
  3. Assign a Category Tag (e.g., Industry News, Lore Updates).
  4. Save and confirm.

The AI will periodically poll the feed and add new articles to its reference context.

Cloud Storage Integration

Supported Cloud Service

  • Google Drive (initial rollout)

How It Works

  • The CCE monitors a linked Google Drive folder.
  • Any file added to this folder becomes available to the AI.

Setup Steps

  1. In the Knowledge Base panel, click Connect Cloud Storage.
  2. Select Google Drive.
  3. Authenticate with the Google account containing your source folder.
  4. Choose the specific folder for ingestion.
  5. Confirm and save.

👍

Tip

Maintain a dedicated folder for each character to avoid irrelevant uploads.

Managing and Organizing Knowledge Sources

As your Knowledge Base grows, organization becomes critical.

Features

  • Source List View: Displays all connected documents, feeds, and cloud folders.
  • Sorting & Filtering: Filter by type, date added, or category tag.
  • Replace vs. Append: Replace outdated files (e.g., old patch notes) or append new ones.
  • Manual Removal: Delete any source to immediately remove it from the AI’s active context.

Avoiding and Handling Conflicting Information

Conflicting data can confuse the AI and lead to inconsistent outputs.

Example:

  • File A says: "Zeus is male."
  • File B says: "Zeus is female."

System Behavior

  • The AI attempts to reconcile based on recency and volume of references.
  • However, false or contradictory data will still influence output.

Best Practices to Avoid Conflicts

  • Review documents before upload.
  • Remove outdated or superseded files promptly.
  • Use consistent terminology across all sources.

Updating the Knowledge Base Over Time

The Knowledge Base should evolve alongside your game and campaigns.

When to Update

  • After every patch release.
  • When launching new characters or expansions.
  • Before major in-game events or seasonal campaigns.

Recommended Maintenance Cycle

  • Weekly: Check RSS feed relevance.
  • Monthly: Audit documents for outdated info.
  • Quarterly: Review entire Knowledge Base for accuracy.

Best Practices

  • Keep it Relevant: Only upload materials that directly inform content you want generated.
  • Tag Everything: Use descriptive tags for easier filtering later.
  • Use Official Sources: Avoid community speculation unless intentional for engagement.
  • Preview Outputs: After adding a major source, test content generation to ensure accuracy.

Updated 29 days ago