Jump to content

All Activity

This stream auto-updates

  1. Today
  2. Yesterday
  3. i think some of admin sometime we need to create event or need to adjust some zone we don't want player to use some skill in that area for some reason but seems igcn not have config to adjust like this way From my idea this config will combination of Skill_UseArea.xml and PlayerKillSystem.xml (in freepkzone config) so config will looklike this <BlockSkill> <Skill ID="XX" Name="XXX"> <Area MapNumber="X" StartX="X" StartY="X" EndX="X" EndY="X" /> <\Skill> <\BlockSkill>
  4. Last week
  5. Bigman

    Release 85.03

    UPGRADE PROCEDURE FOR ANY VERSION BEFORE v85: YOU MUST UPDATE ALL LAUNCHER COMPONENTS TOGETHER AND NOT SELECTIVELY. The reason for that is that this release contains security fixes which depends on every component. Instructions for updating 1. Regenerate your 'Settings' file using 'ManagementTools' v1.5.0.0 2. Update 'LauncherServer' to v1.5.0.0 3. Prepare and deploy Launcher v1.11.0.0 together with the new 'Settings' file, using self-update system (or ship directly to players) a. rename 'IGC.LauncherPremium.exe' provided in this package to 'NewLauncherVersion.exe' b. paste 'NewLauncherVersion.exe' into '%LauncherWebHost%\Launcher\Patches\LauncherUpdate\temp.zip' c. create new directory 'Data\Launcher' and paste the newly generated 'Settings' file (v1.5.0.0) into it d. paste directory 'Data' into '%LauncherWebHost%\Launcher\Patches\LauncherUpdate\temp.zip' e. 'temp.zip' file should contain 2 files now: * ./NewLauncherVersion.exe * ./Data/Launcher/Settings f. open 'L_Version.zip' file and modify 'L_Version.wvd' so it has 1 line which is "1.11.0.0" (including quotes) 4. Once players will press "GameStart", their launcher will update to latest version. (if this fails, you can give them manual patch) ----------------------------------------- IGC.LauncherServer [MOD] allow custom FW rule suffix name (see config.ini)
  6. Bigman

    2 Launcher Server same machine

    there is no way to chose which external (WAN) IP application listen on. you will have to use different port for multiple instance of LauncherServer in any case.
  7. Wizzy

    Release 19.1.3.3 S

    This is a maintenance release to fix common issues reported from previous version.
  8. LaLiTaBluE

    2 Launcher Server same machine

    that's already allow... i have 3 server licenses with 3 launcher licenses.... check your license panel.
  9. tranvutuan

    2 Launcher Server same machine

    Allows additional license purchases for Launcher
  10. Add the option to choose IP to open the ports so it is possible to have 2 launcher servers or more in 1 server with many IP Addresses With this will be necessary to have custom name for the firewall rule for every Launcher Server App open. Reason, keep launcher servers on external machine to avoid CPU load on main game servers machine when idiots make attacks 😃
  11. Grab the Easter Eggs on the Early Easter promotion! Find a selection of great deals we have prepared for you. Make it best Easter for you and your players with selection of our subscription plans, server plugins and fantastic World Creator! Deal #1 - Server Subscription Plans Get one of available server subscription plans 20% off IGC.Premium - Season 6 Episode 3 IGC.Premium Plus - Any past and supported version & any future seasons (currently Season 19 Part 1-3), it also includes Season 6 Episode 3 Overview files features or visit our store directly. The promotion applies to purchase price and not renewals. To apply use following coupon code upon purchase: P-EASTER-2024 - if purchasing IGC.Premium PP-EASTER-2024 - if purchasing IGC.Premium Plus Deal #2 - World Creator Get one of our greatest and newest tool to customize your game world, now 10% off World Creator To apply use following coupon code upon purchase: WC-EASTER-2024 Deal #3 - Server Plugins Get any of our server plugins to enhance your players' experience, 20% off Check available plugins here* * - Flags & Shop plugin is excluded from promotion. To apply use the following coupon for every plugin purchase: PL-EASTER-2024 Deal #4 - Launcher Designs Get any of our designs prepared exclusively for IGC.Launcher (Premium), 20% off Check available designs here To apply use the following coupon for every plugin purchase: LD-EASTER-2024 Promotion valid from 23.03.2024 until 05.04.2024 (inclusive).
  12. Wizzy

    Release 19.1.3.2 S

    [NEW] Added missing Power Chicken mini-event [ADD] Added Ability Card mixes configuration to ChaosBox.ini [MOD] Added extended scheduler to Arca Battle event [MOD] Added extended scheduler to Acheron Guardian event [MOD] Added extended scheduler to Loren Deep event [MOD] Extended BonusEvent configuration by start/end minute [MOD] Extended Bots System by ability of configuring flag item (Flag & Shop plugin required) [MOD] Modified structure of LimitedItemDrop.xml and simplified configuration of the system [MOD] Enabled support of flag items in ItemOptionSystem plugin [FIX] Item Bags could drop zen despite item rate was set to 100% (extremely rare scenario) [FIX] Expired Unicorn could not be sold to shop [FIX] Certain Ability Cards effect was getting stacked [FIX] Event map entry limit reset failed if happened on turn of the month [FIX] Hiding item glow effect did not work for AntiLag plugin [FIX] Rewards were not properly issued at certain scenario for labyrinth of Dimension event [FIX] Monster kill counter for CryWolf event did not work properly [FIX] Inventory bundle option did not work correctly for elemental items [FIX] Dropping ancient item using SetItemRate option from inventory item bag was bugging inventory [FIX] Characters being in off-mode and summoned by party master could experience various of issues [FIX] Muuns repair did not work when character was in Off-Level mode [FIX] Text translation of Flags Shop at Guild Master NPC was not possible [FIX] Setting MaxDayMonsterPerVip in Hunt Point System did not apply configured values correctly to certain VIP types [FIX] Configuration of ability to use specific item by class did not work for Flag Items [FIX] Using /clearinv and /clearbag commands while having flag activated could bug inventory [FIX] Transforming an item into another using Jewel Upgrade System could bug inventory [FIX] Extra damage could apply in PvP (blocked) [FIX] Chaos Goblin could be attacked by combo with damage higher than 1 [FIX] Period items were getting bugged in inventory if expiry time occurred during transaction time [FIX] Helper Plus was not returning player to spot after death if player was member of a party [FIX] Extra Damage was not applied to fourth skills of Grow Lancer class [FIX] Selection of Grow Lancer skills could cause client performance loss on highly crowded areas [FIX] Collecting required number of overlapping item was not resulting in conversion into new item at certain scenario [ADD] Extended English.xml by language bits 848-850 [MOD] Extended DoppelGanger_DropInfo.xml by optional Durability attribute [FIX] Game Server crash
  13. Earlier
  14. Pedro Vinicius

    MU Dashboard

    If you're looking for one, i can provide it! It works with IGCN and does not have hooks or anything like that that will get virus detection
  15. Currently, the Huntpoint Buff system depends entirely on pre-set things. Allow users to edit Buff HuntPoint to their liking. Like skill scripts or formula data.
  16. The 5th damage is too high, even if 25: Absorb PVP damage, (Probability %) is set to 100%, there will be a second kill.
  17. Hope to add one more, pve damage absorption
  18. Flags system is done, the SD Boost Aura effect is too much work with no extra benefits.
  19. Can't, the 5th wings currently cannot support it.
  20. Please add option PvE damage increase +%.
  21. From Original - webzen Wing 5th dont have luck but in this moment we can use jewel of luck add luck to wing 5th. With server hard config, luck so important when ugrade to +15. The best config is add function disable jewel of luck for wing 5th. Thanks!
  22. Dudi

    Arka War and Ice Wind Valley schedule

    Arca Battle & Acheron Guardian -> from 19.1.3.2 S Ice Wind Valley -> soon.
  23. When the game master wants to design the original official, you can set Rate3=0 and Rate4=0 In this case, the game design is more diverse
  24. Hey there! Suggest to add in World Creator very usefull functional: Undo / Redo. For now looks like map designer not have chance for mistake, sometimes we rotate / translate / add objects just for check how it's will looks, sometimes we doing color painting of terrain for understand if this will be better, sometimes we cloning multiply objects by mistake and many other examples where CTRL+Z it's must-have thing. In most nice way (as i can imagine) this feature can be implemented as part of Action History, which can be killer feature. With best regards.
  25. Make an official IGCN dashboard, currently every server has its own dashboard (so there's a demand for it), some better than others. It would be nice if we have an IGCN official dashboard for our clients, it is really useful. Dashboard display event times, invasion time, notify when those events happen, notify when your character dies, and more.
  26. [FIX] Item Editor: unable to set wing core slot to some 5th wings [MOD] Item Editor: now its possible to set wing core type to 5th wings
  27. 1. What is multi-realm configuration of the server? This is the most recommended setup even you are starting with single realm. It allows to offer multiple realms (aka Worlds) under one game client and single account where characters on every realm will be different. Realm is group of servers (channels) represented under unique name and defined by range of server codes, example: Realm 1: Server codes 0-19 (group 0) Realm 2: Server codes 20-39 (group 1) Realm 3: Server codes 40-59 (group 2) and so on.. 2. Understanding purpose of server applications Purpose and maximum instances of different types of game servers is described in Additional Channel configuration tutorial. Beside Game Servers there are additional applications being a part of server applications set, Data Server and Chat Server. In this tutorial we will focus on the first one. Data Server main operation modes Regular Data Server Battle Core Data Server Operating mode is controlled using IsBattleCoreServer setting in config.ini (IGCDS.ini for older version) of Data Server folder. To switch Data Server application to work for purpose of Battle Core Game Server, set above setting to 1. 1.1. Data Server modules The Data Server application in constructed from three different modules JoinServer: taking key part of login process, general accounts operations and cross-channel moves DataServer: handles general data flow between game and database ExDataServer: handles specific data (shared among channel) flow between game and database, it is responsible for Personal Store, Monster Soul, Party, Guilds, Gens, MuHelper, ItemDropLimit, certain rewards distribution The above modules can be turned on or off by changing below settings to 1 or 0. UseJoinServer = 1 UseDataServer = 1 UseExDataServer = 1 Depending of main operational mode of Data Server application (Regular/BattleCore) the modules should be configured as in default file examples provided by us. Regular server: uses all 3 modules BattleCore server: uses Join and Data Server modules, ExData Server should stay disabled 1.2. Understanding how and where to use Data Server application modules JoinServer: can be used only one time for all realms served under single game client Data Server: can be used multiple times to split load within single realm, different game servers can use different instances of Data Server ExDataServer: can be used only once within single realm, all game servers should connect to single ExData Server. 3. Folders structure for multi realm setup The below folders structure is base example of how to start with multi realm Server JoinServer ConnectServer Realm #1 DataServer GameServer_R (one or more) GameServer_A GameServer_M GameServer_C GameServer_I ChatServer Data MapServerInfo.xml Realm #2 DataServer GameServer_R (one or more) GameServer_A GameServer_M GameServer_C GameServer_I ChatServer Data MapServerInfo.xml BattleCore DataServer_B GameServer_B Data MapServerInfo_Global * * - Continue read for further explanation 4. Databases Structure The below structure is base example for the above two realms setup with BattleCore AccountDB: restored from Me_Muonline.sql script R1_CharacterData: restored from MuOnline.sql script R1_Events: restored from Events.sql script R1_ Ranking: restored from Ranking.sql script R2_CharacterData: restored from MuOnline.sql script R2_Events: restored from Events.sql script R2_ Ranking: restored from Ranking.sql script BattleCore: restored from BattleCore.sql script 5. Server configuration (modules) 5.1. JoinServer The Join Server is simply a module from DataServer application. To configure operational JoinServer, copy content of DataServer application into JoinServer folder and configure config.ini as follows: UseJoinServer = 1 UseDataServer = 0 UseExDataServer = 0 JoinServerPort = 56970 DataServerPort = 0 ExDataServerPort = 0 MapServerInfoPath = ..\\MapServerInfo_Global.xml CharacterDB = AccountDB = AccountDB EventDB = RankingDB = 5.2. Data and ExData Server modules (per realm) To configure the Data and ExData Server modules, follow to DataServer folder of every realm, open config.ini (IGCDS.ini for older versions) and configure them using below example: UseJoinServer = 0 UseDataServer = 1 UseExDataServer = 1 JoinServerPort = 0 DataServerPort = 56960 ExDataServerPort = 56906 ChatServerPort = 56980 CharacterDB = R1_CharacterData AccountDB = AccountDB EventDB = R1_Events RankingDB = R1_Ranking Note that all Data and ExData Server module ports should be unique per realm configuration. Change them in config.ini of every realm. Each realm should point to different databases using our previous logic, considering the only shared database is AccountDB, so second realm configuration will be: CharacterDB = R2_CharacterData AccountDB = AccountDB EventDB = R2_Events RankingDB = R2_Ranking 5.3. Data and ExData Server modules (BattleCore) UseJoinServer = 1 UseDataServer = 1 UseExDataServer = 0 JoinServerPort = 56770 DataServerPort = 56760 ExDataServerPort = 56706 CharacterDB = BattleCore AccountDB = AccountDB EventDB = BattleCore RankingDB = BattleCore To configure the Data and ExData Server modules of BattleCore Data Server, follow to DataServer_BattleCore folder, open config.ini (IGCDS.ini for older versions) and configure it using below example: 5.4. Game Server configuration - GameServer.ini Every game server belonging to different realm should be pointed to valid shared and realm-dedicated component. Shared components game server connects to are: Join Server and Connect Server. Every game server should be configured as follows (using default configuration used in this article): JoinServerPort = 56970 ConnectServerPort = 55667 Realm-dedicated components game server connect to are: Data Server, ExData Server. Game Servers from different realms should point to module of realm they belong to: DataServerPort = 56960 ExDBPort = 56906 The GameServer.ini and config.ini (IGCDS.ini for older version) ports configuration should match then. 6. Server Mapping - MapSerevrInfo.xml The MapServerInfo.xml file should be configured with extra care. Misconfiguration of the file will lead in number of undefined issues, such as inability to move, move to invalid servers, double-login (dupe) and other. 6.1. Realm-dedicated Map Server Info The file is by default located in \Data\ folder and should contain information about servers of current realm only, e.g. if configuring realm 2 (server codes 20-39) it should only contain information of server codes from that range and BattleCore server (as per default example). Example 6.2.Global MapServerInfo.xml The file is simply a copy under special name. It should contain information of servers (channels) of every realm and BattleCore. Server components that should point to the file are: Join Server, BattleCore Data Server, BattleCore Game Server, can be configured using MapServerInfoPath from per application config, config.ini (IGCDS.ini for older versions) and GameServer.ini Example file containing info of realm 1 and realm 2 6.3. BattleCore server The BattleCore server is special game server instance handling events where players from different realms can join and compete. That type of Data and Game Servers should be running under single instance only, one for all realms. To configure server mapping properly, point dat and game servers to it properly for MapServerInfo_Global.xml using MapServerInfoPath setting from config.ini and GameServer.ini.
  28. Please make the Arka War & Ice Wind events have more scheduling options such as: different days of the week and times (just like the Hide and Seek event). This would allow administrators to have greater control over event times: We could set up multiple events throughout the week at specific times. Example: <Schedule> <Start Year="-1" Month="-1" Day="-1" DayOfWeek="2" Hour="06" Minute="00" Second="-1" /> <Start Year="-1" Month="-1" Day="-1" DayOfWeek="4" Hour="15" Minute="00" Second="-1" /> <Start Year="-1" Month="-1" Day="-1" DayOfWeek="6" Hour="18" Minute="00" Second="-1" /> </Schedule>
  29. 1. Extending realm by additional channels (sub-servers) To understand how to properly extend realm (aka World) by additional channel it is essential to get familiar with game server types each realm operates on. Realm is group of a servers (channels) containing maximum and total of 20 channels configured with server codes from scope belonging to realm being configured. Example Realm 1: Server codes 0-19 Realm 2: Server codes 20-39 Realm 3: Server codes 40-59 and so on.. Mixing codes from different groups is not allowed. 1.1 Game Server types and their purpose GameServer_R (regular): common game play, Boss Battle Together event, Mini Games, used to extend realm by new channels GameSevrer_A (arca): Arca Battle and Acheron Guardian Events GameServer_C (siege): Loren Deep, Castle Siege and CryWolf Events GameServer_M (market): Loren Market and Event Square maps, Chaos Castle, Illusion Temple Renewal, Illusion Temple Championship, Blood Castle, Chaos Castle, Devil Square Events GameServer_I (instance): Labyrinth of Dimension, Imperial Guardian, 4th and 5th class quest GameServer_B (battlecore): Tormented Square, Tormented Square (Battle), Chaos Castle (Battle), Chaos Castle Survival, requires dedicated Data and Join Servers Every server type should be configured at maximum number of instances per realm depending on game server type. Regular: 1 or more Arca: one only Siege: one only Market: one only Instance: one only Battle Core game server should be only one for all realms. 2. Extending configuration by new channel To add new channel it is necessary to edit 3 files: ServerList.xml located in ConnectServer folder MapServerInfo.xml located in Data folder GameServer.ini located in folder of newly added regular Game Server 2.1 Connect Server - ServerList.xml Default configuration <ServerList> <Server Code="0" IP="PUBLIC_IP" Port="56900" Visible="1" Name="Regular" /> <Server Code="12" IP="PUBLIC_IP" Port="56912" Visible="0" Name="Market" /> <Server Code="13" IP="PUBLIC_IP" Port="56913" Visible="0" Name="Arca" /> <Server Code="14" IP="PUBLIC_IP" Port="56914" Visible="0" Name="Siege" /> <Server Code="15" IP="PUBLIC_IP" Port="56915" Visible="0" Name="Instance" /> <Server Code="480" IP="PUBLIC_IP" Port="56120" Visible="1" Name="BattleCore" /> </ServerList> To add new channel copy line of existing Regular game server type and set it with unique Code and Port <ServerList> <Server Code="0" IP="PUBLIC_IP" Port="56900" Visible="1" Name="Regular1" /> <Server Code="1" IP="PUBLIC_IP" Port="56901" Visible="1" Name="Regular2" /> <Server Code="12" IP="PUBLIC_IP" Port="56912" Visible="0" Name="Market" /> <Server Code="13" IP="PUBLIC_IP" Port="56913" Visible="0" Name="Arca" /> <Server Code="14" IP="PUBLIC_IP" Port="56914" Visible="0" Name="Siege" /> <Server Code="15" IP="PUBLIC_IP" Port="56915" Visible="0" Name="Instance" /> <Server Code="480" IP="PUBLIC_IP" Port="56120" Visible="1" Name="BattleCore" /> </ServerList> Note that PUBLIC_IP must be set to actual WAN IP. 2.2 Map Server - Map ServerInfo.xml Default configuration Similarly to previous file, extend existing sections of ServerList and ServerMapping by entries reflecting existence of new channel. ServerList section <ServerList> <Server Code="0" Initiation="1" IP="PUBLIC_IP" Port="56900" MinEntryGrandReset="-1" MaxEntryGrandReset="-1" MinEntryReset="-1" MaxEntryReset="-1" MinEntryLevel="-1" MaxEntryLevel="-1" Name="Regular1" /> <Server Code="1" Initiation="1" IP="PUBLIC_IP" Port="56901" MinEntryGrandReset="-1" MaxEntryGrandReset="-1" MinEntryReset="-1" MaxEntryReset="-1" MinEntryLevel="-1" MaxEntryLevel="-1" Name="Regular1" /> <Server Code="12" Initiation="0" IP="PUBLIC_IP" Port="56912" MinEntryGrandReset="-1" MaxEntryGrandReset="-1" MinEntryReset="-1" MaxEntryReset="-1" MinEntryLevel="-1" MaxEntryLevel="-1" Name="Market" /> <Server Code="13" Initiation="0" IP="PUBLIC_IP" Port="56913" MinEntryGrandReset="-1" MaxEntryGrandReset="-1" MinEntryReset="-1" MaxEntryReset="-1" MinEntryLevel="-1" MaxEntryLevel="-1" Name="Arca" /> <Server Code="14" Initiation="0" IP="PUBLIC_IP" Port="56914" MinEntryGrandReset="-1" MaxEntryGrandReset="-1" MinEntryReset="-1" MaxEntryReset="-1" MinEntryLevel="-1" MaxEntryLevel="-1" Name="Siege" /> <Server Code="15" Initiation="0" IP="PUBLIC_IP" Port="56915" MinEntryGrandReset="-1" MaxEntryGrandReset="-1" MinEntryReset="-1" MaxEntryReset="-1" MinEntryLevel="-1" MaxEntryLevel="-1" Name="Instance" /> <Server Code="480" Initiation="0" IP="PUBLIC_IP" Port="56120" MinEntryGrandReset="-1" MaxEntryGrandReset="-1" MinEntryReset="-1" MaxEntryReset="-1" MinEntryLevel="-1" MaxEntryLevel="-1" Name="BattleCore" /> </ServerList> ServerMapping section <ServerMapping> <Server Code="0" MoveAble="0" MapNumber="30" DestServerCode="14" Name="Regular to Siege"/> <Server Code="0" MoveAble="0" MapNumber="31" DestServerCode="14" Name="Regular to Siege"/> <Server Code="0" MoveAble="0" MapNumber="34" DestServerCode="14" Name="Regular to Siege"/> <Server Code="0" MoveAble="0" MapNumber="41" DestServerCode="14" Name="Regular to Siege"/> <Server Code="0" MoveAble="0" MapNumber="42" DestServerCode="14" Name="Regular to Siege"/> <Server Code="0" MoveAble="0" MapNumber="79" DestServerCode="12" Name="Regular to Market"/> <Server Code="0" MoveAble="0" MapNumber="92" DestServerCode="13" Name="Regular to Arca"/> <Server Code="0" MoveAble="0" MapNumber="96" DestServerCode="13" Name="Regular to Arca"/> <Server Code="0" MoveAble="0" MapNumber="114" DestServerCode="15" Name="Regular to Instance" /> <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --> <Server Code="1" MoveAble="0" MapNumber="30" DestServerCode="14" Name="Regular to Siege"/> <Server Code="1" MoveAble="0" MapNumber="31" DestServerCode="14" Name="Regular to Siege"/> <Server Code="1" MoveAble="0" MapNumber="34" DestServerCode="14" Name="Regular to Siege"/> <Server Code="1" MoveAble="0" MapNumber="41" DestServerCode="14" Name="Regular to Siege"/> <Server Code="1" MoveAble="0" MapNumber="42" DestServerCode="14" Name="Regular to Siege"/> <Server Code="1" MoveAble="0" MapNumber="79" DestServerCode="12" Name="Regular to Market"/> <Server Code="1" MoveAble="0" MapNumber="92" DestServerCode="13" Name="Regular to Arca"/> <Server Code="1" MoveAble="0" MapNumber="96" DestServerCode="13" Name="Regular to Arca"/> <Server Code="1" MoveAble="0" MapNumber="114" DestServerCode="15" Name="Regular to Instance" /> <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --> <Server Code="12" MoveAble="0" MapNumber="30" DestServerCode="14" Name="Market to Siege"/> <Server Code="12" MoveAble="0" MapNumber="34" DestServerCode="14" Name="Market to Siege"/> <Server Code="12" MoveAble="0" MapNumber="31" DestServerCode="14" Name="Market to Siege"/> <Server Code="12" MoveAble="0" MapNumber="41" DestServerCode="14" Name="Market to Siege"/> <Server Code="12" MoveAble="0" MapNumber="42" DestServerCode="14" Name="Market to Siege"/> <Server Code="12" MoveAble="1" MapNumber="79" DestServerCode="-1" Name="Stay on Market"/> <Server Code="12" MoveAble="0" MapNumber="92" DestServerCode="13" Name="Market to Arca"/> <Server Code="12" MoveAble="0" MapNumber="96" DestServerCode="13" Name="Market to Arca"/> <Server Code="12" MoveAble="0" MapNumber="114" DestServerCode="15" Name="Market to Instance"/> <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --> <Server Code="13" MoveAble="0" MapNumber="30" DestServerCode="14" Name="Arca to Siege"/> <Server Code="13" MoveAble="0" MapNumber="31" DestServerCode="14" Name="Arca to Siege"/> <Server Code="13" MoveAble="0" MapNumber="34" DestServerCode="14" Name="Arca to Siege"/> <Server Code="13" MoveAble="0" MapNumber="41" DestServerCode="14" Name="Arca to Siege"/> <Server Code="13" MoveAble="0" MapNumber="42" DestServerCode="14" Name="Arca to Siege"/> <Server Code="13" MoveAble="0" MapNumber="79" DestServerCode="12" Name="Arca to Market"/> <Server Code="13" MoveAble="1" MapNumber="92" DestServerCode="-1" Name="Stay on Arca"/> <Server Code="13" MoveAble="1" MapNumber="96" DestServerCode="-1" Name="Stay on Arca"/> <Server Code="13" MoveAble="0" MapNumber="114" DestServerCode="15" Name="Arca to Instance"/> <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --> <Server Code="14" MoveAble="1" MapNumber="30" DestServerCode="-1" Name="Stay on Siege"/> <Server Code="14" MoveAble="1" MapNumber="34" DestServerCode="-1" Name="Stay on Siege"/> <Server Code="14" MoveAble="1" MapNumber="31" DestServerCode="-1" Name="Stay on Siege"/> <Server Code="14" MoveAble="1" MapNumber="41" DestServerCode="-1" Name="Stay on Siege"/> <Server Code="14" MoveAble="1" MapNumber="42" DestServerCode="-1" Name="Stay on Siege"/> <Server Code="14" MoveAble="0" MapNumber="79" DestServerCode="12" Name="Siege to Market"/> <Server Code="14" MoveAble="0" MapNumber="92" DestServerCode="13" Name="Siege to Arca"/> <Server Code="14" MoveAble="0" MapNumber="96" DestServerCode="13" Name="Siege to Arca"/> <Server Code="14" MoveAble="0" MapNumber="114" DestServerCode="15" Name="Siege to Instance"/> <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --> <Server Code="15" MoveAble="0" MapNumber="30" DestServerCode="-1" Name="Instance to Siege"/> <Server Code="15" MoveAble="0" MapNumber="34" DestServerCode="-1" Name="Instance to Siege"/> <Server Code="15" MoveAble="0" MapNumber="31" DestServerCode="-1" Name="Instance to Siege"/> <Server Code="15" MoveAble="0" MapNumber="41" DestServerCode="-1" Name="Instance to Siege"/> <Server Code="15" MoveAble="0" MapNumber="42" DestServerCode="-1" Name="Instance to Siege"/> <Server Code="15" MoveAble="0" MapNumber="79" DestServerCode="12" Name="Instance to Market"/> <Server Code="15" MoveAble="0" MapNumber="92" DestServerCode="13" Name="Instance to Arca"/> <Server Code="15" MoveAble="0" MapNumber="96" DestServerCode="13" Name="Instance to Arca"/> <Server Code="15" MoveAble="1" MapNumber="114" DestServerCode="15" Name="Stay on Instance"/> <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --> <Server Code="480" MoveAble="0" MapNumber="30" DestServerCode="-1" Name="Stay on BattleCore (Move Disabled)"/> <Server Code="480" MoveAble="0" MapNumber="34" DestServerCode="-1" Name="Stay on BattleCore (Move Disabled)"/> <Server Code="480" MoveAble="0" MapNumber="31" DestServerCode="-1" Name="Stay on BattleCore (Move Disabled)"/> <Server Code="480" MoveAble="0" MapNumber="41" DestServerCode="-1" Name="Stay on BattleCore (Move Disabled)"/> <Server Code="480" MoveAble="0" MapNumber="42" DestServerCode="-1" Name="Stay on BattleCore (Move Disabled)"/> <Server Code="480" MoveAble="1" MapNumber="79" DestServerCode="-1" Name="Stay on BattleCore (Move Enabled)"/> <Server Code="480" MoveAble="0" MapNumber="92" DestServerCode="-1" Name="Stay on BattleCore (Move Disabled)"/> <Server Code="480" MoveAble="0" MapNumber="96" DestServerCode="-1" Name="Stay on BattleCore (Move Disabled)"/> <Server Code="480" MoveAble="0" MapNumber="114" DestServerCode="-1" Name="Stay on BattleCore (Move Disabled)"/> </ServerMapping> Note that if configuring new channel for server group of higher server codes, e.g. 20-39, the DestServerCode attribute must be also configured to server code of Game Servers from group that is being configured. Use base example for general logic of pointing game server and their types. 2.3 New Game Server - GameServer.ini Being by coping entire 3. GameServer_R folder under desired name. Open GameServer.ini and edit following keys to new values matching previously configured values, as above. ServerName: set to unique name, simplifies game server identity on task bar and in logs ServerCode: set to new server code the game server will run with, in our example it is 1 GameServerPort: set to port the game server will run on, in our example it is 56901 3. New Channel with unique settings It is possible to run newly created channel under unique for that channel settings based on Data folder. To configure new channel this way, place 3. Game Server folder inside new folder together with a copy of already configured Data folder. Such configuration requires to update each copy of Data folder every time such need occurs, e.g. to apply new update or when editing shared files, such as MapServerInfo.xml
  1. Load more activity
×
×
  • Create New...

Important Information


We use technologies, such as cookies, to customize content and advertising, to provide social media features and to analyse traffic to the site. We also share information about your use of our site with our trusted social media, advertising and analytics partners. See more about cookies and our Privacy Policy.