The old tsunami article linked example.com and described unsupported wave-direction, radius and preview controls. This guide covers Niknock’s NKHD_Tsunami, version 1.2.0 at commit 906899d7836d17a3f9e4432b9db32ce8280fd2c7. Its browser-based menu offers Start, Stop, Pause, Reset Water and Close; /tsunami opens that menu.
Creator release and documentation
Use the required name and configuration
Name the resource NKHD_Tsunami as the README requires: its NUI callbacks hardcode that name. Keep fxmanifest.lua, config.lua, the client/server scripts, html and both water XML files together. Configure maxWaterHeight, tsunamiSpeed, tsunamiWaitTime and WaterWaitingTime in config.lua, then start the selected framework before ensure NKHD_Tsunami. WaterWaitingTime changes update frequency and therefore rise speed; it is not a quality preset.
Fix authorization before public use
Config.Framework selects ESX, QBCore or none. The none branch lets everyone open the menu; Config.AdminPermission is not used by the inspected permission function. More critically, the server events for start, stop, pause and water reset do not repeat an authorization check. Restrict those events server-side, verify the framework’s actual permission API and prevent duplicate flood loops. A restricted chat command alone does not protect the event handlers.
Verify water and population recovery
Test joining during a flood, pause followed by stop, repeated starts and resource shutdown on an isolated test server. The client swim-check loop has no exit condition, and the source has no resource-stop cleanup handler. Confirm normal water, population settings and NUI focus are restored after every exit path. The creator’s historical Resmon numbers are not a current benchmark; no synchronized gameplay or performance guarantee is established by this source review.