Skip to content
Raxiore Wiki
Powered by Pagefind
Guides
Language
English
The Field Guide

Raxiores of Raxiore Dinosaur List: Verified 0.6 Names

See the dinosaurs named in the current Java 0.6 changelog, including Triceratops, Alioramus, Amargasaurus, and Giganotosaurus, with source limits.

11/1/2026 Last updated: 11/1/2026 4 min read

FAQ

Is this the complete Raxiores dinosaur roster?
No. This index records names explicitly present in the Java ror-0.6 changelog. A changelog is not a complete entity registry, so other creatures may exist.
Is Triceratops finished in Java 0.6?
The author changelog marks the Triceratops addition as WIP, meaning work in progress. This page preserves that qualification.
Does this list also apply to the Bedrock port?
Not automatically. Its evidence comes from the Java file changelog. The separate Bedrock port has its own beta release track.

What this list actually covers

This index records the creature names explicitly found in the author’s ror-0.6 changelog, uploaded October 31, 2026. It is useful for checking which dinosaurs an update mentions, but it is not a complete list of every entity in the mod.

The source belongs to the current Java 1.20.1 Forge project. If you are using an add-on or reading a guide for a similarly named older project, first check the edition and project comparison.

Dinosaurs named as additions

Name in the release notes What the author says Important limit
Triceratops Added; marked “wip” Do not present the creature as feature-complete
Alioramus Added The entry does not establish a spawn biome, diet, or taming recipe
Amargasaurus Added The entry does not establish a breeding or egg system
Giganotosaurus Added; marked “complete” This is the author’s status label, not a combat ranking

Creature index diagram lists Triceratops as WIP alongside Alioramus and Amargasaurus in the Java 0.6 changelog.

Original editorial diagram. These are source labels, not creature portraits.

The wording matters. “Added” supports recording a creature’s name in this update. It does not tell us where to find it, how rare it is, or whether it can be tamed. We have not substituted real-world paleontology for Minecraft mechanics.

Giganotosaurus and the meaning of “complete”

The release notes describe the Giganotosaurus addition as complete. That qualifier is worth preserving because Triceratops carries the opposite, unfinished status in the same changelog. It still does not establish which creature is strongest, whether a particular attack wins a matchup, or what equipment a player should bring.

Giganotosaurus status diagram explains that the author’s complete label does not imply damage rankings or taming mechanics.

A release-status note is different from a gameplay recommendation.

For the surrounding feature and balance changes, see the 0.6 changelog summary. Keeping the file context attached to a name helps prevent details from older videos becoming unqualified current facts.

Other dinosaurs mentioned in combat changes

The same changelog also mentions Spinosaurus and T. raxiores. These are combat-change references, not new-addition entries in the table above. The author notes a Spinosaurus slash interaction with blocking dinosaurs and timing-related parry changes for T. raxiores.

Those notes are evidence that the names occur in this release record. They are not enough to write a full move list, damage chart, cooldown guide, or player-control tutorial. We have not tested those interactions in-game.

How to verify a creature guide

Before following a creature-specific tip, ask three questions:

  1. Does it identify the current project and exact file or version?
  2. Does it show or cite the claimed mechanic, rather than infer it from the creature’s name?
  3. Does it distinguish Java from the Bedrock port and retain work-in-progress qualifiers?

Evidence checklist for a Raxiores creature guide separates confirmed names, release context, and mechanics still needing sources.

Unknown spawn tables or recipes should stay unknown until documented.

There are no taming or breeding recipes on this page because we do not have adequate current-version evidence for them. To get the correct file before investigating a creature yourself, follow the installation guide. If a creature-related problem is reproducible, the issue-report checklist explains which environment details to record.

Source and verification scope

Primary source: Java ror-0.6 file and changelog, CurseForge file 9380871. Reviewed November 1, 2026. The index is an editorial reading of the author’s notes; no species behavior, spawn location, or player interaction has been independently tested here.

Related Articles

Was this helpful?