Wizzy

[NEW] Support of IGC.Dashboard product [MOD] Updated ServerInfo.xml (BMD) structure for purpose of IGC.Dashboard [MOD] Changed name of IGCCS.ini (ConnectServer) to Config.ini to match general patterns used across the files [MOD] Extended structure of Config.ini of ConnectServer application by "Dashboard" section [MOD] Added support for excellent options when using Mysterious Stone on armor-type items [ADD] Added options to verify if required font is installed in Config.ini of game Client [FIX] Game Server crash [FIX] Game Server freeze

1. Assigning dashboard to server license To assign a dashboard license to a specific server license, follow these steps: Have at least one unassigned dashboard license available Follow to server license data form and click on dropdown button to expand available options Click Assign Dashboard Fill Link URL with valid URL pointing to web-accessible location of your dashboard host Click Save to apply the changes 2. Editing dashboard license To edit the details of a dashboard license that is already assigned to a server license, follow these steps: Follow to server license data form and click on dropdown button to expand available options Click Edit Dashboard Details Fill Link URL with valid URL pointing to web-accessible location of your dashboard host Click Save to apply the changes 3. Removing dashboard from server license To remove the dashboard license from the server license, follow these steps: Follow to server license data form and click on dropdown button to expand available options Click Edit Dashboard Details Click the Detach Dashboard red button. Proceed with caution, as no additional confirmation will be requested. * Dashboard license changes might be subject to regular free change allowance. Needed to change dashboard license beyond free allowance scope may require a purchase a license data change service. It can be done by clicking Get More link under Buy Dashboard button. Periodically, change of dashboard data may be free of charge. Subject to change without further notification. ** Single dashboard license can be assigned to only one server license at a time

1. Assigning launcher to server license To assign a launcher license to a specific server license, follow these steps: Have at least one unassigned launcher license available Follow to server license data form and click on dropdown button to expand available options Click Assign Launcher Fill Update URL and Hash URL pointing to two different web accessible locations you will store patches and security hashes Click Save to apply the changes 2. Editing launcher to server license To edit the details of a launcher license that is already assigned to a server license, follow these steps: Follow to server license data form and click on dropdown button to expand available options Click Edit Launcher Details Fill Update URL and Hash URL pointing to two different web accessible locations you will store patches and security hashes Click Save to apply the changes 3. Removing launcher from server license To remove the launcher license from the server license, follow these steps: Follow to server license data form and click on dropdown button to expand available options Click Edit Launcher Details Click the Detach Launcher red button. Proceed with caution, as no additional confirmation will be requested. * Launcher license changes might be subject to regular free change allowance. Needed to change launcher license beyond free allowance scope may require a purchase a license data change service. It can be done by clicking Get More link under Buy Dashboard button. Periodically, change of launcher data may be free of charge. Subject to change without further notification. ** Single launcher license can be assigned to only one server license at a time

Re-activation with no data change In certain cases, activating the license may be necessary even without data changes. Before proceeding, confirm you have an available license change (either a free or purchased service*) and follow the steps below: Click the dropdown button on the license form needing activation, and select Clear Activation. Your Activation Key will be refreshed and ready to use after 3 minutes; copy it and run any of GameServer.exe applications on host identified with IP filled in license form** Activation window will appear, enter the Activation Key and click activate. Your license should be active already. * Any change beyond free allowance requires to purchase a license change service. It can be done by clicking Get More link under Buy Dashboard button. ** If activating on PC the license previously existed make sure to run RemoveLocalLicenseData.reg shipped along with full pack of server suite before proceeding with new license activation.

How to change license data? Each license's data can be modified once every 30 days at no cost. The next available date for a free change is shown in the license header, e.g., Next Free Change on xx/xx/xx. Any changes beyond the free allowance require purchasing a license change service. This can be done by clicking the Get More button located under the Buy Dashboard button. Change of license Fill license data that changed (see points 1-3 of activation guide) Click Update Details Your Activation Key will be generated and become available after 3 minutes; copy it and run any of GameServer.exe applications on host identified with IP filled in license form* Activation window will appear, enter the Activation Key and click activate. Your license should be active already. * If activating on a machine where the license previously existed, run the RemoveLocalLicenseData.reg file (included with the full server suite package) before proceeding with the new license activation.

How to activate server license for first time? Fill IPv4 or Hostname*, the IP must be your public IP of your server machine Fill Server Name, a string of your liking to help identity the license Fill SQL/Database IPv4**, IP address of your SQL server database, leave disabled if all is hosted on same machine; fill when used Hostname in point 1. Click Update Details Your Activation Key*** will be generated and will appear after 3 minutes; copy it and run any of GameServer.exe applications on host identified with IP filled in point 1.**** Activation window will appear, enter the Activation Key and click activate. Your license should be active already. * Hostname is a DNS record that will be resolved by our system to IPv4, it can be updated on your end with actual IP, useful in case of dynamic IP, ** Required when database is located on different host than server. If used hostname, *** License Key can be used only once every license data change, to reset license Key for another activation update license details and click Update Details button or use Clear Activation to proceed without license data change, **** Depending of your environment setup you may need to open port TCP/50235 (for version lower than 17.1.3.25 port is TCP/48235); Version 17.1.3.25 and up requires operating system time to be synchronized with internet time, check the tutorial. If having problems with default time sync servers use the following one: pool.ntp.org

1. Event notification configuration The configuration for event timers and notifications necessitates direct editing of the events.js file found in the web part directory at /Templates/Defaults/js/. Note that a more user-friendly configuration will be introduced in future updates. Open the events.js file and locate following block: var events = [ ["Boss Battle", ["06:30", "15:00", "21:30"],"Boss Battle", "boss"], ["BloodCastle", ["00:05", "01:05", "02:05", "03:05", "04:05", "05:05", "06:05", "07:05", "08:05", "09:05", "10:05", "11:05", "12:05", "13:05", "15:05", "16:05", "17:05", "18:05", "19:05", "20:05", "21:05", "22:05", "23:05",],"BloodCastle", "event"], ["Devil Square", ["00:40", "01:40", "02:40", "03:40", "04:40", "05:40", "06:40", "07:40", "08:40", "09:40", "10:40", "11:40", "12:40", "13:40", "15:40", "16:40", "17:40", "18:40", "19:40", "20:40", "21:40", "22:40", "23:40"],"Devil Square", "event"], ["Chaos Castle", ["00:25", "01:25", "02:25", "03:25", "04:25", "05:25", "06:25", "07:25", "08:25", "09:25", "10:25", "11:25", "12:25", "13:25", "15:25", "16:25", "17:25", "18:25", "19:25", "20:25", "21:25", "22:25", "23:25"],"Chaos Castle", "event"], ["Mirror", ["00:55", "01:55", "02:55", "03:55", "04:55", "05:55", "06:55", "07:55", "08:55", "09:55", "10:55", "11:55", "12:55", "13:55", "14:55","15:55", "16:55", "17:55", "18:55", "19:55", "20:55", "21:55", "22:55", "23:55"],"Mirror", "event"], ["Illusion", ["00:50", "01:50", "02:50", "03:50", "04:50", "05:50", "06:50", "07:50", "08:50", "09:50", "10:50", "11:50", "12:50", "13:50", "15:50", "16:50", "17:50", "18:50", "19:50", "20:50", "21:50", "22:50", "23:50"],"Illusion", "event"], ["Golden Attack", ["01:45", "05:30", "06:15", "15:00", "16:45", "18:15", "21:15"],"Golden Attack", "inv"], ["Red Dragon", ["00:10", "01:10", "02:10", "03:10", "04:10", "05:10", "06:10", "07:10", "08:10", "09:10", "10:10", "11:10", "12:10", "13:10", "14:10", "15:10", "16:10", "17:10", "18:10", "19:10", "20:10", "21:10", "22:10", "23:10",],"Red Dragon", "inv"], ["Medusa", ["20:00"],"Medusa", "boss"], ["Raffle", ["10:00", "14:00", "19:00"],"Raffle", "Event"], ["Last Man Standing", ["03:00", "06:00", "09:00", "12:00", "15:00", "18:00", "21:00"],"Last Man Standing", "Event"], ["Hide And Seek", ["04:00", "11:00", "14:00", "20:00"],"Hide And Seek", "Event"], ["Arca Battle", [3], ["20:00"],"Arca Battle", "event"], // Tuesday ["Castle Siege", [7], ["16:00"],"Castle Siege", "event"], // Saturday ["Scramble", ["00:35", "01:35", "02:35", "03:35", "04:35", "05:35", "06:35", "07:35", "08:35", "09:35", "10:35", "11:35", "12:35", "13:35", "15:35", "16:35", "17:35", "18:35", "19:35", "20:35", "21:35", "22:35", "23:35"], "Scramble", "event"], ["World War",["20:50"],"World War", "Event"], ["Egg Event", ["06:00", "07:15", "16:00", "19:15", "21:45", " 23:45"],"Egg Event", "inv"], ["Deep Gorgon", ["01:15", "04:15", "08:15", "10:15", "13:15", "17:45", "20:50"],"Deep Gorgon", "inv"], ["Zaikan", ["01:00", "04:45", "08:30", "09:45", "12:15", "13:30", "17:15", "18:30", "19:45", "21:05", "22:20", "23:30"],"Zaikan", "inv"], ["Hydra", ["00:45", "03:15", "04:30", "05:45", "09:30", "10:45", "12:00", "14:30", "17:00", "22:00", "23:20"],"Hydra", "inv"], ["Balrog", ["00:30", "03:00", "06:45", "08:00", "09:15", "10:30", "13:00", "14:15", "15:30", "19:20", "20:30", "21:50", "23:00"],"Balrog", "inv"], ["Gorgon", ["02:30", "03:45", "07:30", "11:15", "13:45", "16:15", "18:15", " 21:20", "23:15"],"Gorgon", "inv"], ["Ice Queen", ["00:15", "01:30", "02:45", "04:00", "07:45", "09:00", "11:30", "12:45", "15:15", "19:00", "20:15", "21:35", "22:45"],"Ice Queen", "inv"], ["World Boss", [1], ["14:00"],"World Boss", "boss"], // Sunday ["World Boss", [2], ["09:00"],"World Boss", "boss"], // Monday ["World Boss", [3], ["15:00"],"World Boss", "boss"], // Tuesday ["World Boss", [4], ["18:00"],"World Boss", "boss"], // Wednesday ["World Boss", [5], ["09:00"],"World Boss", "boss"], // Thursday ["World Boss", [6], ["15:00"],"World Boss", "boss"], // Friday ["World Boss", [7], ["18:00"],"World Boss", "boss"] // Saturday ] The actual block content may vary from what is shown above due to potential updates to the application. The system can identify two types of entries, consisting of 4 and 5 elements. Four elements example ["Boss Battle", ["06:30", "15:00", "21:30"],"Boss Battle", "boss"], "Boss Battle" - Display Name ["06:30", "15:00", "21:30"] - Array of event schedule "Boss Battle" - Event notification name "boss" - type of event Five elements example ["World Boss", [1], ["14:00"],"World Boss", "boss"], "World Boss" - Display Name [1] - Day of week ["14:00"] - Array of event schedule "World Boss" - Event notification name "boss" - type of event, used for filters The last argument, event type allows to define following values event inv boss The day of week argument defines days as follows [1] - Sunday [2] - Monday [3] - Tuesday [4] - Wednesday [5] - Friday [6] - Saturday The events.js file includes several hard-coded texts that may need to be modified directly within the file if necessary. These texts may be moved to a dedicated settings file in future updates. starts in 5 minutes! Started! "Sun", "Mon", "Tue", "Wed", "Thu", "Fri", "Sat" 2. Templates and customizations Templates system can be found within the dashboard systems. Custom modifications to default template, same as custom templates are beyond support scope of the product. You are permitted to modify existing HTML, CSS, and JS files (some JS files are obfuscated), as well as create your own custom templates. However, it's important to note that when creating a custom template, you must retain certain internally used names.

1. Files configuration Before beginning the patch preparation, configure the necessary files. There are two files that need to be set up before the Dashboard files can be placed in their target location: \Server\ConnectServer\config.ini \Client\Data\Local\ServerInfo.bmd (XML) 1.1 ServerInfo.bmd (XML) Open the ServerInfo.xml and locate the following (supported files version required): <Dashboard Enabled="0" ExeName="Dashboard.exe" Path="Dashboard" IsNative="1" MainProcessName="main" MemoryShareName="IGCDashBoard" /> Enabled: Activates or deactivates run of the dashboard, 0/1, ExeName: The name of dashboard binary, including file extension, Path: Path to the dashboard binary file, relative to the game client root folder. Do not include leading or trailing slashes; this field can be left blank to run the dashboard from the client root, IsNative: Set to 1 if using IGC Dashboard, otherwise leave disabled, 0/1, MainProcessName: The actual name of the game client binary file, which defaults to "main," excluding the file extension, MemoryShareName: A unique name that allows the dashboard and client to share character and server information. Use alphanumeric characters only. Encode the file to BMD using ToolKit Lite or Premium. 1.2 Config.ini (ConnectServer) Open the config.ini of ConnectServer and locate the following (supported files version required): [Dashboard] MemoryShareName = IGCDashBoard DiscordAppID = 0 MemoryShareName: A unique identifier that enables the dashboard and client to share character and server information. It must match the configuration in ServerInfo.bmd (XML). DiscordAppID: Accepts the Discord application ID for purpose of Discord Rich Presence. Requires external configuration as outlined in the Discord documentation, 0 to ignore. Information To obtain Discord App ID configured Discord Account and Server/Community is required. Go to https://discord.com/developers/applications and create new application. For detailed guide refer to Discord Documentation. Short Guide Open Discord Application center: https://discord.com/developers/applications Click New Application → enter application name, it will be displayed as your Rich Presence main name Accept Terms & Conditions → click Create Copy Application ID Fill other necessary data, such as application description website URL/Legal/Privacy URLs, other as required → click Save Changes 2. Client dashboard patch files By default, the dashboard files are located in the Dashboard folder, which should be placed in the root directory of the Game Client, alongside main.exe. It might be necessary to modify the location of the dashboard files according to the earlier configuration in ServerInfo.bmd (XML). Once dashboard files are on its place, locate two files and open them in text editor: setting.json Strings.xml setting.json { "DashBoardPath": "Dashboard", "RestoreProcessOnClose": true } DashBoardPath: Path to the dashboard binary file, relative to the game client root folder. Must match configuration of Dashboard Path in ServerInfo.bmd (XML). RestoreProcessOnClose: Determines whether to restore hidden game client processes when the dashboard application is closed. If set to false, the game client window can only be restored by reattaching the game client processes after running the dashboard application. The window_handle.json file cannot be manually modified; if it has been altered, it may be necessary to terminate the game client processes via Task Manager. Strings.xml The file contains language strings that can be translated to desired language. Ensure the file encoding is always set to UTF-8. Point particular attention to explanatory comments located in the file. This tutorial will only clarify purpose of selected strings from DISCORD and GENERAL sections. <General> <String Id="0" Text="Blue MU Server" /> <String Id="1" Text=" died!" /> <String Id="2" Text="The application is running in the background, check your tray." /> <String Id="3" Text="Blue MU - Dashboard" /> </General> <Discord> <String Id="0" Text="Season 19, come play with us!" /> <String Id="1" Text="Part 2-3" /> <String Id="2" Text="SITE" /> <String Id="3" Text="https://mydomain.com" /> <String Id="4" Text="DISCORD" /> <String Id="5" Text="https://discord.gg/AFSDFgdFHG" /> <String Id="6" Text="image_large" /> <!-- Large Image Key --> <String Id="7" Text="Let's go!" /> <!-- Large Image Description --> <String Id="8" Text="Level: " /> <String Id="9" Text="Character: " /> <String Id="10" Text="Part 2-3" /> <String Id="11" Text="Season 19, come play with us!" /> <String Id="12" Text="image_small" /> <!-- Small Image Key --> <String Id="13" Text="Let's go!" /> <!-- Small Image Description --> </Discord> General 0: Server name, title used across multiple places, e.g. Windows Notification Balloon. 1: Part of character death notification, placed after character name, e.g. Black Mage died! 2: Text that will appear on notification balloon when minimizing the dashboard application before it goes to tray area 3: Text that will appear when placing mouse over the tray icon Discoed 0: Rich presence details text to mention 1: Rich presence state text to mention 2: Label text for website button, can be used for other purpose 3: The URL of the website 4: Label for Discord Invitation button, can be used for other purpose 5: Discord server invitation URL 6: A name (key) of image file used for large image avatar in rich presence, can be left blank 7: Description text for large image avatar 8, 9, 10, 11: Static texts used for purpose of rich presence update notifications 12: A name (key) of image file used for small image avatar in rich presence, can be left blank 13: Description text for small image avatar Information To get valid value for purpose of Discord strings 6 and 12 (large/small image key) go to https://discord.com/developers/applications, edit previously created application and upload the images under Rich Presence → Art Assets tab. Short Guide Open Discord Application center: https://discord.com/developers/applications Left click on previously created application Open Rich Presence → Art Assets tab Copy Application ID Under Rich Presence Assets section click Add Image The name under the file was uploaded with be a key value for small/large image Newly uploaded Images may appear under Rich Presence Assets area even after 45 minutes from upload time. Avoid reuploading the files. You may continue to configure your rich presence by completing all available fields and uploading Invitation Cover Image. 4. Change of Dashboard icon The binary file icon cannot be changed, however it is possible to override icon visible on the taskbar and system tray. To do this, place an ICO-format icon file with the appropriate name in the root folder of the dashboard.

1. Uploading the files to the web hosting Once your web hosting environment meets the necessary requirements, locate the previously downloaded and extracted files, and upload the contents of the Web folder to your web server. It is recommended to place these files in a dedicated folder, such as dashboard. You can then access the Dashboard directly via your domain (e.g., https://yourdomain.com/dashboard/) or by setting up a dedicated subdomain pointing to the dashboard folder on your server. 2. Files Configuration Go to the location of your newly uploaded files and open Defines.php. You will see the following: <?php define('TEMPLATE_DASHBOARD','Default'); define('URL_DEFAULT','https://mydomain.com/files/dashboard'); // No / at the end define('SUB_DIRECTORY', '/files/dashboard'); // No / at the end define("CACHE_PATH","Cache"); define('CONFIG_HASHER_KEY_CACHE','Wd5uPbTyq62ApNHHrMSnCyVbFgtHyuJg'); define('CONFIG_HASHER_KEY_GENERAL','Wd5uPbTyq62ApNHHrMSnCyVbFgtHyuJg'); TEMPLATE_DASHBOARD: Specifies the name of the template folder located in the Templates directory. URL_DEFAULT: The web-accessible address for the dashboard, which can either be a subdomain pointing to the folder where the dashboard files are located or a simple address that includes the folder path. SUB_DIRECTORY: The value of SUB_DIRECTORY can be configured in two ways, depending on the URL_DEFAULT configuration: If URL_DEFAULT is set to a subdomain (e.g., https://dash.mydomain.com), then SUB_DIRECTORY should be set to a forward slash: / If URL_DEFAULT is configured with a folder path (e.g., https://mydomain.com/files/dashboard), then SUB_DIRECTORY should be set to the absolute path of the dashboard location, starting from the web hosting root. CACHE_PATH: The location of the Cache folder, relative to the dashboard folder. CONFIG_HASHER_KEY_CACHE and CONFIG_HASHER_KEY_GENERAL: Both require a hash key for encrypting cache files and other related components. Information The value configured for URL_DEFAULT must match value of Link URL set in License Manager when assigning dashboard to server license. 2.1 Directories permissions Depending on your environment setup, it may be necessary to make the cache folder writable. The default cache folder is named Cache. 2.2. Confirm the validity of the setup To ensure everything is configured correctly, copy the value set in URL_DEFAULT and paste it into your browser. The dashboard should display and no errors should be thrown, otherwise review your setup and do not move forward to license activation. 3. License Activation The dashboard application is licensed on a per-server instance basis, meaning each dashboard license is tied to a specific server license. Consequently, the dashboard can only be utilized within game servers operating under the assigned server license. Once server files are placed on your server machine and you have not activated your license yet, make sure to follow the licensing system guides and proceed with license activation. A brief step-by-step guide is also available on the License Manager page.

1. Dashboard requirements The Dashboard is a WebView application that uses client-side application to display web content hosted on a server side, therefore the technical requirements must be met either on server and client side. 1.1 Web Hosting PHP >= 8.0 Rewrite engine support to handle .htaccess rules: Mod Rewrite WebServer, e.g. Apache, LiteSpeed, Nginx, Microsoft IIS Information In case of using Microsoft IIS web server the .htaccess must be rewritten to supported format or .htaccess supporting module must be installed. 1.2 Client side Microsoft .NET Framework, version 4.8 - Download Windows 7 or later Operating System 2. Downloading and extracting server files Download the file and extract the archive to your preferred location on your personal or web server's disk. You will see two folders: Web and Client. The purpose of each folder's contents will be explained in later sections of the Dashboard guides.

[FIX] Game client crashed when hovering over required item image within Event Information window [FIX] Game client was becoming laggy during Illusion Temple Renewal event [FIX] Party experience calculation was improper what resulted in too high party experience in 19.2.3.11 [FIX] Opening time was invalid for Devil Square event in Event Information window

[FIX] Boss Battle start time under Event Info Window did not display correctly [FIX] Master level was getting corrupted after killing a monster after reaching maximum master level [MOD] Removed "Strings" section from Hide And Seek event plugin configuration file and added it to English.xml [MOD] Removed "Strings" section from Raffle plugin configuration file and added it to English.xml [FIX] Experience was split in favor of first party in scenario second party started to attack same monsters [MOD] Changed default maximum punish damage limit to 250000 in CalcCharacter.ini [MOD] Updated default attack speed formula for Elf class in CalcAttackSpeed lua function in CalcCharacter.lua [FIX] Corrected default maximum attack speed for DW, DW, LM, LW classes in CalcCharacter.ini [FIX] Corrected default rates for selected mixes in ChaosBox.ini [FIX] Corrected default values of Mastery Seals (14,225-232) in ItemAddOption.bmd, ItemOptionManager.xml, BuffEffect.txt, BuffEffectManager.xml [FIX] Corrected missing rendering data for mastery lightning items for KOR language patch in EnchantEffect.txt [FIX] The SocketCount attribute did not handle -2 value for all configuration files of Chaos Cards [FIX] Item ToolTip became corrupted and client got stuck when number of lines in ToolTip exceeded 40 [FIX] Game Server crash

[FIX] Game Server crash