> For the complete documentation index, see [llms.txt](https://fantasy-scripts.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fantasy-scripts.gitbook.io/docs/weazel-news.md).

# Weazel News

{% embed url="<https://youtu.be/2AAF4meQTGc>" %}

**The complete media system for FiveM.** A real newsroom with reporters, editors, live television, a printed paper, and advertising that actually earns.\
Built for ESX, QBCore and QBox. Everything a news job needs, and nothing your players have to be taught.

**Features:**

* Multi-Framework Support
* Auto-detects ESX, QBCore and QBox.
* Multi-Inventory Support
* Works with ox\_inventory, qb-inventory and ESX items.
* Complete Newsroom
* Write, edit, review and publish from one screen.
* Nine-Stage Workflow
* Draft to front page, with approval at every step.
* Article Versioning
* Every edit is kept. Restore any older version.
* Fifteen Staff Roles
* Intern to Editor-in-Chief, each with its own access.
* Rank Sync
* Job grade sets newsroom access. One setjob runs the staff.
* Permission Overrides
* Give one person extra access without inventing a rank.
* Media Library
* Photos and video with captions, credits and locations.
* Assignment Desk
* Send reporters and photographers out on jobs.
* News Tips
* Any player can send one. Police and EMS scripts can too.
* Interview System
* Request an interview, ask questions, publish the answers.
* Investigations
* Long-form work with evidence and a case timeline.
* Confidential Sources
* Protected identities only cleared staff can ever see.
* Newspaper Editions
* Lay out real pages on a drag-and-drop grid.
* Public Paper
* One command opens the front page, breaking and more.
* Breaking News Cards
* Lands on every screen in the city. Never freezes anyone.
* Live Television
* Run a bulletin from the gallery with a full rundown.
* Real TV Screens
* Any television prop in the world shows the broadcast.
* Teleprompter
* The anchor reads the script straight off the screen.
* Field Kit
* Camera, microphone and boom, with real props and animations.
* Go Live Anywhere
* Set up a live shot in the street. The gallery takes you.
* Live Camera Feed
* The reporter's own view goes out to every television.
* Live Voice On Air
* Stand near a television and hear the reporter talking.
* Advertising Campaigns
* Businesses book adverts. Approve, run and get paid.
* Classifieds Board
* Players browse every advert currently running.
* Ad Revenue
* Money lands in the company account automatically.
* Press Credentials
* Issue passes with serials. Police scripts can check them.
* Staff Reputation
* Track who files, who publishes and who gets read.
* Analytics Reports
* Thirty days of reads, tips and revenue in live charts.
* Full Audit Log
* Every action, approval and payment is tracked.
* Newsroom Inbox
* Staff are told the moment something needs them.
* One-Block Theming
* Change one colour and the whole interface follows.
* Usable Items
* Camera, mic, boom and newspaper as real inventory items.
* Sample Newsroom Included
* Import one file and every screen is full of real content.
* Exports For Your Scripts
* Push tips in, check press passes, open the paper.
* Fully Configurable
* Ranks, colours, TV models, prices, commands and more.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://fantasy-scripts.gitbook.io/docs/weazel-news.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
