Jump to content

Recommended Posts

Posted
1 minute ago, Kara said:

 

Alright you're right it was developed by multiple people @Zoey76 for me represent all these people who provided this "stable" pack for us to leech and make our "projects". 

 

Only those who spend days doing all these packet sniffing (especially in H5 that is a mess), should be credit on each file we make. 

 

You get what i mean. @Tryskellmostly did a clean up and partial rework not big engine re-work (at least so far), but still he should lock it and make it private. 

 

make private WHAT a downgraded L2J H5 ? if aCis wasn't freely accessible by the average user it would cease to exist long ago since there would not be reports / contributions but just Tryskell's work who would pretty sure give up if he was closed source and isolated

Posted (edited)
10 minutes ago, Kara said:

 

I said that You work on @Zoey76 source and it's a mess already cause its a combination of your work and their work. Since you feel like you did a heavy re-work why don't you lock aCis and make it via payment? Even amateur projects are locked nowadays such as L2JHellas. 

You should also protect your work since they don't respect you. 

 

 

Yes i know. For me the best "developer" i've ever seen it's by far @Zoey76 and even if we work 10 years we won't balance the work he did for us. All projects right now (in my opinion) exists because of him yet nobody credit their work. We are greed.

 

Actually, I think L2J is at this bad shape only because of Zoey76. And Zoey76 isn't the one who coded initial L2J, just for your concern. He got nothing to do with L2J IL (if he was simply here at this time).

 

There was a nice video made on L2JForum, back in time, with all contributors names - and I assure you than Zoey76 isn't the biggest one, in the concerned period of L2JIL, which is mine.

 

----

 

Locking a source don't avoid the leak, and it's not my point to lock things.

 

And as says xdem, even if I could simply make few servers and fix things by myself and wait reports from players, it's "easier" and more "friendly" to build a community around a project.

 

If you honor my words, you honor my work - that's all. If you don't feel like honoring my words, you got other, amateur or pro, L2J forks - simply use them.

Edited by Tryskell
Posted

And lets not forget - aCis ultimately killed L2JFrozen because it was FREELY available and cleaner, if aCis wasn't free or a concept at all, we would probably use L2JFrozen today and be happy about it !

Posted
9 minutes ago, xdem said:

 

Why should I be lying? I've always said your work is well respected but even with your huge contribution you are still a drip drop in the sea comparing to what all of us including players contributed to L2J - which you inherrited to create aCis ! This is a fact that you can't deny

 

 

 

I'm not sure how you calculate things, anyway, I can tell you than it's not a matter about how much was previously done - if everything done is wrong, then, everything has to be redone from zero.

 

I can give you few exemples, such as skill effect system. It's as old as L2J, and it's the wrongest thing ever, leading to numerous issues. It's not even yet fixed on latest. Spawnlist is another wrong system (should be territory based). Knownlist is another (was scaling so bad than it could easily consume 2g RAM of your server with 3500 NPCs seeing each other). I can name few dozen and dozen of wrong things, than I reworked or am actually in the process to rework with my community.

 

Most data (scripts, only to name those) has been or will be reparsed - that's a fact. It's not because it was existing before, or I reuse the existing structure, it makes my work "invisible".

 

My work is a part of a bigger work. I'm not sure if you know exactly how bad L2J IL is, but It's an old decayed house than I refactor since 10y.

 

And saying my (and my community) work equals 5% is, as I said, either ignorance or a lie.

Posted
7 minutes ago, xdem said:

And lets not forget - aCis ultimately killed L2JFrozen because it was FREELY available and cleaner, if aCis wasn't free or a concept at all, we would probably use L2JFrozen today and be happy about it !

 

Believe me, I doubt L2JFrozen would survive a lot - Shyla/Nefer were doing hotfixes. You don't make a pack out of hotfixes. They had no special vision about what needed to be done.

 

Remember than L2JFrozen isn't based on L2JIL, but on Scoria. Which means people already worked before them, and before them, it was probably some other russian dudes... Until L2J IL.

 

L2JFrozen is only "good" because of the Scoria part... If they would begin on the same level than me, believe me, that would be another story.

 

And if I can tell you that, it's because I was checking their timeline, during their whole lifetime, without ninja-ing anything useful.

 

As I did with L2JHellas - nothing special to import.

Posted
2 minutes ago, Tryskell said:

And saying my (and my community) work equals 5% is, as I said, either ignorance or a lie.

 

It doesn't matter if you reworked or coded something from scratch, I do appreciate and understand the need of it - Yet you have to realise that taking a car and tuning it or changing the tires doesn't make you a car manufracturer - You used a solid base, L2J that is and it does not come only with a java source but with a battle proven Database architecture and a retail like Datapack. Packet reverse engineering is also a big thing, I've already mentioned before these guys did the heavy lifting for us but you probably didn't notice or ignored. This is what matters most - not scrapping out working things and re-doing them. So I still personally believe that it tops 5-10%

Posted (edited)
26 minutes ago, xdem said:

 

You used a solid base, L2J that is and it does not come only with a java source but with a battle proven Database architecture and a retail like Datapack

 

Lol, you would figure out what I have to reparse, you would reformulate immediately... Spawnlist, zones, skills, items, npc templates have to be reparsed and got their own issue tab on my gitlab... Without counting what I already did since few years.

 

You got it all wrong, but that's np, you're a "car driver". From the moment wheels and engine are working, everything is good.

 

All in one, it changes nothing to the concept - my point isn't to insult (or "forget") old retired L2J developers, who did what they could. At that time, there was no special leader, there was no special code rules and conventions (that's the real, only thing than Zoey76 did - for the team management, imho, he just destroyed L2J, forcing the split of L2JUnity, not accepting forks help for YEARS, etc).

 

My point is to make my pack the most practical for ME and my COMMUNITY to MAINTAIN. I got few, basic, rules you are free to respect or not - which I believe improve aCis and will allow to maintain its legacy - and until now, it worked.

 

My point is to deliver a IL pack for everyone. If you still didn't get it, I can't help you.

 

I would want to make it private, I would simply make my own server, back in 2010, and only rely on players reports. I wouldn't care about javadoc, about methods rename, about splitting classes.

 

But I know aCis is far more than "that" - some people litteraly LEARNT coding, reading my code. Some people PMed me, saying than my project gave them the desire to go in developer classroom - or simply thanked me for the "player memories".

 

And if aCis is still used, it's only because it's coded in a serious way. There is a vision and there is a team leader, with defined goals. Which most of projects simply don't have.

 

PS : packets aren't a big deal, once you got opcodes, and structure. And that's decompilable.

Edited by Tryskell
Posted (edited)
8 minutes ago, Tryskell said:

 

Lol, you would figure out what I have to reparse, you would reformulate immediately... Spawnlist, zones, skills, items, npc templates have to be reparsed and got their own issue tab on my gitlab... Without counting what I already did since few years.

 

You got it all wrong, but that's np, you're a "car driver". From the moment wheels and engine are working, everything is good.

 

All in one, it changes nothing to the concept - my point isn't to insult (or "forget") old retired L2J developers, who did what they could. At that time, there was no special leader, there was no special code rules and conventions (that's the real, only thing than Zoey76 did - for the team management, imho, he just destroyed L2J, forcing the split of L2JUnity, not accepting forks help for YEARS, etc).

 

My point is to make my pack the most practical for ME and my COMMUNITY to MAINTAIN. I got few, basic, rules you are free to respect or not - which I believe improve aCis and will allow to maintain its legacy - and until now, it worked.

 

My point is to deliver a IL pack for everyone. If you still didn't get it, I can't help you.

 

I would want to make it private, I would simply make my own server, back in 2010, and only rely on players reports. I wouldn't care about javadoc, about methods rename, about splitting classes.

 

But I know aCis is far more than "that" - some people litteraly LEARNT coding, reading my code. Some people PMed me, saying than my project gave them the desire to go in developer classroom - or simply thanked me for the "player memories".

 

And if aCis is still used, it's only because it's coded in a serious way. There is a vision and there is a team leader, with defined goals. Which most of projects simply don't have.

 

I can't deny all these, im an aCis fanboi since 10 years, you know that. I even upgraded it to H5 because I couldn't let go when I wanted to move on to a different chronicle. Its fine work such an old pack - so I can understand the level of quality aCis delivers now.

 

I just really believe that acis-based custom projects that are for sell should be allowed given that the work they've put on to customize it justifies the money asked - even if its aCis based or not.

Edited by xdem
Posted
6 minutes ago, xdem said:

 

I can't deny all these, im an aCis fanboi since 10 years, you know that. I even upgraded it to H5 because I couldn't let go when I wanted to move on to a different chronicle. Its fine work such an old pack - so I can understand the level of quality aCis delivers now.

 

I just really believe that acis-based custom projects that are for sell should be allowed given that the work they've put on to customize it justifies the money asked - even if its aCis based or not.

 

Since sellers will never maintain the pack, I think that they shouldn't. Their sell is bound to aCis name, meaning if there is a backdoor, a shitty custom or an issue, they will come to me, not to the seller.

10 minutes ago, BruT said:

actually thats the reason all l2jservers exist, and no one can deny it.

 

 

That's the video I was referencing on my post :). Like if Zoey76 did all... :D

Posted (edited)

i've been in the l2jserver forums for a very long time and i never saw a single commit by Zoey76 until h5 when l2jserver was already dead.

 

kara I dont mean to offend you, but you are too young to argue about l2j which is 17 year old project 😐

 

L2jserver was created in middle of 2004 and  Zoey76 Joined: Tue Aug 11, 2009 3:36 am in the second forum of l2jserver

Edited by BruT
Posted

Guys don't get me wrong but mention Zoey76 i refer to the whole L2J team. I just appreciate the way he code more than other's so i mention his name often even tho lately he quit and focus on customization which is a shame for L2J. It's like they head to a custom project. 

 

@Tryskell XDEM is paying his respect to your work and pretty much any other person since you're the only active C6 Project, you don't have to raise your shield to him. I also agree that you can't ask other's to provide .diff for a project that is open source when they share or sell it. Pretty much when someone sell aCis project he is not selling the fixes, more like his custom, we all know who the owner of aCis is. 

Posted
2 minutes ago, BruT said:

i've been in l2jserver forums for a very long time and i never saw a single commit by him until h5 when l2jserver was already dead.

 

12 minutes ago, Kara said:

Guys don't get me wrong but mention Zoey76 i refer to the whole L2J team. I just appreciate the way he code more than other's so i mention his name often even tho lately he quit and focus on customization which is a shame for L2J. It's like they head to a custom project. 

 

@Tryskell XDEM is paying his respect to your work and pretty much any other person since you're the only active C6 Project, you don't have to raise your shield to him. I also agree that you can't ask other's to provide .diff for a project that is open source when they share or sell it. Pretty much when someone sell aCis project he is not selling the fixes, more like his custom, we all know who the owner of aCis is. 

 

Most of customs are already shared, and the pack is free. Meaning they sell "wind", since they won't even "maintain" their offers (aka, provide fixes for either their customs or the initial pack).

 

As I said to Trance, marketplace should stop to offer such spot for 2008 year behavior. Because yes, putting some dirty ninja-ed customs from some dark russian forums, adding your own HTMs (sometimes, not even yours) and putting it on any random base doesn't make it a "pack".

 

My point isn't an ego point, it is a project leader point - a point than you can't understand, since you don't manage a publically used pack and you're part of the "car users" (to take back the "car manufacturer" image of xDem).

 

The pack isn't 'fully' open source for specific reasons (and actually, the number of shares and aCis popularity gave me right about the made choice, back in 2010), the pack isn't able to sell for specific reasons (which I already explained - customers don't have any support from sellers, and will ultimately whine to me, my bug report section will be filled with either invalid or already fixed reports, there is no control over quality, there is no control over security, etc) - and once again, you can use any other fork or even basic L2JIL if you want to SELL your customs.

 

I work almost for free, since 10 years. The minimum is to, at least, respect the few rules I put - which are far to be extreme.

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

    • With EA Sports FC 27 officially announced, many players are hoping to get their hands on a coveted Closed Beta code. The FC 27 beta gives fans an early opportunity to test new gameplay features, modes, and updates before the game's full release. Ultimate Team is expected to be one of the most anticipated modes, giving players an early look at the in-game economy and how valuable FIFA 27 coins may be at launch. While there's no guaranteed way to receive a beta invitation, there are several steps you can take to maximize your chances. These methods have helped many players receive beta codes in previous years, and they're still the best options heading into FC 27.     1. Enable EA Email Communications The first and most important step is to make sure EA can actually contact you. Log in to your EA account and head to Communication Preferences. Here, you'll find options related to emails about products, events, and promotions. Make sure to: • Turn on promotional emails. • Set email frequency to "Any Time" instead of monthly updates. • Save your changes. EA typically sends Closed Beta invitations via email, so if these settings are disabled, you could miss your chance entirely.   2. Add FC Games to Your Favorite Titles Under your EA account preferences, you'll find a section for favorite games. Add any football-related EA titles you play, including: • EA Sports FC 26 • EA Sports FC 27 (if available) • EA Play • Other EA football games This helps EA understand your interests and may improve your chances of being selected for football-related tests.   3. Select Your Preferred Platforms Another useful step is updating your preferred gaming platforms. Choose all the systems you actively use, such as: • PlayStation 5 • Xbox Series X|S • PC • Nintendo Switch 2 There's no official confirmation that selecting more platforms increases your odds, but it doesn't hurt to ensure EA knows where you can participate in the beta. Just remember: if you don't own a particular console, there's little point in selecting it.   4. Verify Your Email Address Double-check that the email address associated with your EA account is verified. An unverified email could prevent important messages from reaching you, including beta invitations. It only takes a few seconds to confirm, and it's one of the easiest things to overlook.   5. Link Your Gaming Accounts Make sure your EA account is connected to the platforms you play on. Common account links include: • PlayStation Network • Xbox Network • Steam • Epic Games • Nintendo Account Having your accounts linked ensures your profile is fully set up and ready if you're selected for the FC 27 beta.   6. Consider Joining EA's Playtesting Program If you're interested in testing games beyond FC 27, consider signing up for EA's playtesting program. EA occasionally invites players to participate in early tests for upcoming titles. While joining doesn't guarantee you'll receive an FC 27 beta code, it can improve your chances of being considered for future playtests. Players selected for EA playtests are usually notified via email, so keeping your communication settings enabled remains essential.     Is There a Guaranteed Way to Get an FC 27 Beta Code? Unfortunately, no. EA selects participants based on a variety of factors, and luck still plays a significant role. Even players who have received beta codes in previous years aren't guaranteed to get one again. That said, following the steps above gives you the best possible chance: 1. Enable EA email communications. 2. Set email frequency to "Any Time." 3. Add FC titles to your favorite games. 4. Select your active gaming platforms. 5. Verify your email address. 6. Link your platform accounts. 7. Join EA's playtesting program.   When Does the EA Sports FC 27 Closed Beta Begin? If selected, players may receive their invitations around July 31, so keep an eye on your inbox and check your spam folder regularly. The Closed Beta is scheduled to kick off on August 5 and will remain available until August 25. This gives invited participants nearly three weeks to explore the game and provide feedback to EA. Compared to past beta tests, this is a relatively lengthy testing period, suggesting that EA is placing a strong emphasis on collecting player impressions and identifying potential issues ahead of the official release. Below are the launch and closing times for major regions around the world: Region / Time Zone EA FC 27 Closed Beta Start Date & Times EA FC 27 Closed Beta End Date & Times Pacific Time (PT) 10:00 AM—August 5 10:00 AM—August 25 Central Time (CT) 12:00 PM—August 5 12:00 PM—August 25 Eastern Time (ET) 1:00 PM—August 5 1:00 PM—August 25 Brasilia Time (BRT) 2:00 PM—August 5 2:00 PM—August 25 British Summer Time (BST) 6:00 PM—August 5 6:00 PM—August 25 Central European Summer Time (CEST) 7:00 PM—August 5 7:00 PM—August 25 China Standard Time (CST) 1:00 AM—August 6 1:00 AM—August 26 Korean Standard Time (KST) 2:00 AM—August 6 2:00 AM—August 26 Japan Standard Time (JST) 2:00 AM—August 6 2:00 AM—August 26 Australian Eastern Time (AET) 3:00 AM—August 6 3:00 AM—August 26 New Zealand Standard Time (NZST) 5:00 AM—August 6 5:00 AM—August 26   Which Modes Are Included in the Closed Beta? EA is using the FC 27 Closed Beta to evaluate several of the game's most important experiences before launch. Participants may gain access to popular modes such as Ultimate Team, Career Mode, and Clubs, as well as The Grounds, a brand-new addition making its debut in FC 27. Because multiple game modes are being tested simultaneously, the extended beta period gives players ample time to try different features and report their findings.   Final Thoughts Getting an EA Sports FC 27 Closed Beta code isn't guaranteed, but spending a few minutes optimizing your EA account settings can make a big difference. Every year, thousands of players receive invitations, and many of them simply have their accounts properly configured and ready to go. If you're lucky enough to get a code, you'll be among the first players to experience FC 27's new gameplay changes and features before launch. Until then, keep an eye on your inbox, stay patient, and good luck—you might be kicking off your FC 27 journey sooner than expected.
    • If you need in L2off i can hook you up! many people know me here and the work i offer. Live example https://l2exalta.org
    • Almost 16 years, you never know when a random Korean finds this topic and shares it.
    • Update: Version 3.1.2: * Improved compaction: deleting even a few textures now always reduces the file (previously small deletions could still slightly grow some packages, such as fonts); Version 3.1.1: * Deleting textures now actually shrinks the package: on save it is automatically compacted, reclaiming the space of the deleted textures (format and encryption preserved); Version 3.1.0: * La2Tools now checks for updates on startup and lets you know when a newer version is available on the site; Version 3.0.9: * Fixed textures that appeared blank in some clients (their object carries an embedded shader the reader mis-parsed) — they now decode and display correctly; * ShaderCode is now editable: Texture Properties → Material → ShaderCode shows the texture's real HLSL shader (was a fixed placeholder before); edit it and Apply — works across client formats (Interlude-era through Essence 542); Version 3.0.8: * BMP now imports as a native format, like UnrealEd: 8-bit BMP becomes a P8 (paletted) texture with a real Engine.Palette, 24/32-bit becomes RGBA8, 16-bit becomes G16; * Compress to P8 — adaptive 256-color palette (median-cut quantization); P8 is also selectable as an import "Convert to" target; * Copy / Cut / Paste now works for P8 (paletted) textures; * Non-power-of-two textures are highlighted in red (tiles and table) with a tooltip; new "Fix texture size" menu item pads them to a power of two while keeping the displayed size; * Reads "broken" packages that were tampered to block editors (corrupted size fields) — the client still loads them and now so does La2Tools; * "Repair package" — shown only for a tampered package (its tab is marked red) and restores the corrupted size fields; * Added client license 30 support (reads and imports its textures); * Import dialog now auto-resizes to fit its content; Version 3.0.7: * Import: the file name is now parsed smartly — package.group.name automatically fills the Group and Name fields (the package prefix is ignored); * Import: live name validation with an inline hint and tooltip — OK is blocked until the name is valid (allows - + ' etc., forbids only characters illegal in file names); * Import: textures whose size is not a power of two are now auto-padded for ALL formats (DDS/TGA/BMP too, not only PNG/JPG/GIF) — padded to a power of two with UClamp/VClamp preserving the original display size; * Texture filter now has a clear (×) button; * Light theme: visible Chrome-style tab outlines; Version 3.0.6: * "Save as..." — toolbar button and tab-menu item: save a package under a new name to any folder, choosing the format (Old/New) and Lineage2Ver121 encryption; the tab switches to the saved file; * Tab right-click menu reworked: Save, Save as... and Settings on top; Copy path and Open in Explorer at the bottom; Version 3.0.5: * Animation grouping now follows AnimNext links instead of frame names — chains group correctly with any naming (mixed prefixes, non-sequential or 0-/1-based numbers); * GIF import: animation parameters (frame rate) and TotalFrameNum are now written only to the first frame, the rest keep just the AnimNext link — matches the game's own format; same fix applied to "Create animation"; Version 3.0.4: * Clipboard <-> Explorer: Ctrl+C in the browser then Ctrl+V in Explorer pastes the textures as files; copy files in Explorer then Ctrl+V in the browser imports them; * Rename a package right from Package settings (handles Lineage2Ver121 re-keying); * Hotkeys: F1 (About), F2 (rename), F5 (reload from disk, asks if unsaved), Delete, Enter (Properties), Ctrl+W (close tab); * The application icon now appears in the title bar of every dialog and sub-window; * Fixed flipped preview when importing TGA files;  Download (Installer) |  Download (Portable)
    • Hello! I am creating a new L2 Editor version with most bugs fixed and new features added. PM me for more info!
  • 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..