Vilmis

View File L2jOrion Server Files Updates (Changeset 31 | Revision 1108) All information about (Changeset #31 | Revision #1108): https://www.l2jorion.com/index.php?/topic/405-changeset-31-revision-1108/ DataPack commits / changes for this changeset: https://orionproject.assembla.com/spaces/OrionProject/subversion/commits/19 *** if you don't know how to use it or have any question - contact us. Let me know if you find any mistake. Thank you! Submitter Vilmis Submitted 09/04/24 Category Server Pack Updates  

BUGS / CORRECTIONS ADDED - 2 missing skills to enchantable skills : Mass Fear and Mass Gloom (Like L2OFF). FIXED - A few bugs inside bot engine. Also, decreased CPU usage and improved bots behavior. FIXED - Sell buffs bug/exploit. FIXED - A few critical security exploits. UPGRADES UPGRADED - Custom premium item. From now on you can add as much as you want of them with any time you want. UPGRADED - Random PvP Zone: ADDED - A new config for buffs leave / remove on die inside zone.. ADDED - Reward per kill. ADDONS ADDED - Item enchanting system by your settings and chosen currency at gm shop. ADDED - Premium players chat system. IMPROVED - Server core performance and stability (database connections, code clean up/corrections and fixes). Also, less CPU usage. ADDED - New bots dashboard v1.0 (new features coming soon). ADDED - New menus for player, bot and npc panels.

Hello, First of all, what you need to do it's to buy a legal version of server pack.

So far I got 2 ideas: 1. Classic-Interlude which would be same as Interlude but with new updated game client and all Orion's features. 2. Continue the work on H5 paid files.

People with illegal server pack are not welcome here. Also, only one thing what they can get here is BAN.

Sveiki, Taip, lietuviai. Jei turite daugiau klausimų - galite tiesiog parašyti privačiai.

That's the point - we don't have a free version. It's paid server pack.

Hello, Yes, it's possible, but once again - we can't help people who use an illegal version of our server pack files. I can to offer the ban only.

Maybe you did not know it, but „Classic“ has a few different versions like starting from 1.5 Zaken to 3.0 The Kamael. So, which one of them is this?

Hello, I have this an idea to start working with some kind of classic client, but I did not decide which version I should use for. Any suggest?

View File L2jOrion Server Files Updates (Changeset 30 | Revision 1087) All information about (Changeset #30 | Revision #1087): https://www.l2jorion.com/index.php?/topic/385-changeset-30-revision-1087-back-to-work/ DataPack commits (all SVN changes) for this changeset: PART 1 - https://orionproject.assembla.com/spaces/OrionProject/subversion/commits/15 PART 2 - https://orionproject.assembla.com/spaces/OrionProject/subversion/commits/16 PART 3 - https://orionproject.assembla.com/spaces/OrionProject/subversion/commits/17 *** if you don't know how to use it or have any question - contact us. Let me know if you find any mistake. Thank you! Submitter Vilmis Submitted 03/20/24 Category Server Pack Updates  

BUGS / CORRECTIONS CORRECTED - Movement on bow attack (Like L2OFF). CORRECTED - Quest: Fate Whisper (Like L2OFF). CORRECTED - Quest: Seekers Of The Holy Grail (Like L2OFF). CORRECTED - A few creatures spawn location (Like L2OFF). ADDED - Missing drop item for Dark Choir Captain (Like L2OFF). UPGRADES UPGRADED - Admin command: //reload. Added new reload features: class damages (for class balance), achievements, skins and faenor. UPGRADED - Castles sieges. Improved performance, decreased CPU usage and fixed a few more issues. UPGRADED - Geo engine stability and performance. UPGRADED - Spawn/Teleport protection. Fixed some important issues. UPGRADED - Dressme / Skins system: ADDED - Shield skins. ADDED - „Buy all“ action for each type of skin (package's settings is in xml file). ADDED - „Delete“ skin permanently. ADDED - 2 new configs: AllowBuyTryWithoutWeapon and AllowBuyTryWithoutShield. ADDED - Confirmation for Buy all and Delete. CHANGED - System removes skin if you try to change weapon <-> shield. UPGRADED - Command. menu. Also, added more settings like shots / spiritshots effect and pvp / pk announcements - on /off. ADDONS ADDED - New Rebirth System. (Big thanks to @Taduse He paid for this new feature and allowed to share with you, guys) OPTIMIZATION IMPROVED - Server core performance and stability (database connections, code clean up/corrections). OTHER UPDATED - Server pack LIBS folder jar files (several most important). UPDATED - MySQL connection. From now server works with MySQL 5.x - 8.x versions without any issue.

Hello, I just checked and it worked fine. Please double check your card data.

So, did you find out the real problem?

Frankly speaking Mysql should not make lag at all. Especially in that way like you explained. I never saw something like mysql lag in my entire life and I'm working with servers more than 10 years. Even by default settings mysql can hold pretty huge data bandwidth. I don't understand why you both decided like that. However, there can be many other reasons why this happens. Try do the tests to find out what's the real reason of lag. A few suggestions:: 1. Try default Orion server pack with same mysql and database. Just change ip and most important settings to make server running. Nothing else. 2. Try different system - clean, without custom items etc. 3. Re-install full Lineage 2 game client. Let me know what you found out.

He's just another random annoying, rude and disrespectful player which tries to get something for free telling it's a bug. Ok, topic closed.

First of all, are you sure 100% that lag makes mysql? What do you call a lag? What happens exactly, can you describe it?

Your 46Lv was too big for 40Lv chest.

Hello, I've checked that and I did not find anything wrong. People should not forget that if it's not 100% then there is a chance for no drop all the time and sometimes it can even be more times if you're unlucky. For example: I've changed rates to x3 and i killed boss „Cronos's Servitor Mumu„ several times. The drop was: 2-4 items which is really good I think. Also, I would recommend to check drop chance after server restart just in case if you used //reload command. Reloading server data during runtime is STRONGLY NOT RECOMMENDED for LIVE servers. It's just for developing environments. It might make temporary bugs or some kind of issues - till server restart.

Look, it's easy to add, but it needs core support. Add these 2 lines to bottom of actionname-e.dat: acionname-e.txt