So i implemented this simple system on emu ,works but not properly ,and there is nothing wrong with implementation nor values becuz i have no problem with other adaptions like custom cb,java buffer from L2J etc...
case 4
case 7
case 10
case 15
but guess how it goes
it goes like omg... at 4 kills it goes to case 7 instead 4 ,at around 9 [yep 5 not 3] kills i think it goes to case 15 instead of 10 and from case 15 it goes to 25 instead of 20....
Anyone have idea of this cause?
This is the weirdest bug i ever found and i cant seem to fix it ,it doesnt giveme any info or warning ,error or whatever, its just goes like that ,retarded... ,there is nothing wrong with L2PcInstance or character ,all are implemented properly on pack
L2VikosMemory | User Manual
1. General Information
L2VikosMemory is a memory optimization tool for Lineage II.
It automatically clears the game cache, reducing RAM usage and improving stability.
2. Installation
Extract L2VikosMemory.dll and ogg.dll into the game folder (where l2.exe is located).
No additional steps are required.
3. Configuration
L2VikosMemory settings can be adjusted in the L2VikosMemory.cfg file:
CleanInterval=X – Cleanup interval (in minutes)
TryElevate=true/false – Enable/disable privilege escalation
AltClientGuard=true/false – Compatibility setting for STRIXGUARD
Example Configuration:
CleanInterval=3
TryElevate=false
AltClientGuard=false
4. Verification
The log file L2VikosMemory.log contains:
Connection status
Cleanup results
Freed memory
5. Troubleshooting
If L2VikosMemory is not working:
Check if the DLL files are in the correct folder.
Try running the game as an administrator.
Check the log file for errors.
6. Support
For support, contact Artem on Telegram.
7. Additional Information
Compatibility: Supports most Lineage II clients.
Recommended Interval: 3-5 minutes.
Gameplay Impact: No effect on gameplay performance.
Price: $150
Question
Karasu
So i implemented this simple system on emu ,works but not properly ,and there is nothing wrong with implementation nor values becuz i have no problem with other adaptions like custom cb,java buffer from L2J etc...
case 4
case 7
case 10
case 15
but guess how it goes
it goes like omg... at 4 kills it goes to case 7 instead 4 ,at around 9 [yep 5 not 3] kills i think it goes to case 15 instead of 10 and from case 15 it goes to 25 instead of 20....
Anyone have idea of this cause?
This is the weirdest bug i ever found and i cant seem to fix it ,it doesnt giveme any info or warning ,error or whatever, its just goes like that ,retarded... ,there is nothing wrong with L2PcInstance or character ,all are implemented properly on pack
10 answers to this question
Recommended Posts