Updating — Hunter Job | Quasar Store | Quasar Store

Updating — Hunter Job | Quasar Store | Quasar Store

Start and read the console

Coming from 1.x, the first start adds the columns the leaderboard needs to your existing qs_hunter table and creates the tables that version did not have:

bash

[qs-hunter] Added missing column qs_hunter.total_experience
[qs-hunter] Added missing column qs_hunter.total_earnings
[qs-hunter] Added missing column qs_hunter.season_experience
[qs-hunter] Added missing column qs_hunter.season_earnings
[qs-hunter] Added missing column qs_hunter.daily_experience
[qs-hunter] Added missing column qs_hunter.daily_earnings

Each line appears once. On every later start the schema is already complete and nothing is printed.

Before	Now
Three NPCs: the employer, a seller and a buyer.	One employer. Missions, the crew, the shop (buy and sell), the statistics and a guide are views inside the same panel.
Buying and selling in context menus.	A shop with category filters, a basket and a sell list with Sell all.
Opening the panel while on a mission asked to abandon it.	The panel opens normally mid-hunt; the footer offers Abandon quest with a confirmation instead of Start Mission.
Changing job left the hunt running.	Losing the job ends the mission on screen, and the server refuses to pay anyone who no longer holds it.
Killing an animal with the wrong weapon was only reported after the whole harvest.	It is reported before the animation starts.
A missing item read as "your inventory is full".	The two are told apart: a missing item names itself, keeps the experience and the mission progress, and prints a console line for the owner.

Setting	What happened
`Config.StartJob.pedSeller` · `Config.StartJob.pedBuyer`	Removed with their NPCs. Only `Config.StartJob.ped` remains.
`Config.AimBlock.enable`	Now ships `false`. In earlier versions the weapon comparison was broken, so the block never actually ran on any server. It works now — and with `global = true` it stops every sniper rifle on the map being fired at players. Turn it on deliberately; see Usage.
`Config.Animals` · `Config.BuyItems` · `Config.Tasks`	Same shape, but now the single source of truth: the server prices every trade, rolls every drop and pays every mission from these tables.
`Config.RemoveWeapon`	Applied by the server from this table; the client only reports that a mission ended.

Removed	What replaced it
`qs-hunter:getPayment`	Missions are paid by the server, from the task in config, the moment it records the last animal harvested.
`qs-hunter:giveItemToPlayer`	Drops are rolled and granted by the server inside the harvest itself.
`qs-hunter:addExperienceOnly`	Experience comes only from items a harvest actually produced and from completed missions.
`qs-hunter:updateGroupQuestProgress`	Progress is recorded by the server after a harvest has been granted.
`qs-hunter:buyItem` · `qs-hunter:sellItem`	`qs-hunter:buyItems` and `qs-hunter:sellItems`, which take item names and quantities only and look every price up in config.
`qs-hunter:removeWeapons`	`Config.RemoveWeapon`, applied by the server when a mission ends or is abandoned.
`qs-hunter:clearDailyQuestCompleted` · `qs-hunter:completeDailyQuest`	The daily and season rankings of the leaderboard, reset by the server at midnight and on the first of the month.
`qs-hunter:sendTreasureToParty`	Nothing — nothing ever listened for it.