LessGRF
What?
LessGRF (LGRF) is an extension to the GRF format which adds a new algorithm for file compression. Normally the GRF will compress files using the DEFLATE algorithm which is the compression method typically used in ZIP files, but LessGRF adds the LZMA algorithm as an option.
Why?
Ragnarok's GRF files can get quite big. Back in the days the game data used to take up a few hundred megabytes, but today the GRF archives are about 2GB and contain tens of thousands of files. Since the data is starting to get pretty big it's possible to save quite a bit of space simply by re-compressing the game files with a more efficient algorithm. In my test on a full data.grf the file was reduced to about 60% of its former size. Maybe someone will find it useful if they want to make a mini client or something? Honestly, this was just a little experiment I did out of curiosity.
How?
Two simple steps are all that's necessary to use the LGRF format. First, download this file.
1. Installation
To upgrade your client, replace the cps.dll in your Ragnarok folder with the one from the download. (Make a backup of the old DLL file first.)
2. Recompression
Extract GRFCrush.exe somewhere. Run it from command line or just drag and drop your GRF file onto it. It will generate a new GRF file which you can use instead of the old one. The recompression process will likely take about 20 minutes on a moderately powerful computer.
Q&A
Q: Since the compression rate is better, will files load slower?
A: I've not notice any different in map load times. LZMA is more expensive to decompress, but modern processors are so fast the load time might just as well be reduced since less data has to be read from the hard disk.
Q: Can I use both GRF files and LGRF files at the same time?
A: Yes. The new cps.dll supports the old GRF compression as well. You can mix LGRF and GRF
Q: Can patchers or GRF tools update LGRF archives?
A: Very likely, but only if they don't attempt to decode the data in the process.
Q: Can current GRF tools extract files from LGRF archives?
A: No.
Q: ...Does that mean it can also be used for GRF protection?
A: I wouldn't recommend it. (That being said I guess this is no less "secure" than GRF protectors like SecureGRF.)
Q: Are there any penalties involved with using this format?
A: Incompatibility with GRF extractors is currently the only thing I've been able to think of. Let me know if you notice something else.
Hey guys!
In about 20 minutes (use this post's timestamp as a reference) i'll be taking the rAthena webserver offline for some quick maintenance updates. No data will be affected.
I'll edit this post once it's complete.
Thanks.
EDIT: Maintenance complete! (Time < 40s)
It's not rate, but probability.
example
<id>,Poring,20
<id>,Poporing,10
<id>,Drops,15
<id>,Marin,10
<id>,Angeling,1
It means,
Poring has chance 20/56.
Poporing has chance 10/56
Drops has chance 15/56
Marin has chance 10/56
Angeling has chane 1/56
If my reply answers your question, please mark as solved and gimme five.
About the annoying Chat Window:
Double check if your clientinfo.xml is inside your GRF folder. Also check if your client is reading the correct GRF. Supposed to be (yourservername.grf or whatever you name it.) You can edit it in your DATA.ini inside your RO folder.
[Data]
0=yourservername.grf
1=rdata.grf
2=data.grf
NOTE: Make sure you are using the LUB files and not the LUA files.
And the scr_logo Problem:
data/texture delete the scr_logo.bmp
Did you do these changes at renewal.h?
trunk\src\config\renewal.h
// Copyright (c) rAthena Dev Teams - Licensed under GNU GPL
// For more information, see LICENCE in the main folder
//#ifndef _CONFIG_RENEWAL_H_
//#define _CONFIG_RENEWAL_H_
//quick option to disable all renewal option, used by ./configure
//#define PRERE
//#ifndef PRERE
/**
* rAthena configuration file (http://rathena.org)
* For detailed guidance on these check http://rathena.org/wiki/SRC/config/
**/
/**
* @INFO: This file holds general-purpose renewal settings, for class-specific ones check /src/config/classes folder
**/
/// game renewal server mode
/// (disable by commenting the line)
///
/// leave this line to enable renewal specific support such as renewal formulas
//#define RENEWAL
/// renewal cast time
/// (disable by commenting the line)
///
/// leave this line to enable renewal casting time algorithms
/// cast time is decreased by DEX * 2 + INT while 20% of the cast time is not reduced by stats.
/// example:
/// on a skill whos cast time is 10s, only 8s may be reduced. the other 2s are part of a
/// "fixed cast time" which can only be reduced by specialist items and skills
//#define RENEWAL_CAST
/// renewal drop rate algorithms
/// (disable by commenting the line)
///
/// leave this line to enable renewal item drop rate algorithms
/// while enabled a special modified based on the difference between the player and monster level is applied
/// based on the http://irowiki.org/wiki/Drop_System#Level_Factor table
//#define RENEWAL_DROP
/// renewal exp rate algorithms
/// (disable by commenting the line)
///
/// leave this line to enable renewal item exp rate algorithms
/// while enabled a special modified based on the difference between the player and monster level is applied
//#define RENEWAL_EXP
/// renewal level modifier on damage
/// (disable by commenting the line)
///
// leave this line to enable renewal base level modifier on skill damage (selected skills only)
//#define RENEWAL_LVDMG
/// renewal ASPD [malufett]
/// (disable by commenting the line)
///
/// leave this line to enable renewal ASPD
/// - shield penalty is applied
/// - AGI has a greater factor in ASPD increase
/// - there is a change in how skills/items give ASPD
/// - some skill/item ASPD bonuses won't stack
//#define RENEWAL_ASPD
//#endif
//#endif // _CONFIG_RENEWAL_H_
http://youtu.be/CJmY5xsQ5Nk
Most of rules is same as normal WoE, different in
1. Only 2 guild can play this game, one is attacker, other is defender.
2. When attacker broken stone, attacker will be defender, defender will be attacker.
3. When stone was broken, defender will be send to save point.
4. Who can own the stone after time out, is winner.
5. Gamer can use NPC to back to their save point after died.
Setting :
Waiting time : 5 minutes
(after time out, game will be canceled)
Prepare time : 10 minutes
(after 5 minutes, defender will be send to stone place)
(when time out, attacker will be send to start point)
Game time : 1 hour
Download :
1 vs 1 WoE.txt
map.allowrA.patch