MinTicketDifferenceWinnerAndLoserTeam = 10 (minimum ticket gap between winning and losing team) MaxPlayers = 80 (maximal players to enable baserape detector / auto nuke) MinRequestsToNuke = 3 (minimum nuke requests in a row to start the NUKE) MinTicketLostPerMinuteLoserTeam = 60 (!IMPORTANT! minimum TLPM rate (ticket lost per min) of LOSING team) MinTicketsLoserTeam = 90 (minimum tickets remaining of LOSING team) MinPlayers = 14 (minimum players to enable baserape detector / auto nuke) the most important key value is the " MinTicketLostPerMinuteLoserTeam" value in main settings. In the SETTINGS area you can customize the following values. if you have more/less players (slots) or a different map you must change the settings! you can find the right settings when you activate the debug mode (" BDDebugInfosInProconPluginConsole = true") and the virtual mode ( BDVirtualMode = true) on a full server. IMPORTANT: the part "SETTINGS" in the code is set for a bf4 server with 32 slots, conquest large, metro / operation locker only. the auto-nuke will not start unless the losing team have less tickets than the winning team. after 3 requests in a row (you can change this value) the auto-nuke is started automatically. If a baserape is detected a nuke request will be sent (preparing nuke). it is a baserape when team1 have a high TLPM rate and team2 a low TLPM rate.Įxample: losing team: 70 TicketLost/Min AND winning team: 5 TicketLost/Min = baserape (preparing nuke) every 30 seconds it checks the TLPM rate (ticket lost per minute rate) each team. This code start a auto-nuke on baserape situation (working with bf4 server + insane limits + conquest map). BF4 baserape detector with auto nuke - insane limits (working code)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |