Pax Historia Modding Guide: Fundamental Mechanics | Part 2

Share

Summary

This video is the second part of the Pax Historia creators guide, focusing on debugging and improving presets. It covers essential aspects like effective region naming, concise prompt writing, utilizing tags, and understanding in-game tools for testing and refinement.

Highlights

Cheats Tab for Testing and Nuance
00:17:54

The cheats tab allows preset editors to manipulate the geopolitical situation and map to test the AI's response to specific nuances or to correct mid-game mistakes. This helps in refining AI behavior for desired scenarios.

Effective Region Naming
00:00:56

Region names are fed to the AI as a massive list, so clear and specific names are crucial. Differentiating between a city and its surrounding region (e.g., 'City of Moscow' vs. 'Region of Moscow') helps the AI accurately interpret the map, reducing mistakes, as the AI cannot visually see the map.

Concise Prompt Writing in 'World Before Round One' and 'Simulation Rules'
00:03:18

The 'World Before Round One' and 'Simulation Rules' fields should be direct and commanding, like giving instructions to the AI, rather than telling a story. Longer prompts can lower AI quality, so keep them as short and necessary as possible. For alternate history, describe lore as a historical textbook, focusing on events and figures the AI should be aware of. Specific reminders for common AI mistakes can also be included here.

Understanding and Using Tags
00:06:38

Tags for map features are primarily 'battalion' and 'city' for default prompts. Region tags are for organization and are not fed to the AI to avoid prompt length issues. Country tags, however, are fed to the AI (e.g., 'communist' for a specific nation), which can significantly improve AI quality and accuracy in simulating alternate histories.

Debugging Tools and Game State Mechanics
00:08:35

Battalions (map features with the 'battalion' tag) are fed to the AI, but cities are not due to their sheer number. Countries are defined as 'polities' to encompass various entity types. A critical issue is when the AI dissolves a polity that still owns regions, making those regions unoccupied. The adviser's logs are not seen by the AI during event simulation, so do not include references to them in simulation rules.

In-Game Settings and Event Manager
00:13:00

The event manager logs player actions, generated events, and chats, providing a history of the game. Events can be deleted to correct AI mistakes or test specific scenarios. The 'consolidator' settings (start on round and chunk size) summarize past events into a single passage, preventing the AI from getting overwhelmed by a massive list of events in the late game. This optimizes AI performance by providing a concise historical context.

Recently Summarized Articles

Loading...