Skip to content
This repository has been archived by the owner on Nov 22, 2021. It is now read-only.

Releases: thelindat/linden_outlawalert

2.7.1

10 May 23:10
a5adce9
Compare
Choose a tag to compare
  • Fixed distress call (wrong variable was being set in the first place, so players could never trigger the notification)

2.7.0

08 May 12:04
88c05ba
Compare
Choose a tag to compare
  • Store if player is dead in a variable (depending on your resource versions, may require editing)
  • Register keymapping G for dead players to send an alert (instead of automatically)
  • Register keymapping Y for players to set a waypoint to the most recent alert
  • Fixed Config.DebugChance, was working in reverse this whole time
  • Fixed spacing and changed some functions slightly

I've learnt a hell of a lot since I make this resource and it's a big ol' mess. Don't expect any updates soon, but I will be remaking it in the future.

2.6.4

27 Mar 17:40
857a905
Compare
Choose a tag to compare
  • Send notifications to all players, then check if they are authorised on the client
  • Moved server callback to a function to be called when resource gets PlayerData or triggers esx:playerLoaded
  • Require argument for 911 calls
  • Send a notification to the player when they send a message to 911

2.6.3

25 Feb 19:48
d90a8a8
Compare
Choose a tag to compare

Fix an error with debugchance not setting to 100%
Attempted fix for Infinity

2.6.2

25 Feb 12:21
941d3a6
Compare
Choose a tag to compare

Resolve an issue when receiving coordinates as table {x = x, y = y, z = z} instead of vector3(x, y, z)

2.6.1

22 Feb 07:45
62e91a8
Compare
Choose a tag to compare

Improved version checking

2.6.0

20 Feb 02:37
ea750b7
Compare
Choose a tag to compare

Resolved an issue from 2.5.0 that would return your own street and zone location instead of the report target
Moved client.lua to client/main.lua
Moved variables and ESX framework related functions to client/esx.lua
Moved timer creation back to config.lua, disabled setting of variables on server
Changed arguments for zoneChance
Removed export getStreetandZone; may cause errors for external custom alerts unless removed

  • You will need to remove both the export and reference to it when sending the dispatchData
  • The location check is now performed by each client when creating the alert

2.5.0

20 Feb 00:50
95ae00c
Compare
Choose a tag to compare

The location of the client sending the report is now checked by the receiving clients instead.

Resolved issue with getStreetandZone() returning nil

16 Feb 06:36
793d338
Compare
Choose a tag to compare

Export used for notifications triggered from other resources

2.4.9

12 Feb 22:21
23029e1
Compare
Choose a tag to compare

Adding check for Config.Shooting to be true before trying to set the Success and Fail timers.
Reduced required speed over the speedlimit to trigger a speeding report.