Jump to content

Recommended Posts

Posted

Vhalior evil noob don't hunt posts on my topic :D (that decreases my own post count).

 

Changeset 201

 

Doormen, misc

 

Doormen

- castle doormen are now retail-like (possibility to teleport in and out, drop of "open/close all doors" function).

- addition of 56 teleports location.

- unhardcode all CHDoormen HTMs.

- addition of many missing Doormen (Siegable CHs ones, 2 at Frontier Border) and fix some templates (Doormen of Hell were bugged as hell).

- drop of all useless HTMs.

 

Misc

- GmListTable is moved on datatable section.

- 2 spawns of Squashs have been dropped (in 4s...) Ty Vonak.

- TaskPriority is dropped (useless crap).

 

This commit doesn't fix yet CH doors issue.

Posted

I can't help but notice the IRC channel is empty :C

 

Also, I switched from the l2j nightlies to this svn, however I noticed when trying to manually edit sql data:

CREATE TABLE `spawnlist` (
  `npc_templateid` smallint(5) unsigned NOT NULL DEFAULT '0',
  `locx` mediumint(6) NOT NULL DEFAULT '0',
  `locy` mediumint(6) NOT NULL DEFAULT '0',
  `locz` mediumint(6) NOT NULL DEFAULT '0',
  `heading` mediumint(6) NOT NULL DEFAULT '0',
  `respawn_delay` mediumint(5) NOT NULL DEFAULT '0',
  `periodOfDay` tinyint(1) unsigned NOT NULL DEFAULT '0'
);

 

The spawnlist table has no key fields. Is this intentional or was it something that was over-looked:

7wTJz.jpg

 

Posted

IRC has been deserted since a long time (months ago). Basically it has never been populated, to be honest, lol. 3 max isn't a * real* success, but an honorable fail :P.

 

Spawnlist doesn't have primary key from basic. So far, I think it's a generic L2J mark (correct me if I'm wrong), from IL (and surely before) to current times. You have to add one column only for that if you really need.

Posted

IRC has been deserted since a long time (months ago). Basically it has never been populated, to be honest, lol. 3 max isn't a * real* success, but an honorable fail :P.

 

Spawnlist doesn't have primary key from basic. So far, I think it's a generic L2J mark (correct me if I'm wrong), from IL (and surely before) to current times. You have to add one column only for that if you really need.

 

I guess it's not actually needed, though I know it can really hurt the performance in some cases:

 

"1) Since you are not using an explicit primary key, the mysqld node will end up randomly connecting to whatever ndbd node it happens to choose, from which the transaction is re-routed to the right data nodes. This unnecessary adds (doubles!) network latency.

 

2) When inserting, fetching the unique autoincrement value acts like a global lock for all inserts. You can parallelize all you want, but it doesn't get any faster. (There is ndb_autoincrement_prefetch_sz to prefetch a number of keys in a batch, but still, always always use primary key.)"

 

Though since it's only a fetch during the load of the server, I guess it's not a big deal.

Posted

non?

or all, depends of PoV. Project is project, there isn't "stable" version. We move on, each commit corrects bugs. If you miss 10 revisions, you got between 20 and 40 bugs and/or less content for sure compared to latest version (average quests commited per commit is 3, you calculate).

 

Use latest revision each time. The only bug I introduced those days are CH doors. Previous bug was inventory refactor, 3 months ago and knownlist refactor, 5-6 months ago.

Posted

or all, depends of PoV. Project is project, there isn't "stable" version. We move on, each commit corrects bugs. If you miss 10 revisions, you got between 20 and 40 bugs and/or less content for sure compared to latest version (average quests commited per commit is 3, you calculate).

 

Use latest revision each time. The only bug I introduced those days are CH doors. Previous bug was inventory refactor, 3 months ago and knownlist refactor, 5-6 months ago.

Ok, thanks.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



  • Posts

    • It has been a while since I updated this thread. I am currently actively working on a full-scale port of the shader library to ensure the fast and accurate transfer of all effects. I have decompiled the original game and created a tool that fully logs the entire *Lineage 2 Interlude* particle system. This allows me to extract the original formulas hardcoded into the game, resulting in a high-fidelity port. For instance, *Lineage 2* uses an `appRnd` system that generates unique randomization patterns for different skills, giving them distinct visual characteristics; there are countless formulas and technical nuances like this. Ultimately, I will derive all the key formulas and replicate the geometry with high precision. Twelve basic geometry formulas have already been ported. The effect was created in 10 minutes using a .uc file, HLSL formulas, and SpriteEmitter particle blending formulas.   https://prnt.sc/_3UDLQVX_Y-_
    • Good luck my friend! 😃
    • try this one instead. The one he shared affects every single NPC/player character in the game, the one I posted only affects player characters  https://drive.google.com/file/d/1UtccbD9e50x3WEnQBab2PTZnBHwpcGYM/view?usp=sharing or perhaps i misunderstood; if you could please post a full explanation of the problem you're having with the files, unfortunately i think whatever you're using to translate to english is a bit bad nevermind, i got what you mean, here's the fix   https://drive.google.com/file/d/1av7OHaGSdnVQtcBgb9MhtiIkxVXy3P2y/view?usp=sharing   CanIngnoreCollision=True CanBeIngnoredCollision=True  
    • <dailyReward days="28" autoOpen="true" minimumOnlineTimeSeconds="30" oneRewardPerIP="true" resetIfMissDay="true">   For now, I have these settings in the XML—this is the V1 version I created, though I plan to make further improvements over time. Of course, I’ll also add more protections—MAC, HWID, and perhaps others like account-based restrictions—to make it more secure. We can also implement non-tradable items to further enhance the system's security. I’ll keep posting updates and refining both the system and the interface. I might make a video tomorrow; if you look at the top, you'll see the "auto-open" feature can be toggled on or off, allowing users to rely solely on the `.daily` command. Cheers! Note: If I sell it in this state, I’ll provide support and roll out updates to users. I’m not forcing anyone to buy anything; I’d even provide the patch files so that anyone with the necessary skills can add features, modify it, or improve it further.
  • Topics

×
×
  • Create New...

Important Information

This community uses essential cookies to function properly. Non-essential cookies and third-party services are used only with your consent. Read our Privacy Policy and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..