Jump to content

Recommended Posts

Posted

Lineage II Private Server Setup Guide

 

 

Extract your Lineage2 Server (170MB+) files onto a directory. Extract L2server.zip (1.81 MB) into your Server's root directory that contains CacheD, L2LogD, L2NPC, NewAuth, etc. Overwrite all the files when prompt. Extract DBScript.zip (103.4 KB) into your Server's root directory that contains the folder DBScript and override all the files.

 

 

 

When installing MSSQL. Make sure you take note of the account/user login and password!! You'll need them for later. Here's a quick walkthru installation guide:

 

 

 

Make sure you choose "Local Computer"

 

Then "Creater a new instance of SQL Server, or install Client Tools" //or something similar. If you don't have this option prompt. Don't worry about it. You get this if you're installing again for the 2nd time.

 

Make sure you pick "Server and Client Tools" along the way in the installation process.

 

It'll automatically check "Default" for instance name or you can specific one. It doesn't really matter which one you pick as long as you remember the instance name.

 

Along the way in the installation process, make sure you pick an option that uses Both MySQL Login and Windows Login.

 

 

-----------------------------------------------------------------------------------------------

 

IP Configurations

Go to your Lineage 2 Server folder.

 

 

 

In each of these following folders: L2LogD, CacheD, NewAuth, PetitionD, L2NPC, and L2Server, they contain a configuration file that is either a *.ini or *.txt document. You don't need to change anything and make sure they're set at 127.0.0.1. The only time you would need to change them is if you are loading them from multiple computers! It doesn't matter if you even have a router! As long as you are loading all 6 Process from the same machine, you just need to keep most of the IP adress as 127.0.0.1.

 

Change the following lines in config.txt under "NewAuth\etc" folder:

 

DevServerIP="24.68.124.198" //Change this to your Internet IP address, your WAN, the IP that you get from your ISP. Visit www.whatismyip.com to find it.

 

logdip="127.0.0.1" //Change this to what you used for your L2LogD.ini address.

 

Change the following lines in l2cache.ini under CacheD folder:

 

address="127.0.0.1" //Change this only if you plan to load this from a different computer! Adjust it to the ip of that computer! If PC2 has IP of 192.168.0.121 and it is planning to load L2CacheD.exe there. Then change it, otherwise leave it as 127.0.0.1!

 

 

 

Change the following lines in l2logd.ini under L2LogD folder:

 

address="127.0.0.1" //Same thing as L2CacheD.ini

 

 

 

Change the following lines in config.txt under PetitionD\etc folder:

 

webAuthServer="127.0.0.1" //Same thing as L2CacheD.ini

 

 

 

Change the following lines in L2NPC.ini under L2NPC folder:

 

//Change them accordingly to what you adjusted for them. If L2LogD.ini has ip of 192.168.0.121 on PC2. Then change that IP in L2NPC.ini to that. You are pointing L2NPC.exe to connect to the other Server Processes. Leave the ports alone!

 

 

 

[LogD]

 

address="127.0.0.1"

 

port=3999

 

 

 

[CacheD]

 

address="127.0.0.1"

 

port=2008

 

 

 

[server]

 

address="127.0.0.1"

 

port=2002

 

 

 

[map]

 

directory="map"

 

 

 

[World]

 

WorldId=1

 

 

 

[db]

 

address="127.0.0.1"

 

user="gamma" //This should be your MSSQL Login (I used sa since it sets up the sa account for you when you install SQL and sa has all permissions)

 

password="l2online" //This should be your MSSQL Password

 

[setting]

 

;Country=0 KR

 

;Country=1 US

 

;Country=2 JP

 

;Country=3 TW

 

;Country=4 CN

 

Country=1 //Change this accordingly to what "CLIENT" version you allow to connect!

 

ExceptionMailing=false

 

MailServer=ncs-mail.ncsoft.co.kr

 

 

 

Change the following lines in l2server.ini under L2Server folder:

 

//Again, the same explaination from L2NPC.ini config applies here as well!

 

[LogD]

 

address="127.0.0.1"

 

port=3999

 

 

 

[CacheD]

 

address="127.0.0.1"

 

port=2006

 

 

 

[AuthD]

 

address="127.0.0.1"

 

port=2104

 

 

 

[petitionD]

 

address="127.0.0.1"

 

port=2107

 

WorldId=1 //Leave this as 1 if you don't plan to run multiple servers! WorldId = ServerId in lin2db (will be explained furtherdown). If they're not the same number, your server won't be connecting to the same gameworld or won't find one to connect to!

-----------------------------------------------------------------------------------------------

 

 

 

 

------------------------------------------------------------------------------------------

 

Setting up Database Scripts

 

------------------------------------------------------------------------------------------

 

 

 

Important! - If you are running MSSQL Server on the same machine that's hosting the server. Leave everything at 127.0.0. and 127.0.0.1!! The only time you would need to change this is if you're trying to connect to a different computer running Lineage 2 Chronicle One Server! You would then need to adjust it accordingly to that computer's IP!

 

 

 

Important!! #2 - If you already have an existing mysql db installed and are changing connection to connect to a different MSSQL Server (say to your friend's computer). You will need to update your MSSQL database information again. By doing this, make sure you export all your previous data! Because if you input the new IP changes, everything from the previous data will be lost! All character and account information are stored in lin2db and lin2world!

 

 

 

open lin2comm_new.sql under DBScript

 

 

 

find

 

set @conn_str = '127.0.0.' + @world_id + ''';''sa'';''l2online'

 

change 127.0.0. to the first 3 sets of numbers of your internal IP (If your internal IP is 192.168.0.121 then enter 192.168.0.)

 

change "sa" as your SQL database account

 

change "l2online" as your SQL database password

 

there are 3 lines you have to change

 

find

 

'SQLOLEDB', '127.0.0.1';'sa';'l2online'

 

change 127.0.0.1 to your internal IP

 

change "sa" as your SQL database account

 

change "l2online" as your SQL database password

 

there is only 1 line you have to change

 

save and close the file.

 

open lin2world_20040609_all.sql under DBScript

 

find

 

set @conn_str = '127.0.0.' + @world_id + ''';''sa'';''l2online'

 

change 127.0.0. to the first 3 sets of numbers of your internal IP (If your internal IP is 192.168.0.121 then enter 192.168.0.)

 

change "sa" as your SQL database account

 

change "l2online" as your SQL database password

 

there are 3 lines you have to change

 

 

 

find

 

'SQLOLEDB', '127.0.0.1';'sa';'l2online'

 

change 127.0.0.1 to your internal IP

 

change "sa" as your SQL database account

 

change "l2online" as your SQL database password

 

there are 2 lines you have to change

 

save and close the file

 

--End Part I

 

 

 

----------------------------------------------------------------------------------------------

 

Setting up MSSQL Database for Lineage 2

 

----------------------------------------------------------------------------------------------

 

 

16pj3.jpg

 

Make sure the SQL server is running, Open Service Manager (found in start menu) and if the start/continue button isn't greyed out click it.

 

 

 

Open SQL Server Enterprise Manager (start menu again), double click SQL Server Group, double click (local) the click OK. Double click on databases folder, to make a database right click and select New Database. Make the following databases: lin2world, lin2comm, lin2log, lin2report, lin2db, petition

 

 

 

 

 

If you used "sa" as your account you dont have to give permissions cause they already are set, if you used another account you have to make it and give permissions to the databases.

 

 

 

Go to the tools menu, then click SQL Query Analyser.

 

 

 

 

 

Change the database drop down menu on the top bar to lin2world. Then click the Load SQL Script button (Also on the top bar). Choose lin2world_20040609_all.sql (Located in the DBScript folder). Click the Parse Query button (blue check mark icon) then once that is done click Execute Query (The green triangle icon). After this is complete go file save.

 

 

 

Change the database drop down menu on the top bar to lin2comm. Then click the Load SQL Script button (Also on the top bar). Choose lin2comm_new.sql (Located in the DBScript folder). Click the Parse Query button (blue check mark icon) then once that is done click Execute Query (The green triangle icon). After this is complete go file save.

 

 

 

Change the database drop down menu on the top bar to lin2log. Then click the Load SQL Script button (Also on the top bar). Choose lin2log_20040416.sql (Located in the DBScript folder). Click the Parse Query button (blue check mark icon) then once that is done click Execute Query (The green triangle icon). After this is complete go file save.

 

 

 

Change the database drop down menu on the top bar to lin2report. Then click the Load SQL Script button (Also on the top bar). Choose lin2report_20040416.sql (Located in the DBScript folder). Click the Parse Query button (blue check mark icon) then once that is done click Execute Query (The green triangle icon). After this is complete go file save.

 

 

 

Change the database drop down menu on the top bar to lin2db. Then click the Load SQL Script button (Also on the top bar). Choose lin2db_AuthDBSchema.sql (Located in the DBScript folder). Click the Parse Query button (blue check mark icon) then once that is done click Execute Query (The green triangle icon). After this is complete go file save.

 

 

 

Change the database drop down menu on the top bar to lin2db. Then click the Load SQL Script button (Also on the top bar). Choose lin2db_update.sql (Located in the DBScript folder). Click the Parse Query button (blue check mark icon) then once that is done click Execute Query (The green triangle icon). After this is complete go file save.

 

 

 

Change the database drop down menu on the top bar to petition. Then click the Load SQL Script button (Also on the top bar). Choose petition.sql (Located in the DBScript folder). Click the Parse Query button (blue check mark icon) then once that is done click Execute Query (The green triangle icon). After this is complete go file save.

 

 

 

Close SQL Query Analyzer and open SQL Server Enterprise Manager. Under databases click lin2db then double click the tables icon. Right click on the server table go open table, then select return all rows. Add the following information:

 

 

44wa1.jpg

 

To add information in for the example [ id = 1 ] you would put the number 1 in the id column:

 

id = 1

 

name = same as the worldname in l2server.ini

 

ip = your external IP

 

inner_ip = your internal IP

 

ageLimit = 0

 

pk_flag = 0 PK not allow; 1 allow

 

kind=0

 

port=7777

 

 

 

Close the SQL Server Enterprise Manager.

 

 

-----------------------------------------------------------------------------------------------

 

DSN Configuration

 

-----------------------------------------------------------------------------------------------

 

 

 

Open control panel, click administrative tools, then double click Data Sources (ODBC).

 

 

57mw.jpg

 

Choose the File DSN tab then click the add button. Select SQL Server and click next, type lin2world. Leave description blank and select (local) in the server dropdown menu then click next. Leave it on windows NT configuration and click next. Check the box next to Change Default Database to, then select the lin2world database and click next, then click finish and ok.

 

 

 

Click add button again. Select SQL Server and click next, type petition. Leave description blank and select (local) in the server dropdown menu then click next. Leave it on windows NT configuration and click next. Check the box next to Change Default Database to, then select the petition database and click next, then click finish and ok.

 

 

 

Click add button again. Select SQL Server and click next, type lin2comm. Leave description blank and select (local) in the server dropdown menu then click next. Leave it on windows NT configuration and click next. Check the box next to Change Default Database to, then select the lin2comm database and click next, then click finish and ok.

 

 

 

Click add button again. Select SQL Server and click next, type lin2log. Leave description blank and select (local) in the server dropdown menu then click next. Leave it on windows NT configuration and click next. Check the box next to Change Default Database to, then select the lin2log database and click next, then click finish and ok.

 

 

 

Click add button again. Select SQL Server and click next, type lin2report. Leave description blank and select (local) in the server dropdown menu then click next. Leave it on windows NT configuration and click next. Check the box next to Change Default Database to, then select the lin2report database and click next, then click finish and ok.

 

 

 

Click add button again. Select SQL Server and click next, type lin2db. Leave description blank and select (local) in the server dropdown menu then click next. Leave it on windows NT configuration and click next. Check the box next to Change Default Database to, then select the lin2db database and click next, then click finish and ok.

 

 

-----------------------------------------------------------------------------------------------

 

System INI Configuration

 

-----------------------------------------------------------------------------------------------

 

 

Go to your control panel (from start menu) then click the system icon, advanced tab, under performance click settings, then choose the advanced tab again and click the change button under virtual memory. Set Custom size with minimum set at 1024 and maximum set at 4096

 

 

 

You must do this to run all the NPC's.

 

 

 

Locate your boot.ini file in C:\ Drive. You'll need to change folder view setting to include hidden and system files or else you won't be able to find it.

 

 

 

Open C:\Boot.ini in notepad, the last line should look like:

 

 

 

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /nodetect

 

 

 

or something similar, add the /3GB tag at the end. It should look like this (if your line was the same as the line above)

 

 

 

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /nodetect /3GB

 

 

 

Reboot your computer

 

 

 

-----------------------------------------------------------------------------------------------

 

ASP Account Registeration System

 

-----------------------------------------------------------------------------------------------

 

 

Extract L2Asp.zip to your C:\Inetpub\wwwroot (or wherever you have as your IIS root directory, this is default)

 

 

 

If you don't have Internet Information Services installed. Then you'll need to find your Windows XP Pro CD. Go to Add/Remove Program and select "Add/Remove Windows Components" -Select Internet Information Services from the list and install it.

 

 

 

Open the conn.asp (from the directory that you just extracted to) with notepad and change the following:

 

ms_sql_server_host_addr = "127.0.0.1" //This should be set to your WAN IP. Leave it as 127.0.0.1 if you want to just manually make accounts on your computer for your friends.

 

 

 

sql_server_username = "sa"

 

sql_server_password = "l2online"

 

save and close the file.

 

 

 

Open control panel, click administrative tools, then double click Internet Information Services. Click on local computer then click websites. Right click default websites and go properties. Click on the documents tab and then the add button. Under default document name type index.asp then press OK. Select index.asp and use the up arrow to move it to the top of the list then press OK.

 

 

67qx1.jpg

 

 

Close IIS and open internet explorer and type http://127.0.0.1 (where 127.0.0.1 is your internal IP)

 

Once the website comes up click register. Then enter a username and a password and click next.

 

 

 

You have now made an account on your server.

 

 

-----------------------------------------------------------------------------------------------

 

Client Setup

 

-----------------------------------------------------------------------------------------------

 

 

Install your Lineage 2 Chronicle ONE Client (either download it or off a CD). Chronicle 2 Client will NOT WORK on C1 Private Server!

 

If you want things to be in english, install the US client and unzip l2cnpatch.zip, c2textures and l2cnmeshes.zip to your /System/ directory.

 

 

 

Unzip Fixed15-10-2004html.zip to your server directory (\L2server\html\) and overwrite all the files.

 

 

 

Extract l2decrypt.zip to your computer (doesnt matter where). Run the decrypter and decrypt the L2.ini file. Then open up L2.ini file with notepad.

 

 

 

"L2.ini"

 

 

 

MapExt=unr

 

EXEName=l2.exe

 

SaveExt=usa

 

Port=7777

 

Class=LineageWarrior.MFighter

 

ServerAddr=69.105.31.9 //Change it to your WAN IP

 

IsL2NetLogin=True

 

IsL2Console=True

 

IsL2Seamless=True

 

IsL2Projector=True

 

 

 

Change the IP to your WAN IP. The IP that's the same as NewAuth and the one in MsSql Lin2db Server entry.

 

 

 

Re-encrypt the file with v212 or v211 setting. Copy it to your Client's /System/ Folder and override the L2.ini file there. When you start up your client. Make sure you are using the L2.exe from the /System/ Folder and not the Lineage2.exe in /Lineage 2/ Folder

 

 

 

-----------------------------------------------------------------------------------------------

 

Running the Server

 

-----------------------------------------------------------------------------------------------

 

 

Open the files in the following order.

 

 

 

L2LogD.exe

 

 

 

File DB = lin2log

 

login name = your SQL account

 

password = your SQL password

 

 

 

CacheD.exe

 

 

 

File DB = lin2world

 

login name = your SQL account

 

password = your SQL password

 

 

 

L2AuthD.exe

 

 

 

File DSN = lin2db

 

login name = your SQL account

 

password = your SQL password

 

 

 

PetitionD.exe

 

 

 

Server = (local)//or the name of the server for your MySQL Server Agent

 

login name = your SQL account

 

password = your SQL password

 

Database = petition

 

 

 

L2Server.exe

 

 

 

L2NPC.exe

 

 

 

Congrats with setting up your server!

 

 

 

If you want to free up some system resources. You can shutdown Petition Server once everything is fully loaded. Some people claim L2LogD Server is also not require to run. You can try shutting it down, but I don't recommend it, since CacheD, L2AuthD, L2Server, and L2NPC requires it when loading. L2Server.exe must be running on the same machine with L2NPC.exe! You cannot load them on seperate computers for some stupid reason!

 

 

-----------------------------------------------------------------------------------------------

 

Setting up Administration Account / GM Characters

 

-----------------------------------------------------------------------------------------------

 

For this to work you must have created an user account.

 

 

 

Open SQL Server Enterprise Manager (start menu again), double click SQL Server Group, double click on your local server then click OK. Double click on databases folder and select lin2db. Click on tables then find user_account, right click on it and select Open Table then Return All Rows. Note the name and uid of the account that you want to make a gm.

 

 

 

Go back to databases and this time select lin2world. Click tables and select builder_account, right click select Open table then Return All Rows. Under account name enter the name of your character (that you noted before in user_account) and under default builder enter 1 and under account_id enter the uid you noted from user_account.

 

When you make a new character on this account it will have GM powers, the commands are located in script/BuilderCmdAlias.txt and are used //command so to disable invisible mode you would type in: //hide off

 

 

 

To give a current character GM powers, Go back to databases and select lin2world. Click tables and select user_data, right click select Open table then Return All Rows. All the character on the server will be listed, you can just change the builder value from 0 to 9 for any character you want to give GM powers.

 

 

 

-----------------------------------------------------------------------------------------------

 

Editing the Server / Gameplay Properties

 

-----------------------------------------------------------------------------------------------

 

All the things you can edit are in the /scripts folder.

 

For EXP/SP/Adena rates and drops you can edit: npcdata.txt

 

For GM Commands you can edit: BuilderCmdAlias.txt

 

For Item stats you can edit: Itemdata.txt

 

For Blacksmith sell lists you can edit: multisell.txt

 

For NPC spawn locations you can edit: npcpos.txt

 

For Recipe information you can edit: recipe.txt

 

For Teleporters and store you can edit: ai.obj

 

 

 

Before you begin editting anything. A rule of thumb is ALWAYS BACK UP YOUR FILES.

 

 

 

 

 

--End Guide.

 

Kind Regards

 

Romeo

 

Posted

ai.obj cant be edited without program , anyway thanks for share it will be better if u can add some programs like buff time editor and scripts editor

Posted

Very Good Guide, Usefull and full explained!!!!!!!! GJ `Romeo.

 

Thanks ;)

 

ai.obj cant be edited without program , anyway thanks for share it will be better if u can add some programs like buff time editor and scripts editor

 

you are right ofcourse when i find some time i will re-update This Theard thanks for Idea ;D

Guest
This topic is now closed to further replies.


  • Posts

    • Продам комплекты (Custom Colour) Apella Сеты. Контакт со мной/Contact with me  Telegram. Custom Colour Apella Light YouTube Video
    • haha, I don't say it, chatgpt says it. discuss it with him if you have problems 😉 or sue chatgpt for lying, for example when he tells you that you are an idiot and tells you that I do things that are light years ahead of you.
    • hey i make enough to live comfortably you, on the other hand... doubt that'd be the case if you were as competent as you claim to be
    • all your doubts ask chatgpt, also ask what you could do yourself hahaha
    • This post originally appeared on MmoGah. Odin: Valhalla Rising is an ambitious open-world MMORPG developed with Unreal Engine 4, offering breathtaking visuals and immersive gameplay. I will share everything you need to know before starting it.     Re-rolling In Odin, re-rolling isn't a practical strategy. Unlike most gacha games, where it's common to reset for better initial pulls, Odin focuses heavily on long-term growth. The earlier you begin playing and developing your character, the more advantages you'll gain over time. Instead of spending your efforts on re-rolling for ideal equipment, it's better to dive in and start progressing right away.   Server Selection Before starting your character, selecting a server is a crucial step. Since Odin doesn't support cross-server gameplay, coordinating with your friends, family, or guildmates is essential to ensure everyone creates their characters on the same server. Take the time to plan with your group beforehand. After deciding on a server, your next major choice will be picking a class.   Class Breakdown Odin features four primary starting classes: Warrior, Sorceress, Rogue, and Priest. Each class comes with its own distinct playstyle and unique strengths, so choose wisely, as your selection is permanent. However, even free-to-play players can create up to three characters on one server, giving you the flexibility to try different options and find the one that matches your preferences.   Quest and Leveling Once your character is created, your initial objective is to work through the main questline. This acts as both a tutorial and a method for early leveling. Odin simplifies the process with a convenient quest button that handles navigation, starts dialogues, and even enables auto-combat. This user-friendly feature allows beginners to grasp the basics of the game without feeling overloaded.   Auto Combat and No Kill-steal Mode Auto combat is an essential feature in Odin, enabling your character to battle monsters autonomously. This system allows you to effortlessly gain experience and loot, even while you're busy studying, cooking, or unwinding. To optimize its use, activate the no-kill-steal mode. This setting prevents your character from targeting monsters already engaged by other players, helping you avoid conflicts or potential PvP situations. However, if a quest becomes difficult to complete due to overcrowded areas, you can temporarily disable this mode to overcome the obstacle and move forward.   Item Management and Potions Don't overlook the importance of consumable items, especially health potions. These can be purchased, along with buffs, from general merchants in villages, and they play a crucial role in improving your combat efficiency and ensuring your survival. Always aim to keep a full stock of HP potions and carry buffs that boost attack, defense, or regeneration in batches of 5-10 for convenience.   Once you've acquired your consumables, assign them to your quick slots located at the bottom center of the screen. Swiping down activates these slots, and items like potions will automatically be used when necessary, so you don't need to worry about them mid-battle. Keep a close eye on your potion reserves, as running out during a tough fight could leave you vulnerable before reaching a safe area. In the early stages of the game, it's better to return to town for a restock if supplies are low rather than risking unnecessary defeats. You can also enable notifications to alert you when your health or potion count drops too low—a handy feature for staying prepared if your attention is elsewhere.   Leveling and AFK Farming Once you've mastered the fundamentals, the next step is to focus on leveling up and enhancing your character. Gaining levels is your primary source of progression early on, as it not only improves your stats but also unlocks crucial game features and new abilities. At this stage, simply sticking to the main questline provides a reliable and efficient way to gain experience.   Additionally, Odin includes a highly convenient idle feature called AFK mode. This allows your character to keep farming for resources and experience even when the game is closed, with a maximum duration of 8 hours per day. It's an excellent option for making progress while you're asleep, commuting, or otherwise occupied.   Gear Upgrades When the time comes to improve your gear, the initial focus should be on upgrading from normal-grade equipment to high-grade items. These provide significantly better stats and can be enhanced further to increase their effectiveness. Enhancing requires enhancement stones and gold, but it's important to stay within the safe enhancement limit. Attempting upgrades beyond this limit carries the risk of destroying your gear if the enhancement fails. Stick to safe enhancements until you've gained more experience and accumulated spare equipment to mitigate potential losses.   Skill Purchases When you've accumulated enough gold, it's time to invest in skills. These are crucial for enhancing your combat abilities and provide key benefits tailored to your class, whether it's increasing damage output, improving healing capabilities, or adding valuable utility. Before purchasing, ensure your character meets the level prerequisites for each skill. Your ultimate goal will be progressing through and completing the main questline in Midgard as you continue to develop your character.   Unlocking Jotenheim Finishing this milestone grants you access to the next region, Jetunheim, unlocking a variety of new content and challenges. This marks your first significant achievement in the game and is an essential early objective to strive for as you progress.   Joining a Guild Joining a guild is a highly beneficial step in Odin. Guilds not only provide opportunities for social interaction and group activities but also offer passive bonuses that can significantly enhance your gameplay. Even if you're not particularly active socially, being part of any guild is advantageous. The guild feature becomes accessible after completing Chapter 4, Quest 19 of the main story.   Guilds provide various perks, including buffs that scale with the guild's level. Additionally, you can earn guild coins by contributing through donations, quest completions, or regular logins. These coins can be exchanged for valuable rewards, such as epic-grade armor. The more you actively contribute to your guild, the greater the overall benefits for both you and the guild itself. Joining early and staying involved will undoubtedly strengthen your progression in the game.   Conclusion Here is the end of this beginners' guide. I hope these tips will help you level fast in Odin.
  • Topics

×
×
  • Create New...