Newcastle gamers meeting in a cafe to plan tournaments

About Dravixom

A Newcastle hub run by players

Walk in, find your squad, play tonight.

Who runs this

Dravixom is an independent, community-run hub at Hunter Street, Newcastle NSW 2300, Australia. We are players, bracket admins and LAN volunteers, not a broadcast network. The site at dravixom.com exists to make Australian online play easier to organise: readable forums, honest tournament listings, active clan pages and local event notes. Contact is direct: support@dravixom.com, +61 2 4900 3361.

Hunter Street Mon–Fri 09:00–18:00

Why we started

A city scene, run on volunteer time

Random queues are fine until you want a real team, a regular night and people who show up. The old Newcastle Gamers Steam group proved a city scene could run LANs and tournaments on volunteer time. Dravixom carries that forward with better archives, clearer listings and open admin decisions.

Anyone in Australia can join. Newcastle sets the working culture — how rulings are written, how brackets get seeded, how a Saturday LAN gets booked and cleaned up. It is one room with a long memory, and the room's habits are what we carry when a new city posts its first fixture.

What we stand for

Four habits, asked of everyone

  1. A

    Show up

    Sign the fixture, arrive at the time you named, message the lead if something changes.

  2. B

    Post scores

    Result, timestamp, and a link to the match if you have one. The board stays readable when everyone does.

  3. C

    Share the server load

    Host a lobby when you can, pass the duties around, don't leave one person carrying every Wednesday night.

  4. D

    Give beginners a lobby as well as advice

    A novice bracket with real matches beats a pile of coaching posts. Both belong here.

Community rules Read the long form

How content stays useful

The board has to still help next month

Editors review boards weekly. Outdated patch guides are archived. Dead clan pages are marked dormant. Event posts are timestamped on every edit. We do not keep teaser blocks or empty hub pages to look busy. If a board has no current activity, it says so and points to the nearest active thread.

Weekly

Boards reviewed

Every thread board gets a read at the start of the week. Fixes, subs, archived patches — all handled in one pass so nothing drifts half-updated.

Ongoing

Timestamps on edits

When a community post changes — a date shifts, a venue moves, an admin swaps — the edit carries its own timestamp. Readers see what moved, not just what's there now.

Retired

Dormant, not deleted

A clan page that thinned out is marked dormant and left in place. Threads are archived, not wiped. Someone coming back in six months still gets the history.

Empty LAN aisle at shift-change with monitors still on

Who handles tournaments and events

Names on every listing, not anonymous rulings

Tournament admins are named on each listing with a contact thread. LAN leads are named on each event post with setup responsibilities. Disputes need match links and timestamps, and outcomes are posted publicly. For larger weekends we add a second admin so decisions do not wait on one person.

Role
Tournament admin
Seeding, rulings and posting outcomes. Named on the bracket listing with a contact thread so any decision has a person behind it.
LAN lead
Venue setup, table plan, power and network, teardown. Named on the event post with their responsibilities spelled out.
Second admin (weekends)
A second pair of eyes on larger weekends so rulings, verification and disputes don't wait on one volunteer for hours.
Board editors
Weekly review of thread boards, archiving outdated guides, marking dormant clan pages. Open about what was changed and why.
Disputes
Filed with match links and timestamps. Outcomes are posted publicly against the listing, not sent privately.

Our take on quality over time

We judge work by whether it still helps after a month

A short scrim template that gets reused, a team comp thread that survives a patch, a venue checklist that saves an organiser an hour. That is long-term value here. Flashy one-off posts fade. Practical ones get pinned — and pinned things are what a returning player finds first.

The same test applies to events. A well-written LAN post tells you the venue, the start time, the spare seat list and who to message. If it can be reread next month and still make sense, it earned its place on the board.

Our standard Reviewed weekly

Money and independence

No prize-pool promises, no paid placements

Dravixom has no prize-pool promises or paid placements on listings. If an event charges entry, the fee, what it covers and refund terms appear in the post. If we help run a LAN, venue costs are stated. Readers should be able to tell community notes from paid venue hire at a glance.

Independence also means we say no. We don't take a fee to push one clan above another on a listing, and we don't trade a bracket slot for a sponsorship line. Community-run means the room pays for itself, and the people running it aren't deciding who wins.

Community rules in plain words

Short, specific, and easy to follow

  • Be specific in posts. A title, a time and a game beats a vague "anyone on tonight".
  • Respect posted skill bands. Novice brackets are for novice players.
  • No smurfing novice brackets. No hate speech, no harassment, no doxxing.
  • Keep spoilers tagged until VODs are public.
  • Organisers may set extra rules per event — those rules appear in the event thread, not buried elsewhere.
Full rules Read and review
A Newcastle venue on Hunter Street in the late afternoon with gamers arriving

Talk to a person

If a listing looks wrong, tell us

Support runs Monday to Friday, 9:00 AM – 6:00 PM. Reports about inaccurate fixtures, dormant pages, or a listing that needs a second admin are read by a person, not a ticket queue. Say what you saw, where you saw it, and what it should say instead.

Dravixom Gaming Community Hunter Street · Newcastle NSW 2300

Cookies

We keep small files that remember your sign-in and your forum view. That is the whole of it — read the cookie policy.