impulsivefps
/
Lemontropia-Suite
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Lemontropia-Suite/RESOURCES.md

2.5 KiB
Raw Blame History

Entropia Universe Developer Resources

This document outlines the primary data sources and community resources required to build and maintain the Entropia-Tools suite. Use these sites to verify item stats, calculate costs, and parse game data.

1. Item & Game Mechanics (The "Database")

  • EntropiaWiki
    • Use Case: The most critical resource for weapon decay rates, ammo consumption, creature HP, and blueprint requirements.
    • Data Type: Static item stats, weapon efficiency, and mob attributes.

2. Market & Economic Data

  • Entropia Nexus
    • Use Case: Real-time market tracking. Use this to pull daily/weekly/monthly markups for items.
    • Data Type: Auction house history and markup percentages.

3. Loot Tracking & Global History

  • Entropia Life
    • Use Case: Cross-referencing "Global" and "HoF" (Hall of Fame) drops. Useful for verifying OCR/Log data against community-recorded drops.
    • Data Type: Global loot feeds and player rankings.

4. Geospatial & Mining Data

  • Entropia Planeteer
    • Use Case: Coordinate systems and planet-specific mapping. Essential for the Mining Tracker module.
    • Data Type: Interactive maps and resource distribution.
  • PC-Center
    • Use Case: Deep-dive analytics into mining finder depths and resource categories.
    • Data Type: Mining depth tables and resource tier lists.

5. Technical References (Log Parsing)

  • EL-Tracker
    • Use Case: Reference for how third-party apps interface with the chat.log file.
    • Data Type: Log parsing logic and community tools.

6. Official Source

  • Entropia Universe Official Site
    • Use Case: Monitoring Developer Notes and Patch Logs.
    • Data Type: Client updates that may affect log file formats or screen layouts (impacting OCR).

Instructions for Coding Agent:

  1. Web Scraping: If building an auto-updater for item stats, prioritize EntropiaWiki.
  2. API Simulation: Since most of these sites do not have public JSON APIs, you may need to implement lightweight web scrapers or use local CSV exports where available.
  3. Accuracy: Always cross-reference weapon "Decay" values from the Wiki to ensure ROI calculations in the Hunter Module are 100% accurate.