Lethal Quests Ascended

Paid Lethal Quests Ascended 1.26

No permission to buy ($45.00)
Overview Updates (6) Reviews (11) History Discussion
This resource is paid, and requires to be purchased

1.26

1739798987310.png

1739798998400.png

1739799008452.png

1739799018801.png

1739799028503.png

1739799046960.png

1.20

Lethal Quests Ascended v1.20
Server API 1.15+ Required and Visual C++ 2022 Runtime Files Required

EXTINCTION FIXES

(no config changes)

1.18

Lethal Quests Ascended v1.18
Server API 1.16+ Required and Visual C++ 2022 Runtime Files Required

Added httppost reward type with the ability to set the "headers" for the post.
Code: 
json
  { //Advanced Feature: Will send an HTTP POST to the url in the command
    "Type": "httppost",
    "Headers": [ //Optional headers to send with the request
      "Accept: application/json",
      "Authorization: Bearer <TOKEN HERE>"
    ],
    "Command": "http://www.someurl.com/eos_id={eos_id}&variable=value" //Advanced feature that requires you to have special handling in place to use.
  }
Updated quest completion checking.
Added the ability to have tribe scores configurable via a formula. (Tribe Score is only available in the UI and is not stored in the database)
JSON: 
  "TribeScoreFormula": "((SUM(PlayerKills)*3) - SUM(TotalDeaths) + (SUM(MinutesPlayed)/60)) / COUNT(*)", //Formula to calculate the Tribe Score
  //You can use any of the database column names in the formula and the formula must return a single value
  //COUNT(*) is the number of players in the tribe
  //SUM() is the total of the stat column for all players in the tribe
  //You can use +, -, *, / in the formula
  //You can use () to group parts of the formula
  //The above example formula is "((Total Player Kills * 3) - Total Deaths + (Total Minutes Played / 60)) / Number of Players"
Added the following to the NameMapping section
"TribeScore": "Tribe Score" //This is a special case for the Tribe Leaderboard
  • Fixed API errors (AB release)
  • Fixed harvest tracking ignore list issue
  • Fixed UI name mappings
  • Added "CryoPodExpirationTime": 1, //number of hours before a cryopod expires valid range from 1-24 //0 = default timer (30 days?) to General
Increased Quest Name size to 200 from 50.
Fixed issue with "K/D" being used in the UI
Added {playerid} as a token that can be used in Command rewards
Added range settings for Wild Dino Kills and Server Event tracking
Code: 
json
    "EventTrackingRange": 33, //Range measured in foundations from the event center for which players need to be inside of to get credit for the Lethal Server Event.
    "DinoKillRange": 15, //Range measured in foundations from the dino for which players need to be inside of to get credit for the kill on a Wild dino.
    "ForceKillRangeForAll": false, //true will awarad players within the range of the dino to get credit for the kill on all dinos //false will give credit to the player who got the kill directly or if the dino is in the `ForcedKillRangeDinos` list all players in range will get credit
    "ForcedKillRangeDinos": [ //List of dinos that will always give credit to all players inside the `DinoKillRange`. Only used if `ForceKillRangeForAll` is false
      "Blueprint'/Game/PrimalEarth/Dinos/Rex/Rex_Character_BP.Rex_Character_BP'",
      "Blueprint'/Game/PrimalEarth/Dinos/Spino/Spino_Character_BP.Spino_Character_BP'"
    ]
(config changes noted above)

1.18 Beta 5

Lethal Quests Ascended v1.18 Beta 5
Server API 1.16+ Required and Visual C++ 2022 Runtime Files Required

Added httppost reward type with the ability to set the "headers" for the post.
Code: 
json
  { //Advanced Feature: Will send an HTTP POST to the url in the command
    "Type": "httppost",
    "Headers": [ //Optional headers to send with the request
      "Accept: application/json",
      "Authorization: Bearer <TOKEN HERE>"
    ],
    "Command": "http://www.someurl.com/eos_id={eos_id}&variable=value" //Advanced feature that requires you to have special handling in place to use.
  }
Updated quest completion checking.
Added the ability to have tribe scores configurable via a formula. (Tribe Score is only available in the UI and is not stored in the database)
JSON: 
  "TribeScoreFormula": "((SUM(PlayerKills)*3) - SUM(TotalDeaths) + (SUM(MinutesPlayed)/60)) / COUNT(*)", //Formula to calculate the Tribe Score
  //You can use any of the database column names in the formula and the formula must return a single value
  //COUNT(*) is the number of players in the tribe
  //SUM() is the total of the stat column for all players in the tribe
  //You can use +, -, *, / in the formula
  //You can use () to group parts of the formula
  //The above example formula is "((Total Player Kills * 3) - Total Deaths + (Total Minutes Played / 60)) / Number of Players"
Added the following to the NameMapping section
"TribeScore": "Tribe Score" //This is a special case for the Tribe Leaderboard
* Fixed API errors (AB release)

(config changes noted above)

1.17

Lethal Quests Ascended v1.17
Server API 1.15+ Required and Visual C++ 2022 Runtime Files Required

Fixed issues with missing quest tracking stats.

(no config changes)

1.16

Lethal Quests Ascended v1.16
Server API 1.15+ Required and Visual C++ 2022 Runtime Files Required

Fixed issue where players received double credit in certain situations.

(no config changes)
Back
Top