Links
Tags
Creators
Details
1.0.1
Compatibility
Changes
Telegraph v1.0.1 - Carnite Translation Fixes
This patch release fixes multiple translation issues in the Carnite language engine, improving accuracy for in-game communication between civilizations.
Fixed Translation Issues
Core Grammar
- Fixed word order parsing for complex patterns (e.g., "CN :: ; atk" now correctly translates as "My civilization is attacking Carnation")
- Corrected subject-verb-object role assignments in all sentence structures
- Fixed indirect object placement with proper prepositions
Questions
- Fixed yes/no questions with blue banners (e.g., "Is my civilization attacking Carnation?")
- Corrected "Who/What/When/Where/Why" content question handling
- Fixed question tense expectations to use past tense by default per spec
Agents & Roles
- Fixed civilization property agents with levels (e.g., "NM,smth|5" → "Nowy Madagaskar's level 5 blacksmith")
- Corrected plural agent parsing (e.g., "~rd|" → "some raiders")
- Fixed agent role parsing before semicolons
Trade System
- Fixed stack notation in trade offers (e.g., ".dmd" → "1 stack of diamonds")
- Corrected trade response handling with proper civilization references
Special Constructions
- Fixed conjunction operator "&" (e.g., "CN&EG" → "Carnation and Eastguard")
- Fixed negation operator "-" (e.g., "-atk" → "not attack")
- Corrected event noun templates (e.g., "Elctn TWC" → "There is going to be an election at The Twin Cities")
- Fixed possession statements (e.g., "lib|5 CM" → "Cactus Mountain has a librarian level 5")
- Fixed phrasal verb "gear" → "gear up" for requests
- Fixed intransitive verb conjugation (e.g., "die" → "dying", not "dieing")
Formatting
- Removed urgent tense special formatting for consistency
- Fixed various cosmetic rendering issues
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:RT9VpjLI:mELnGGnV"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RT9VpjLI:mELnGGnV"
}
