Welcome to the information log for VRTX Development’s Anti-Exploit.
CHANGE-LOGS
Change Log: 1.1.4:
-
Added in the ability to add your own extensions to the System,
-
Added the ability for the extension to be detected as a ModuleScript anywhere in ReplicatedStorage aslong as it has
extension
somewhere in it’s name in any capitalisation, -
Added in a new DetectAdonisAdmin configuration which allows the System to detect any instance of Adonis and remove it (such as the Command bar or admin alert),
-
Updated the PrintConfigurations as mentioned in
VORTEX 1.1.3 Console Output Update
, -
Added a
PrintToConsole was set as true but it's a Deprecated feature
warning as mentioned in the Console Output Update. -
Fixed/Changed the V_ReportCommand feature to run on the server instead of the Client, currently working under all tests,
-
Updated the PrintConfigurations as mentioned in
VORTEX 1.1.3 Console Output Update
, -
Changed most events to “SelfCreate” as I call it, this removes the need to have multiple events folders,
-
Changed the V_Events folder to insert in with the V_Inserter rather than having it in with the default V_Admins and V_Configurations.
Note: I am working on making the V_Events folder completely “SelfCreated”. I am also working on adding in a GroupLock to the V_ReportCommand to prevent abuse.
Change Log: 1.1.3:
-
Added in a new EBD feature, allows a developer to enable or disable detections for a specific player on the client (Eg, if they get in a plane that gives them extra health, to prevent being kicked for health exploits, you’d use this),
-
Added in a new IngameAlert feature, this allows you to enable, disable and configure ingame alerts to display for admins and the detected user (Counts down for the detected user, then kicks them if enabled),
-
Added in UseIngameAlerts_PLAYER, UseIngameAlerts_ADMIN, PlayerAlertCountdown and AdminAlertCountdown configurations to the V_Configs module,
-
Added in a new V_SystemFunctions module to the VORTEX_Replicated module which allows for the use of custom functions (Such as
instance:ShowDetectionUI(Player, Reason)
.) -
Changed the V_ServerDetection to not search for the PlayerGui once a player is in the process of being kicked,
-
Changed the V_ActionHandler script to work with the new IngameAlerts system,
-
Changed the V_ClientDetection module to fully prevent scans during EBD protocols.
-
Removed an old script and placed it into the V_ScriptArchive,
Note: There is an issue where the V_Loader and Inserter scripts do not detect the V_DEX_NAMES module, this does not effect the V_ActionHandler nor the V_Configs.Dex_Panel_Detection features.
Change Log: 1.1.2 (bug crunch & misc):
-
Added new support for Version info:
-
Added a comparison from the VORTEX Server to the InfoModule to prevent outdated versions,
-
Added a Version value to the VORTEX Server,
-
Added the ability to detect a studio instance, if detected, it will default to on - for debugging,
-
Added double checking a game’s WL for extra security,
-
Removed V_UI support:
-
Version indication no longer exists via UI,
-
V_UI_Manager has been transferred to a new purpose,
-
V_UI no longer produces errors/warnings via the VORTEX inserter,
-
Removed the reporting system,
-
Removed the configurations related to the former Reporting system,
-
Changed the way the V_Loader checks for modules,
-
Adding the ability to disable/enable certain modules,
-
Changed all prefix’s to match a new capitalisation format,
Change Log: 1.1.2:
-
Added an exemption for Admins during scans,
-
Managed by the V_Admins module, game admins cannot be kicked if found ‘exploiting’,
-
The system automatically adds the game.CreatorId into the V_Admins module (If user owned, then they will be exempt by default),
-
Added Client & Server alerts during scan requests,
-
Says if the player can be scanned (If an admin),
-
Says the Scan Count (Server or Client count),
-
Added a Repair_Nil_Values,
-
If set to true, when an error is found in the V_Configs module, it’ll use default values,
-
If set to false, when an error is found, it will not use default values, and just continue (May error out),
-
Removed the DefaultAdmins being exempt from detections,
-
Only admins chosed by the game owner will be exempt,
-
DefaultAdmins (VRTX Developers) will only have command access,
-
Removed V_DEX_NAMES from the DefaultConfigs module,
-
The system will use the direct path to the DexNames module
-
Changed the PrintToConsole value to be false by default,
-
Adding the ability to detect a studio instance, if detected, it will default to on,
Change Log: 1.1.1:
-
Added an AntiBtools detection,
-
Includes an Anti_Btools configuration,
-
Includes a Kick_If_Btools_Found option,
-
Added a Scan_Interval configuration,
-
Branches for options (Client & Server interval),
-
Defaults at 0.5 (SERVER) and 0.1 (CLIENT),
-
Added a Btools Possible Names module (Similar to the DexNames module)
-
Removed the Kick_If_Btools_Found temporarily,
-
Will default to kicking,
-
Changed the AntiBtools feature to scan both the player(s) backpack, and what they are holding,
-
Changed the contents of the DexNames module
-
Changed the reasoning on the AntiBtools detection:
-
If found being held, it will say Using Btools,
-
If found in a backpack, it will say inserting.
Change Log: 1.1.0:
-
Added player reporting (a player says "!report [User]).
-
Added the ability for the system to detect the closest match to the username given.
-
Added webhook support, including past server detection (if a player was to rejoin after a kick, the log will remain),
-
Added information on the reported players Health, JumpPower and Speed - should help to identify a valid report.
-
Added DexExplorer detection, featuring the ability to detect the DexExplorer with different names, capitalisations and more (if DexExplorer was called D3x, deX_Explorer or any names similar, it’d be detected),
-
Added a version identifying UI, additionally, a future version comparison will be added to check for new updates.
-
Added a Detection method field to the detection Webhook (server or client detection)
-
Added a PrintToConsole option for scanning feedback & report system cooldown updates,
-
Removed the DexExplorer has been detected from the report submission webhook,
-
Removed the detection method from the detection reason,
-
Changed how the detection field is managed on the webhook,
-
Changed the cooldown on the report system to a server side 60 second cooldown,
-
Changed the cooldown feedback to include Seconds after each time,
UPDATE-LOGS
VORTEX 1.1.4 | Miscellaneous update part2:
-
Finished Part 1 of
V_Configs.System.VORTEX_Model
is scripted (Extensions access), finishing up some testing/debugging, -
Added in a preventative measure to ensure the Console will not be spammed with failed to scan warnings from Admins,
-
Added in support for Analytics alerts when it reaches over 100 (The Detections count),
-
Changed
V_SystemFunctions
to display the YourAnAdmin alert and YouHaveBeenDetected alert for the correct amount of time,
VORTEX 1.1.4 | Miscellaneous update:
- Added in a group lock ability to the Reporting system (
GroupIdToUseReport
, if set to 0, no lock will be enabled.) - Added in a new feature to the system/configurations; Danger Zone, these configurations will be quite good, but dangerous.
- Added in a new DisableAll feature to the system, deployed under the Danger Zone; when enabled, all aspects of the system are disabled.
- Added in a warning when the DisableAll feature is enabled → Cannot be disabled to allow for effective ‘bug identifying’ if you mistakenly enable DisableAll and don’t know why the system isn’t running…
VORTEX 1.1.4 | Slight Console Output Update:
- Added in a new PrintExtensionMessages option under PrintConfigs,
- Added in more information regarding PrintConfigs & PrintToConsole (Deprecated)
VORTEX 1.1.3 | Console Output Update:
-
Added in a new PrintConfigs option,
-
Added PrintGeneralOutputs option to PrintConfigs - Outputs Scan info etc when enabled,
-
Added PrintWarnings option to PrintConfigs - Outputs warnings such as outdated version etc,
-
Added PrintErrors option to PrintConfigs - Outputs errors such as failed to locate Humanoid in Character etc,
-
Added in a check to the Client and Console for whether PrintToConsole is set to true - will set to false if so.
-
Changed PrintToConsole to be Deprecated in the V_Configs module,
VORTEX 1.1.3 | New Features & Slight patch:
-
Added in a new PerformanceGuard feature that monitors specified stats in the V_Configs.PerformanceGuard_Stats section and if it goes above a specified value, the player will be kicked. Very useful in combat games that use Kills, Deaths, Heals or even Cash/Money values,
-
Added in a new section to the V_DEX_NAMES module that includes the new Dex version/Alternative version,
-
Added in an AntiNoclip feature that detects when the a few parts of the player character changes state,
-
Fixed the AntiTP detection to prevent players from being kicked when they respawn after dying.
VORTEX 1.1.3 | New Features:
- Added in a new YourAnAdmin UI alert for any admin joining the server,
- Added an AntiUserIdChange detection for the server detection,
- Added a periodical reset for all players UserId to prevent Client changes,
- Added a V_PlayerLog system, this add player values to V_Replicated storage to store a player actual UserId for comparison in AntiUserIdChange detections.
VORTEX 1.1.2 | QOL - EBD Protocol:
- Added in a new ability for game owners to use EBD (Event Based Detection) to toggle detecting on the client at certain time, for example, when entering a plane so the player won’t be detected for ‘travelling an excessive distance’ or flying,
- Adding a new function to the default Roblox functions ( Script:EBD(true or False) for example) to make it easier to manage EBD toggling.
VORTEX 1.1.2 | extras part3:
- Added in a version comparison system,
- If the system is outtdated then all players will be kicked and a warning with be outputted into the console (“The current VRTX version is outtdated, contant the game’s developers.”) - This is to prevent any players bypassing a fix I do, or just to make sure the system is as up to date as possible.
VORTEX 1.1.2 | extras Part2:
- Updated the V_Loader, V_ConfigsHandler, V_ClientLoader & V_ClientDetection in order to reduce bugs when a new player joins, dies, resets, or is detected, a new feature called ClientBackLoad will initiate. ClientBackLoad (CBL) re-loads VORTEX in order to make sure nothing can get past,
- Updated printing sections - Only CLoader and SLoader notifications will bypass the PrintToConsole option in order to display accurate debugging information regardless of settings.
Note: I am going to add a more customisable PrintToConsole section which will include sub options such as PrintSystemMessages (VORTEX Loading & updating), PrintDetectionInformation (Detections of players, scan runs & results from both the Server and Client) and a PrintMiscInformation (VORTEX Information such as the V_ConfigsHandler and administrator information).
VORTEX 1.1.2 | extras:
-
Added in full support for banning,
-
Webhooks automatically state whether the player recieved a ban or kick,
-
DataStores,
-
Unban feature on it’s way,
-
Changed the way the ClientDetection outputs data in accordance to the V_Configs module,
VORTEX 1.1.2 | Update 3:
-
Channged V_InfoModule to contain V.1.1.2 indication,
-
Removed V_Admin commands,
-
Temporary until a bug is fixed,
-
Folder remains,
VORTEX 1.1.2 | Update 2:
-
Added in support for the upcoming V.1.1.3,
-
Fixed the WL prefix on the console output,
-
Fixed the ClientLoader not running,
-
Added in a secondary loading method as a backup,
-
Removed the un-used lines of code to improve performance and readability,
VORTEX 1.1.2 | Update 1:
-
VORTEX now auto updates,
-
Requires the scripts directly from VRTX Development,
-
Any new update will automatically take effect in a new server,
-
Added a :LoadCharacter() function to the inserter,
-
Enables the Local (Client) scripts to take effect,
-
Removed the V_ConfigsHandler from automatically adding admins,
-
No longer adds the game’s ownerID as an automatic admin,
Thanks for reading,
- The VRTX Dev team!