Development is not a release announcement.
OSastra is an upcoming Old School RuneScape-style private server. Right now, it is an alpha development project, not a completed public game. There is no official full-release date published on this website. That distinction matters: an advertised boss, skilling route or quality-of-life idea is only valuable when players can interact with it reliably.
We are concentrating on the parts of the game that people use repeatedly. A player should be able to interact with the world, equip items, switch activities and understand why something succeeds or fails. When those systems misbehave, polishing a promotional page does not solve the problem. Testing does.
What do alpha tests actually cover?
Some test passes focus on obvious things such as logging in, moving, opening interfaces, withdrawing items and saving progress. Others inspect less visible details: whether an NPC is reachable, whether a ranged attack has the correct distance and projectile, whether an animation communicates an action and whether rewards persist after reconnecting.
Skilling brings a different set of questions. An action might grant XP but still fail as a useful training method if its object interaction, item consumption, products or banking route is wrong. PvP and death mechanics need their own attention because players rely on predictable rules about risk and items.
That is why progress can look uneven during alpha: different areas are at different stages, and a verified narrow test does not imply that every related encounter or route is finished.
How players can help shape OSastra.
Feedback is most valuable when it describes the player journey. If you cannot reach an activity, include the location and exact route. If a combat action feels wrong, mention the attack type and what you saw. If an inventory interaction fails, list the items involved and the sequence that caused the issue. This helps turn an experience into a reproducible test.
The current Windows client, active build and participation rules must be confirmed through the official Discord. Website registration is not open, and old installation links should not be assumed current. For sensitive issues such as item loss or account security, contact the team privately.
What happens next?
Our priorities are to keep building usable systems, broaden test coverage and communicate progress without pretending that unfinished content is already available. We will announce broader access and any public release plans only when the project is ready to support them.
For a clear snapshot of the project, see the development status and features overview. If you want to contribute, start with the testing guide.