dataminer
22-11-2008, 22:23
ORIGINALLY POSTED HERE: http://www.postpacific.com/showthread.php?t=9870
FROM: FYYRE
is straight forward and very simple... if its already widely known, then just ignore my post here... discovered this on my own messing around with the client,...thought i'd share:
Everyone is familiar with the l2encdec tool, used for making modifications to the .ini files, etc. When I modify my L2.ini & User.ini files I've always decrypted and re-encrypted them ... I admit this is the only reason I use l2encdec, is to change those two .INI files..
Ironically, Lineage allows us to do this without having to mess with l2encdec. All you need do is take your unencrypted files (L2.ini % User.ini - in my case) and give them a name ... I use myl2.ini and myuser.ini. Now the catch is, to avoid the "Files are corrupted!" dialog ... all of the other files in \system are still encrypted, with only our custom l2 and user .ini which are not.
So when we load Lineage 2, we pass an argument to the client (you can do this in any Unreal Engine based game...):
l2.exe -INI=myl2.ini -USERINI=myuser.ini
or if you want say a short-cut from desktop...:
"C:\Progra~1\Lineag~1\system\l2.exe" -INI="C:\Progra~1\Lineag~1\system\myl2.ini" -USERINI="C:\Progra~1\Lineag~1\system\myuser.ini"
And the game runs successfully using our custom .INI files instead of the default L2.ini and User.ini
Here's another tidbit regarding using non-encrypted .INI files... While in game we can make changes to the clients behavior and write them directly to our .INI files, saving the changes. When in game, assuming you also have the console visible you can use UT commands to modify the .INI files directly.. here's a few examples:
set ini:Engine.Engine.ViewportManager MinDesiredFramerate 60
set ini:Engine.Engine.LevelInfo PhysicsDetailLevel PDL_High
....etc
** Additional info: looking in the l2.ini there is a hint to enable logging.
Add -log to command line using l2.exe -log
Another command line argument from Ra1n0:
"C:\Progra~1\Lineag~1\system\l2.exe" -windowed
quick window mode =)
FROM: FYYRE
is straight forward and very simple... if its already widely known, then just ignore my post here... discovered this on my own messing around with the client,...thought i'd share:
Everyone is familiar with the l2encdec tool, used for making modifications to the .ini files, etc. When I modify my L2.ini & User.ini files I've always decrypted and re-encrypted them ... I admit this is the only reason I use l2encdec, is to change those two .INI files..
Ironically, Lineage allows us to do this without having to mess with l2encdec. All you need do is take your unencrypted files (L2.ini % User.ini - in my case) and give them a name ... I use myl2.ini and myuser.ini. Now the catch is, to avoid the "Files are corrupted!" dialog ... all of the other files in \system are still encrypted, with only our custom l2 and user .ini which are not.
So when we load Lineage 2, we pass an argument to the client (you can do this in any Unreal Engine based game...):
l2.exe -INI=myl2.ini -USERINI=myuser.ini
or if you want say a short-cut from desktop...:
"C:\Progra~1\Lineag~1\system\l2.exe" -INI="C:\Progra~1\Lineag~1\system\myl2.ini" -USERINI="C:\Progra~1\Lineag~1\system\myuser.ini"
And the game runs successfully using our custom .INI files instead of the default L2.ini and User.ini
Here's another tidbit regarding using non-encrypted .INI files... While in game we can make changes to the clients behavior and write them directly to our .INI files, saving the changes. When in game, assuming you also have the console visible you can use UT commands to modify the .INI files directly.. here's a few examples:
set ini:Engine.Engine.ViewportManager MinDesiredFramerate 60
set ini:Engine.Engine.LevelInfo PhysicsDetailLevel PDL_High
....etc
** Additional info: looking in the l2.ini there is a hint to enable logging.
Add -log to command line using l2.exe -log
Another command line argument from Ra1n0:
"C:\Progra~1\Lineag~1\system\l2.exe" -windowed
quick window mode =)