Original OX quest by Owsap
This is an unmodified MIT-licensed snapshot of Owsap's OX Event Quest, published in the Sophie-Williams/m2_oxevent repository. Copyright remains with Owsap Productions (2017). The archive contains ox_event.lua, its README, LICENSE and .gitignore. It is a quest-system resource for a compatible server, not a complete server/client pack.

What the script implements
The quest defines scheduled event opening, gate open/close delays, quiz start timing, a maximum winner count, reward item/count and an end delay. Players enter through Uriel (NPC 20011); a separate GM menu uses NPC 20358 and checks GM permissions. The original README explains enabling the ox_event game flag. Leave automatic scheduling disabled while checking your installation.

Check the dependencies before compiling
The script calls your server's oxevent functions, including open, close, quiz, get_attender, give_item and event termination. It also uses notice_multiline; that helper is not defined in this four-file archive. Confirm the matching helpers and quest-function registration in your branch. Your OX map, quiz questions and NPC definitions must already exist. A successful ZIP download does not confirm those dependencies.

The upstream README's compile step is ./qc ox_event.lua from the locale quest directory. Use it only with the compiler and function set appropriate to your own branch, on a disposable test copy first. M2City has not compiled this snapshot or run an OX event.

Review the settings
Keep the schedule's weekday keys in English; use the translation table's second column for display text. Check the server clock and locale against the scheduled times. Review opening/closing delays, max_winners and the reward {50034, 1} against your own item_proto and economy. Verify that the two NPC identifiers and the warp coordinates fit your maps.

A useful staging check
Confirm the helper/function dependencies, compile on a test copy, then inspect the quest compiler output. Test player entry, the GM menu, opening/closing, a quiz round, winner reward and event cleanup. Record the branch, the settings and the observed result before enabling the schedule. Keep a backup of the old quest and event flags. These are suggested checks, not results already obtained by M2City.

Source and validation
The pinned original source retains the author credits and MIT notice. M2City checked all four archive files, relative paths, expanded size, ZIP integrity and SHA-256, and read the quest statically. The current download and checksum are in the catalogue. Discuss integration with a small synthetic example and your exact branch.