Jump to content

Recommended Posts

  • 1 month later...
Posted

Hello everyone, I will be afk up to 1st January ! I will celebrate the new year with my girlfriend, eating some "boeuf bourguignon" ! 🥩🍷

 

For all people who stay alone during the holidays (and others ), I wish you great health and success in what you undertake, being love or business !

 

Regarding aCis initial fee

 

Initial fee of the project will rise from 100€ to 200€ at 1st January. The monthly fee of 10€/month isn't affected. This rise is due to multiple factors :

  • aCis is the only L2J pack to get retail AI system ;
  • I want to restrict people to access aCis using money, and emphasize contribution over money ;
  • Found and banned leakers will be punished harder if they do so ;

Just to be perfectly transparent, another rise is already planned when skills refactor will be ended, rising the price to 300€ (which is still less than L2OFF, but will be as complete but more editable). Requested amount of cookies to become part of Inner Circle will be kept at 100 in all cases, to promote reporting, coding and sharing.

 

Main goals of 2024

 

Main development axes are already know for 2024 ; skills and zones will be the main targets for this year. Reported bugs will be fixed occasionally, as always.

 

If we got time, a side quest could be another Movement refactor - which would benefit from Vector approach - and LoS - which I find lacking. Some Bounty Hunt will be eventually deployed for those particular cases.

Posted (edited)

As previously said, I'm editing all associated texts through the different medias regarding initial fee, which is now set at 200€. Access through contribution is still reachable for 100 cookies 🍪. Monthly fee is untouched.

 

For reminder, 🍪 can be obtained from bounties - which are paid tasks - or as reward for any committed contribution. Valid reports are also rewarded with 🍪, they are rewarded in same time than the bugfix.

Edited by Tryskell
  • 4 weeks later...
Posted

Changeset 408 (3205)

TradeList refactor, Duel refactor, Handlers management, SpawnManager, Sieges, AdminCommands, Bugfixes, Organization

 

TradeList refactor

  • Use AtomicBoolean instead of synchronized.
  • Rework entirely buy/sell methods, which are now far more safer (notably TradeList#privateStoreSell, which was checking and processing transferItem in same time). A fail upon item transfer notably corrects total transaction price.
  • Few checks (being pointless or doubled) or even entire loops (calling removeItem instead of remove...) are dropped/avoided in few places.
  • Fix few issues :
    • BuyList is now properly refreshed upon inventory edition. Ty bios for report.
    • The strange adena issue is fixed (was due to removeItem not processing -1 as a special value but regular value, which was actually --1 -> +1). Ty bios for report.
    • Items aren't shown anymore as possible sellable item, if that item is already part of the SellList or is equipped.

        
Duel refactor

  • Big cleanup, deleting 1/3 of the class.
  • Abnormal effects are now properly cleansed. Ty MoodFreak for report, Diablo for the initial fix.
  • Play the lose animation only if WIN or SURRENDER, no TIE.
  • Don't play anymore the winner animation.
  • Don't countdown 5/4 upon 1vs1 Duels (5sec timer, starts at 3).
  • Restore Players conditions after SystemMessages.
  • Upon teleport, cancel active enchant and trades for Players, no matter the situation. Indirectly fixes "cancel trade upon party duel teleport".

 

Handlers management - by LaRoja

  • Handlers are now dynamically loaded based on their appearance in package. You don't have to manually set them anymore.

 

SpawnManager

  • Fix 3 invalid bosses dbSave. Ty Denzel for report, Bandnentans for fix.
  • Manually fix few territories (invalid nodes, bad Z, zone over Fortresses...).
  • Delete the whole magic behind setting a returning point from an offset of spawn location ; it's anyway mostly blocked by first returnHome check.
  • Banned territories are considered way before in the random location calculation of territories, which avoid to trigger Z/geo fail for nothing.
  • SiegeGuard#returnHome now also have a geopathfail logic.
  • Max iterations of random location search is reduced from 20 to 10 to trigger issues faster (will probably set back to 20 or even 50 when most territories are fixed).
  • Delete the whole for loop from MultiSpawn#getSpawnLocation for "anywhere" type, since Territory#getRandomLocation generate at least one point (last wrong iterated point).

    
Sieges

  • Control Towers, guards and mercenaries are anew Residence bound (was buggy since Residence rework) ;
  • Control Towers are now implemented as retail ;
  • Siege Guards won't attack you anymore if you're DEFENDER (produced by few scripts, mostly spells related).
  • Fix SiegeFlag NPE. Each NPC must have a Spawn.

    
AdminCommands

  • Revamp //tele panels.
  • Introduce //find item [name]. Ty melron for initial idea, StinkyMadness/CUCU23 for improvements.
  • Introduce //find npc [name], delete 6 related admincommands :
    • admin_show_spawns
    • admin_spawn_index
    • admin_spawn_reload
    • admin_npc_index
    • admin_spawn_once
    • admin_show_npcs

    
Bugfixes

  • Lotto and race tickets are generated differently, and now are bound to an objectId. Ty bios for report.
  • Fix petdata speeds, prior to converted classes to records commit. Ty Denzel for report and fix.
  • Fix ghost Pet over unsummon. Ty Denzel for report, LaRoja for fix.
  • Fix Q220 Radar misplacement. Ty FDX for fix.
  • Fix Q025 Triol's Pawn behavior.
  • AI related - Ty Bandnentans for fixes.
    • Fix ClassCastException from a regular AI script. Ty Denzel for report.
    • Fix SaintNinja script.
    • Fix QueenAnt, Orfen minions and Core scripts.
    • Fix LV3Orc script.
    • Fix GludioHold/GludioStand NPEs.
  • Don't send Npc SocialAction if in a blocking statut (dead, stunned, etc). Ty artemis for report.
  • Fix potential NPE over Siege#isOnOppositeSide.
  • Little GeoEngine#findPath fix (if originZ is too different from calculated Z) - Ty Bandnentans for the fix.
  • Update skills shortcuts upon AutoLearn config on. Ty hqsly for report, Rufo for fix.
  • Don't send inventory update over items which aren't in inventory. Ty FDX for report.
  • Fix NPE over teleportTo (regarding scripts Guards), introducing _isTeleporting as an AtomicBoolean. Ty Bandnentans for fix.
  • Potential IOOBE fix for boat movement. Ty Bandnentans for fix.
  • Fix 2 potential NPEs (if Config.SPAWN_EVENTS is null).

    
Organization

  • Triangle3D class is dropped.
  • Add Player#isOverweight method.
  • Add few records.
  • Rework ITEM_LOGS config
    • Indirectly fix an issue with pet inventory invalid item count. Ty Denzel for report, LaRoja for fix.
    • Avoid to spread useless parameters and generate Strings for nothing.
    • Shortcut most Item related methods by 1 up to 4 parameters.
    • Herbs ItemInstance objects are properly deleted when using addItem(int, int, boolean).
  • Addition of Residence#getTownName
  • MinionSpawn passively delete minion from master list if no respawn is associated to it.
  • Cleanup TerritoryStatus bypass, avoid a NPE if castle owner Clan doesn't exist.
  • Add Quest#createOnePrivateEx method with SpawnLocation parameter.
  • Delete NpcAI#setBackToPeace parameter (unused).
  • Delete GrandBossManager class (unused). Ty LaRoja for report.
  • Delete _isReturningToSpawnPoint variable (unused).
  • Thanks 1
  • Upvote 1
  • 2 weeks later...
Posted (edited)

I created an account on the ip test acis server (161.97.185.208) to test, I don't know if it's up to date but there are still movement bugs in the water, was this fixed in the 408? Because this is fundamental and basic, for the price you suggest at acis with a bug like that it doesn't make sense because at acis 401 public it's the same bug.

 

Link Serve test: aCis PTS "Blackbird" is on ! (i-live.eu)

 

Bug Zone Water: 

https://i.imgur.com/Z2mk23e.mp4 
 

Bug Moviment:
https://i.imgur.com/vKFGNVl.mp4

 

Bug collision Height:

GhqcdXV.png 

 

Bug Target Party : 
https://i.imgur.com/SaiWHVw.mp4 

 

Fix Bug Target Party  aCis public ( 401) :
https://i.imgur.com/yFNOiAk.mp4

Edited by Williams
  • Upvote 1
  • 6 months later...
Posted (edited)

Hellllllo everyone ! Good news for some, bad news for others : aCis was, once again, leaked.

 

It wouldn't be that problematic if it was old content, or even last revision 408 ; but this time, the whole content of under development/master branches was leaked out. One pack project is actually reselling NEXT revision content - before even being announced on aCis forums.

 

The mole/leaker is still part of customers, and is still capable to leak data, at the date I speak about.

 

Since I'm on a joyful mood, following events will occur :

 

PIRATE PLANK MINIGAME

 

Since we got restricted amount of donators (we're actually 13 on sources counting developers, over all), it's not extremely hard to actually delete the mole ; few ppl are actually matching the description, and a list can be easily generated based on time leak, potential country, contributions,...

 

Which basically end with that representation :

 

spacer.png

 

How will it work ? Everytime a new leak will occur, the following donator on the board will jump out of ship (and Talking Island waters are kinda cold). Since I'm not a monster and got principles, I will send back spent money for the non-granted months to the kicked dude. You won't be added back to the sources, anytime. The game ends when the mole is dropped out, or when I'm alone with my most loyal peeps around.

 

CONTRIBUTION

 

Leftover donators will have to contribute to the pack, being reports or code edits. Silent people won't be renewed anymore solely based on money.

 

In the same order of idea, I will now request a minimum of 100 cookies contribution before accepting any new ppl on the gitlab - which anyway won't be hard to do if you're a minimum invested into the pack.

 

If you understood the concept, free ppl can access gitlab sharing for 200 cookies contribution (100+100), and donators can access with 100 cookies + 200€. Regarding monthly contribution, there are no special numbers to achieve, stay active and you will stay.

 

PUBLIC REVISION WILL STEP UP

 

Next rev 409 will be exceptionally released as public revision. This revision got unique reworks, notably AI (L2OFF GF 1:1) and pathfind systems (up to 100 times faster, see #for-your-eyes-only over aCis discord for screens proofs).

 

This revision got a lot of new content, and is far ahead of any other L2J pack in terms of AI fidelity with L2OFF - even the costier.

 

ENDING WORD

 

Thanks to all loyal people who have, will or currently support this pack - one of the very few to offer unique reworks.

 

L2J community, as a whole, unfortunately never stepped up or shined by its cleverness or integrity - and is more preocuppied to add poorly written customs over quality leaked sources.

 

The olympic medal goes to the poop-eater project owner applying straight leak, not even knowing what exactly is the changeset content (because yes, he doesn't know)... It's actually sad real people follow and pay for your work, but well, good job surfing on my own merits, I guess. Maybe one day you will go out of my shadows, and make your own path. That's the best I can wish you.

 

So, my thanks to the few beacons of light in this mere pool of shadows. That's essentially for you (and for my own pleasure, ofc) I continue to work on this hobbyist project - started almost 14 years ago.

 

-----------------------------------------------------

 

Changeset 409 (3301)

 

SCH, Castles, IU, Npc movement, Drop rate rework, Bugfixes, Organization

 

SCH - Ty Bandnentans for the good work

  • All SCHs are normally fixed and working.
  • CH decorations are reworked (they got their own XML, related Configs are dropped).
  • Aden CHs got the Wyvern option, as stated in Patch Notes. Ty Denzel for report.
  • CH features levels are corrected. Ty Denzel for report.
  • Fix NPC clan crest issue.

Castles

  • Keep Castle next tax percent instead of resetting it to 0.
  • Implementation of missing variables over Castle vault management. Ty KejbL for report.
  • Remove doublons over Residence npcIds. Add npcId 35552 HTMs. Ty //Dev for report.
  • Fix the tax income calculation.

IU

  • Add PAPERDOLL as potential location for IU (fix gm enchant, arrows consumption). Ty Roko91 for report.
  • Fix weight calculation over login. Ty KejbL for report.
  • Fix inventory update upon teleport (BSOE consumption). Ty //Dev for report, La Roja for fix.
  • Fix inventory weight upon NPC buy.

Npc movement

  • MOVE_TO desire is cleansed over onEvtBlocked, avoiding to build infinite desire.
  • Don't add MOVE_TO desire if given Location isn't reachable.
  • FLEE doesn't call event upon onEvtBlocked (that event means something wrong happened, it's then impossible to trigger "regular" FLEE checks).
  • Use Location#equals in few scripts.
  • NpcAI#thinkFollow cleanup (-8 arrays, -24 List#get, -8 distance2D).

Drop rate rework

  • Main idea is to iterate each category X times, as if X monsters were killed. No % re-calculation or whatever, it's plain and simple. x50 means you got the calculated drops of 50 monsters.
  • Avoid to generate IntIntHolder, manage the drop/spoil using a Map<Integer, Integer> instead, which also allow to merge similar itemIds.
  • Categories % are tested no matter if drop or spoil, which allow levelMultiplier to be properly applied.
  • Monster#dropItem is moved to Npc#dropItem, which allow any Npc to drop an item and avoid cast.
  • "killer" is now part of all Npc#dropItem, meaning the item is properly item protected.

Bugfixes

  • Fix a ClassCastException over Quest#onClanAttacked.
  • Fix a NegativeSizeArrayException upon client logging. Drop few logging errors related to invalid client attempts.
  • Fix NPE over Q635.
  • Fix PDAM calculation prior to rev 399 physical attack/skill split. Ty Yoska for report.
  • Fix TradeList automatic title cleanup. Ty Denzel for report/fix.
  • Add back missing Config.PARTY_XP_CUTOFF_METHOD "none" option. Ty CUCU23 for report/fix.
  • Fix "upper roof" NPCs. Ty Bandnentans for fix.
  • Fix Seven Signs individual stone contribution method. Ty //Dev for report.
  • Fix Q372 reward table and drop rate. Ty //Dev for report.
  • Q348 now distributes drops as party-random, despite the client info. Ty Denzel for report.
  • Fix Benom teleports out. Hardcode other in/out Locations. Ty //Dev for report.
  • Don't show Crystallize icon on inventory for Bounty Hunters (was an addition of CT1 GP1). Ty Bandnentans for report.
  • Replace "weightPenalty" for "weightLimit" over skills XMLs. Ty //Dev for report/fix.
  • When Heroes participate in a raid against Antharas, Valakas, and Baium, the boss monster has a chance to shout out the Hero characters’ names. Ty deekay for fix.
  • Fix isRaidBoss implementation (a raidboss minion without master was considered raidboss).
  • Fix Nurse Ants not healing the Queen Ant larva.
  • Fix a SQLException over Olympiad server startup.
  • Fix a SQLException over Clan member removal (since clan privs rework).
  • Fix default 30169 npcId HTM. Ty Bandnentans for report.
  • Fix Festival Guide missing rift option. Ty Denzel for report/semi-fix.
  • Few dwarven/general manufacture fixes
    • Add the missing max recipe integrity check.
    • Upon shop fail, call back the manage window.
    • Upon shop fail, don't cleanup the manufacture list.
    • Upon shop success, cleanup the reverse manufacture list (successful general shop resets dwarven, successful dwarven shop resets general).

Organization

  • Rework HtmCache and CrestCache to use NIO. Move CrestType to enums.
  • Implementation of WorldObject#forEachKnownType / WorldRegion#forEachType & forEachRegion - Avoid List overhead in numerous popular locations (notably broadcastPacket or region checks - which are done on every knownlist check).
  • Rework SkillList packet, it is now handled as other packets. Delete Player#sendSkillList method.
  • Delete DeadlockDetector class and related configs.
  • Add GameServer#isServerCrash, based on LaRoja implementation - without uses, for now.
  • Move IPv4Filter class to commons.network, delete net.sf.l2j.util package.
  • Add DefaultSeeRange config, use the retail value 450 instead of 400.
  • Add more records, ty LaRoja for the merge request.
  • Delete unused dimensionalRift.xml.
  • Few ItemContainer optimizations.
  • Rename all ocurrences of adenas to Adena.
  • SonarLint / UCDetector fixes :
    • Drop MathUtil#limit, use Math#clamp instead (introduced in JDK21).
    • Drop following unused Configs : FS_TIME_ENTRY, FS_TIME_END, RAID_MINION_RESPAWN_TIMER.
    • Few public / protected / private edits. A lot more to come.
    • switch cases are merged (introduced in JDK12).
    • Boolean object is compared to Boolean.FALSE/TRUE, not directly tested as a boolean.
    • String#replaceAll is replaced with String#replace when a regex pattern isn't involved.
    • Generate few records : Sequence, TutorialEvent.
    • Few class-based variables are now local.
    • Use HashMap.newHashMap instead of new HashMap when the capacity is known (static final maps). HashMap.newHashMap avoids to set 0.75 capacity when it's not needed.
    • LogRecord record is renamed LogRecord logRecord, due to record being now a keyword.
    • Use proper Singleton pattern for instance type (notably listeners).
    • Generate private constructors calling IllegalStateException for utility classes.
Edited by Tryskell
  • Like 3
  • Sad 1
  • Upvote 1
Posted
On 9/7/2024 at 8:23 AM, Tryskell said:

Olá a todos! Boas notícias para alguns, más notícias para outros: o aCis foi, mais uma vez, vazado.

 

Não seria tão problemático se fosse um conteúdo antigo, ou mesmo a última revisão 408; Mas desta vez, todo o conteúdo das ramificações em desenvolvimento/master vazou. O projeto de um pacote está realmente revendendo o conteúdo da revisão NEXT - antes mesmo de ser anunciado nos fóruns do aCis.

 

A toupeira/vazador ainda faz parte dos clientes e ainda é capaz de vazar dados, na data de que falo.

 

Como estou de bom humor, ocorrerão os seguintes eventos:

 

MINIJOGO DE PRANCHA PIRATA

 

Como temos uma quantidade restrita de doadores (na verdade, somos 13 em fontes contando desenvolvedores, no geral), não é extremamente difícil realmente excluir a toupeira; poucas pessoas estão realmente correspondendo à descrição, e uma lista pode ser facilmente gerada com base no vazamento de tempo, país em potencial, contribuições,...

 

Que basicamente terminam com essa representação:

 

spacer.png

 

Como vai funcionar? Toda vez que ocorrer um novo vazamento, o seguinte doador no tabuleiro pulará do navio (e as águas da Ilha Falante estão meio frias). Como não sou um monstro e tenho princípios, enviarei de volta o dinheiro gasto pelos meses não concedidos para o cara chutado. Você não será adicionado de volta às fontes, a qualquer momento. O jogo termina quando a toupeira é descartada, ou quando estou sozinho com meus amigos mais leais por perto.

 

CONTRIBUIÇÃO

 

Os doadores restantes terão que contribuir para o pacote, sejam relatórios ou edições de código. Pessoas silenciosas não serão mais renovadas apenas com base no dinheiro.

 

Na mesma ordem de ideia, agora solicitarei uma contribuição mínima de 100 cookies antes de aceitar qualquer nova pessoa no gitlab - o que de qualquer maneira não será difícil de fazer se você tiver um mínimo de investimento no pacote.

 

Se compreendeu o conceito, as pessoas gratuitas podem aceder à partilha do gitlab por 200 cookies de contribuição (100+100), e os doadores podem aceder com 100 cookies + 200€. Em relação à contribuição mensal, não há números especiais para alcançar, mantenha-se ativo e você ficará.

 

A REVISÃO PÚBLICA SERÁ INTENSIFICADA

 

A próxima revisão 409 será excepcionalmente lançada como revisão pública. Esta revisão recebeu retrabalhos exclusivos, notadamente sistemas AI (L2OFF GF 1:1) e pathfind (até 100 vezes mais rápido, consulte #for-your-eyes-only no discord aCis para provas de telas).

 

Esta revisão recebeu muito conteúdo novo e está muito à frente de qualquer outro pacote L2J em termos de fidelidade de IA com L2OFF - ainda mais caro.

 

PALAVRA FINAL

 

Obrigado a todas as pessoas leais que apoiaram, apoiarão ou atualmente apóiam este pacote - um dos poucos a oferecer retrabalhos exclusivos.

 

A comunidade L2J, como um todo, infelizmente nunca se destacou ou brilhou por sua inteligência ou integridade - e está mais preocupada em adicionar costumes mal escritos do que fontes vazadas de qualidade.

 

A medalha olímpica vai para o dono do projeto comedor de cocô aplicando vazamento direto, nem mesmo sabendo exatamente qual é o conteúdo do conjunto de alterações (porque sim, ele não sabe) ... Na verdade, é triste que pessoas reais sigam e paguem pelo seu trabalho, mas bem, bom trabalho surfando por meus próprios méritos, eu acho. Talvez um dia você saia das minhas sombras e faça seu próprio caminho. Isso é o melhor que posso desejar a você.

 

Então, meus agradecimentos aos poucos faróis de luz nesta mera piscina de sombras. Isso é essencialmente para você (e para meu próprio prazer, claro) eu continuo a trabalhar neste projeto amador - iniciado há quase 14 anos.

 

-----------------------------------------------------

 

Conjunto de alterações 409 (3301)

 

SCH, Castelos, IU, Movimento Npc, Retrabalho de taxa de queda, Correções de bugs, Organização

 

SCH - Ty Bandnentans pelo bom trabalho

  • Todos os SCH são normalmente fixos e estão a funcionar.
  • As decorações CH são retrabalhadas (elas têm seu próprio XML, as configurações relacionadas são descartadas).
  • Os CHs de Aden têm a opção Wyvern, conforme declarado nas Notas do Patch. Ty Denzel pelo relatório.
  • Os níveis de recursos CH são corrigidos. Ty Denzel pelo relatório.
  • Corrija o problema do brasão do clã NPC.

Castelos

  • Mantenha o próximo percentual de imposto do Castelo em vez de redefini-lo para 0.
  • Implementação de variáveis ausentes no gerenciamento de cofres do Castle. Ty KejbL pelo relatório.
  • Remova os dobrões sobre os npcIds de residência. Adicione npcId 35552 HTMs. Ty //Dev para relatório.
  • Corrija o cálculo da receita fiscal.

UI

  • Adicione PAPERDOLL como local potencial para IU (corrigir encantamento de gm, consumo de setas). Ty Roko91 pelo relatório.
  • Corrija o cálculo de peso no login. Ty KejbL pelo relatório.
  • Correção da atualização do inventário ao se teletransportar (consumo de BSOE). Ty // Dev para relatório, La Roja para correção.
  • Corrija o peso do inventário na compra do NPC.

Movimento Npc

  • MOVE_TO desejo é purificado sobre onEvtBlocked, evitando construir um desejo infinito.
  • Não adicione MOVE_TO desejo se determinado local não estiver acessível.
  • FLEE não chama event upon onEvtBlocked (esse evento significa que algo errado aconteceu, então é impossível acionar verificações FLEE "regulares").
  • Use Location#equals em alguns scripts.
  • NpcAI#thinkFollow limpeza (-8 arrays, -24 List#get, -8 distance2D).

Retrabalho na taxa de queda

  • A ideia principal é iterar cada categoria X vezes, como se X monstros fossem mortos. Sem recálculo de % ou qualquer outra coisa, é puro e simples. x50 significa que você obteve os drops calculados de 50 monstros.
  • Evite gerar IntIntHolder, gerencie o drop/spoil usando um Map<Integer, Integer> em vez disso, que também permite mesclar itemIds semelhantes.
  • As categorias % são testadas, independentemente de cair ou estragar, o que permite que levelMultiplier seja aplicado corretamente.
  • Monster#dropItem é movido para Npc#dropItem, o que permite que qualquer Npc solte um item e evite o lançamento.
  • "killer" agora faz parte de todos os Npc#dropItem, o que significa que o item está devidamente protegido contra o item.

Correções de bugs

  • Corrija um ClassCastException em Quest#onClanAttacked.
  • Corrija um NegativeSizeArrayException no log do cliente. Descarte alguns erros de log relacionados a tentativas de cliente inválidas.
  • Corrija o NPE em Q635.
  • Correção do cálculo do PDAM antes da divisão de ataque/habilidade física da rev 399. Ty Yoska pelo relatório.
  • Corrija a limpeza automática do título do TradeList. Ty Denzel para relatório / correção.
  • Adicione de volta Config.PARTY_XP_CUTOFF_METHOD opção "nenhuma" ausente. Ty CUCU23 para relatório / correção.
  • Corrija os NPCs do "teto superior". Ty Bandnentans para consertar.
  • Corrigir o método de contribuição de pedra individual dos Sete Sinais. Ty //Dev para relatório.
  • Corrija a tabela de recompensas Q372 e a taxa de queda. Ty //Dev para relatório.
  • O Q348 agora distribui drops como aleatórios de parte, apesar das informações do cliente. Ty Denzel pelo relatório.
  • Conserte Benom se teletransportando para fora. Codifique outros locais de entrada/saída. Ty //Dev para relatório.
  • Não mostre o ícone de Cristalizar no inventário de Caçadores de Recompensas (era uma adição de CT1 GP1). Ty Bandnentans pelo relatório.
  • Substitua "weightPenalty" por "weightLimit" em vez de XMLs de habilidades. Ty //Dev para relatório/correção.
  • Quando os heróis participam de um ataque contra Antharas, Valakas e Baium, o monstro chefe tem a chance de gritar os nomes dos personagens heróis. Ty deekay para consertar.
  • Corrija a implementação do isRaidBoss (um lacaio raidboss sem mestre era considerado raidboss).
  • Corrigir Formigas Enfermeiras não curando a larva da Formiga Rainha.
  • Corrija uma SQLException na inicialização do servidor Olympiad.
  • Correção de uma SQLException sobre a remoção de membros do clã (já que o retrabalho das privs do clã).
  • Corrija o padrão 30169 npcId HTM. Ty Bandnentans pelo relatório.
  • Corrigir a opção de fenda ausente do Guia do Festival. Ty Denzel pelo relatório/semi-correção.
  • Algumas correções de fabricação de anões / gerais
    • Adicione a verificação de integridade da receita máxima ausente.
    • Em caso de falha na loja, chame de volta a janela de gerenciamento.
    • Em caso de falha na loja, não limpe a lista de fabricantes.
    • Após o sucesso da loja, limpe a lista de fabricação reversa (a loja geral bem-sucedida redefine o anão, a loja anã bem-sucedida redefine o geral).

Organização

  • Retrabalhe HtmCache e CrestCache para usar NIO. Mova CrestType para enumerações.
  • Implementação de WorldObject#forEachKnownType / WorldRegion#forEachType & forEachRegion - Evite a sobrecarga de lista em vários locais populares (principalmente verificações de broadcastPacket ou região - que são feitas em todas as verificações de lista conhecida).
  • Rework SkillList, agora ele é tratado como outros pacotes. Excluir o método Player#sendSkillList.
  • Exclua a classe DeadlockDetector e as configurações relacionadas.
  • Adicione GameServer#isServerCrash, com base na implementação LaRoja - sem usos, por enquanto.
  • Mova a classe IPv4Filter para commons.network, exclua o pacote net.sf.l2j.util.
  • Adicione a configuração DefaultSeeRange, use o valor de varejo 450 em vez de 400.
  • Adicione mais registros, obrigado LaRoja pelo pedido de mesclagem.
  • Exclua dimensionalRift.xml não utilizados.
  • Algumas otimizações de ItemContainer.
  • Renomeie todas as ocorrências de adenas para Adena.
  • Correções do SonarLint / UCDetector:
    • Descarte MathUtil#limit, use Math#clamp (introduzido no JDK21).
    • Descarte as seguintes configurações não utilizadas: FS_TIME_ENTRY, FS_TIME_END RAID_MINION_RESPAWN_TIMER.
    • Poucas edições públicas / protegidas / privadas. Muito mais por vir.
    • os casos de switch são mesclados (introduzidos no JDK12).
    • O objeto booleano é comparado a Boolean.FALSE/TRUE, não testado diretamente como um booleano.
    • String#replaceAll é substituído por String#replace quando um padrão regex não está envolvido.
    • Gerar alguns registros: Sequence, TutorialEvent.
    • Poucas variáveis baseadas em classe agora são locais.
    • Use HashMap.newHashMap em vez de new HashMap quando a capacidade for conhecida (mapas finais estáticos). HashMap.newHashMap evita definir a capacidade de 0,75 quando não é necessário.
    • O registro LogRecord foi renomeado para LogRecord logRecord, devido ao fato de record agora ser uma palavra-chave.
    • Use o padrão Singleton adequado para o tipo de instância (principalmente ouvintes).
    • Gere construtores privados chamando IllegalStateException para classes de utilitário.

I'm sorry about the leak, you're a good guy. I talked to you a little and I saw that you really want to do something good for the community. I stopped using your leaked sources years ago because it's unethical but I'm still using older sources with my own corrections. I hope your effort isn't wasted.

Posted
On 9/7/2024 at 2:23 PM, Tryskell said:

spacer.png

 

How will it work ? Everytime a new leak will occur

We will get updates of the pirate? and if so we will get new representation each time as well?

 

Tryskel to Pirates:

davy-jones.gif

 

Posted

@Nightw0lfI kept the PSD, so yes. If more leaks occur, another sacrifice will occur, until being purged.

 

@Trance Updates are pretty much constant, without counting under development content aswell. Revision is both a legacy and public event to get a review of what happened.

 

@Williams Consider to share fixes - they benefit to everyone.

  • 2 weeks later...
Posted

Since last massive leak as explained as 07/09 (notably all development branches), I don't accept anymore financial newcomers that easily. People will have to contribute 100 cookies worth of contributions (bug reports/fixes) as a first step to be accepted as Donator. Free user can join after sharing over 200 cookies out of contributions, compared to 100 cookies before.

You can say thanks to RusAcis, and notably his worthless leader, UnleashedForce.

The size of users will continue to shrink if more leaks occur, until true helpers only will be left.

New prices are as following :

Joining price: 200€ + 100 cookies, or 200 cookies
This fee has to be paid if you are joining aCis project. Next month, and all other months, you will have to donate only basic monthly donation.

Monthly price: 10€ / 10 cookies
This fee has to be paid every month.

I won't accept any new join fee before the 100 cookies contribution. Your money will be instantly sent back.

Also, in the same shape of idea, actual supporters/donators have to be active to stay in sources. It doesn't have to be a particular amount, you just have to share from time to time *anything*. I don't accept anymore silent ppl. Only useful people will be kept.

  • Thanks 1
  • Haha 2
  • 2 weeks later...
Posted

I'd like to join aCis community but i can't handle the contributions that often due to my job. I'm returning to L2 development after a few years away and it would be awesome getting this source to work. I can (and would like to) contribute with reviews and code now and then (i'm software engineer for global companies), but sadly i can't commit the time.

 

I have a hard sense of ethical to not not leak anything (my current web project is paid from nkdev even when there's a leaked version floating around.)

 

Please let me know when/if acceptance through donations is available again. @Tryskell

 

In the mean time, gl on your project. Sounds amazing.

Posted (edited)
On 10/7/2024 at 8:33 PM, mend3 said:

I'd like to join aCis community but i can't handle the contributions that often due to my job. I'm returning to L2 development after a few years away and it would be awesome getting this source to work. I can (and would like to) contribute with reviews and code now and then (i'm software engineer for global companies), but sadly i can't commit the time.

 

I have a hard sense of ethical to not not leak anything (my current web project is paid from nkdev even when there's a leaked version floating around.)

 

Please let me know when/if acceptance through donations is available again. @Tryskell

 

In the mean time, gl on your project. Sounds amazing.

 

Hello, you can share from time to time and build cookies out of it. Once you got 100 cookies, you can either add 200€ or 100 cookies more to get access.

 

Cookies are actually easy to get if you know how to code. Bounties are generally 100+ cookies reward, most fixes begin at 5 cookies (so 20 basic fixes is enough to make 100 cookies), any type of useful rework would be 30-50 cookies.

 

You got "the luck" to come in a time where public version is almost identical to private version - since both versions are pretty similar for now, whatever you find as issue is actually existing and need to be fixed.

 

After you are set on private, I don't request a full commitment ; I just need you to be here from time to time, report shits or sharing fixes. I just don't accept anymore 6/8/10/12 months ppl ghosts, saying and doing nothing.

 

It's enough to get 4-5 average active ppl to get the shit done.

 

Even if you suck at development, if you're a server admin, just sharing your players issues from your own forums is enough, for exemple - you just have to confirm it under PTS. It benefits you (you got free fixes), and it benefits me (I got reports).

 

If you're good at development, well, it's normally easier for you to build cookies. Find some bottlenecks, rework it, profit. I don't even need you to know Lineage 2 - just how to make things performant would be already fine.

 

If you don't have time, generally speaking, avoid to get involved with L2J - at all :D. I don't teach you anything saying programming is time-consuming.

Edited by Tryskell
  • Thanks 1

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

    • 📌 FORUM RULES (Revised – Legal Compliant) Η χρήση του forum προϋποθέτει την πλήρη αποδοχή των παρακάτω κανόνων. Οποιαδήποτε παραβίαση ενδέχεται να οδηγήσει σε περιορισμούς ή μόνιμο αποκλεισμό. 1. Spam & Κατάχρηση Δημοσιεύσεων Το spam απαγορεύεται. Μονολεκτικές, άσχετες ή πολλαπλές διαδοχικές δημοσιεύσεις δεν επιτρέπονται. Bumping επιτρέπεται μόνο στο Marketplace, μία φορά κάθε 24 ώρες. Απάντηση σε θέματα παλαιότερα των 6 μηνών δεν επιτρέπεται. Σχόλια τύπου «wrong section», «request lock» κ.λπ. απαγορεύονται — χρησιμοποιήστε το Report Section. 2. Συμπεριφορά & Τάξη Απαγορεύονται: βρισιές, trolling, drama, απειλές, ρατσισμός, flame posts. Οι κανόνες συμπεριφοράς ισχύουν και σε PMs, profile comments και λοιπές περιοχές. Πολιτικά θέματα επιτρέπονται μόνο εντός λογικών και πολιτισμένων ορίων. 3. Απαγορευμένο & Ακατάλληλο Περιεχόμενο Απαγορεύεται αυστηρά η δημοσίευση ή αναζήτηση περιεχομένου που είναι: Παράνομο βάσει ισχύουσας νομοθεσίας Πειρατικό (warez, cracks, serials, pirated software) Σεξουαλικό, πορνογραφικό ή βίαιο Προσβλητικό, ρατσιστικό ή εξτρεμιστικό Θρησκευτικά προκλητικό με σκοπό την ένταση ➡️ Όλα τα παραπάνω διαγράφονται άμεσα, χωρίς προειδοποίηση. 4. Διαφημίσεις & Προώθηση Απαγορεύεται κάθε μορφή διαφήμισης χωρίς έγκριση Administrator. Απαγορεύεται η προώθηση παράνομων ή μη αδειοδοτημένων υπηρεσιών. Affiliate links, referral systems και external promotions απαιτούν έγκριση. 5. Γλώσσα & Παρουσίαση Μην αναμειγνύετε γλώσσες (αγγλικά σε ελληνικά topics και αντίστροφα). Χρησιμοποιείτε tags [GR] ή [EN]. Τα Greeklish επιτρέπονται προσωρινά, ωστόσο προτιμάται η χρήση ελληνικών χαρακτήρων. 6. Credits & Πνευματικά Δικαιώματα Υποχρεωτική αναφορά πηγών και credits. Απαγορεύεται η αναδημοσίευση περιεχομένου χωρίς άδεια. Κάθε χρήστης είναι υπεύθυνος για τα δικαιώματα του περιεχομένου που δημοσιεύει. 7. Κυβερνοεγκλήματα & Επιβλαβείς Πρακτικές Απαγορεύεται αυστηρά: Hacking, DDoS, flooding, botnets, booters Οδηγίες, εργαλεία ή καθοδήγηση για παράνομες ψηφιακές επιθέσεις Αναζήτηση ή πώληση τέτοιων υπηρεσιών 8. Υπογραφές (Signatures) Μέγιστο μέγεθος: 800x300 pixels. Υπογραφές που παραβιάζουν τους κανόνες αφαιρούνται. 9. Λογαριασμοί & Ασφάλεια Ένας λογαριασμός ανά χρήστη. Κλεμμένοι, κοινόχρηστοι ή πολλαπλοί λογαριασμοί απαγορεύονται. Το forum διατηρεί το δικαίωμα άμεσης διαγραφής λογαριασμών. 10. Σεβασμός προς το Staff Υποτίμηση, απειλές ή προσβολές προς staff δεν γίνονται ανεκτές. Για διαφωνίες ή παραβάσεις χρησιμοποιήστε το Report Section. LEGAL POLICY (Updated – Strict Compliance) 1. Νομιμότητα Περιεχομένου Απαγορεύεται κάθε περιεχόμενο που: Παραβιάζει νόμους ή κανονισμούς Παραβιάζει copyright ή intellectual property Προωθεί παράνομες οικονομικές, τραπεζικές ή επενδυτικές υπηρεσίες Σχετίζεται με απάτη, phishing, money laundering 2. DMCA – Copyright Protection Το forum συμμορφώνεται πλήρως με τον DMCA. Έγκυρες αναφορές οδηγούν σε άμεση αφαίρεση περιεχομένου. Επαναλαμβανόμενες παραβιάσεις = μόνιμος αποκλεισμός. 3. AML / Financial Compliance Απαγορεύεται περιεχόμενο σχετικό με ξέπλυμα χρήματος. Απαγορεύεται η προώθηση μη αδειοδοτημένων χρηματοοικονομικών υπηρεσιών. Δεν παρέχεται καμία οικονομική ή επενδυτική συμβουλή. 4. User-Generated Content & Ευθύνη Όλο το περιεχόμενο δημιουργείται από τους χρήστες. Το forum δεν φέρει νομική ευθύνη, αλλά: Παρακολουθεί Διαγράφει Συμμορφώνεται με τον νόμο 5. AI Moderation Χρησιμοποιούνται AI-based εργαλεία για εντοπισμό παραβάσεων. Η τελική απόφαση λαμβάνεται πάντα από άνθρωπο. 6. Τελικές Διατάξεις Οι κανόνες μπορούν να τροποποιηθούν χωρίς προειδοποίηση. Η χρήση του forum συνεπάγεται αποδοχή όλων των πολιτικών. Η άγνοια των κανόνων δεν αποτελεί δικαιολογία.   ΠΟΛΙΤΙΚΗ ΑΠΟΡΡΗΤΟΥ (Privacy Policy) – Ελληνικά Η παρούσα Πολιτική Απορρήτου περιγράφει τον τρόπο με τον οποίο το forum συλλέγει, χρησιμοποιεί και προστατεύει τα προσωπικά δεδομένα των χρηστών του, σύμφωνα με τον Γενικό Κανονισμό Προστασίας Δεδομένων (GDPR – ΕΕ 2016/679). 1. Συλλογή Δεδομένων Το forum ενδέχεται να συλλέγει τα ακόλουθα δεδομένα: Όνομα χρήστη (username) Διεύθυνση email IP address Ημερομηνία και ώρα σύνδεσης Περιεχόμενο δημοσιεύσεων (posts, topics, private messages) Δεν συλλέγονται ευαίσθητα προσωπικά δεδομένα. 2. Χρήση Δεδομένων Τα δεδομένα χρησιμοποιούνται αποκλειστικά για: Τη λειτουργία και ασφάλεια του forum Τη διαχείριση λογαριασμών Τη βελτίωση της εμπειρίας χρήσης Την πρόληψη κατάχρησης, απάτης ή παράνομων ενεργειών Τη συμμόρφωση με νομικές υποχρεώσεις 3. User-Generated Content Όλο το περιεχόμενο που δημοσιεύεται στο forum δημιουργείται από τους χρήστες. Οι χρήστες φέρουν την αποκλειστική ευθύνη για τα δεδομένα που επιλέγουν να δημοσιεύσουν. 4. Cookies Το forum χρησιμοποιεί cookies μόνο για: Διατήρηση σύνδεσης χρήστη Βασική λειτουργικότητα Ασφάλεια Δεν χρησιμοποιούνται cookies για διαφημιστική παρακολούθηση τρίτων. 5. AI & Αυτοματοποιημένη Επεξεργασία Το forum ενδέχεται να χρησιμοποιεί αυτοματοποιημένα ή AI-based εργαλεία για: Ανίχνευση spam Εντοπισμό παραβιάσεων κανόνων ή παράνομου περιεχομένου ➡️ Οι αποφάσεις επιβολής λαμβάνονται πάντα από άνθρωπο. 6. Κοινοποίηση Δεδομένων Τα προσωπικά δεδομένα: Δεν πωλούνται Δεν διαμοιράζονται με τρίτους Εξαίρεση υπάρχει μόνο εφόσον απαιτείται από τον νόμο ή αρμόδιες αρχές. 7. Δικαιώματα Χρηστών (GDPR) Οι χρήστες έχουν δικαίωμα: Πρόσβασης στα δεδομένα τους Διόρθωσης ή διαγραφής Περιορισμού επεξεργασίας Υποβολής αιτήματος διαγραφής λογαριασμού 8. Ασφάλεια Δεδομένων Λαμβάνονται εύλογα τεχνικά και οργανωτικά μέτρα για την προστασία των δεδομένων, ωστόσο καμία πλατφόρμα δεν είναι απολύτως ασφαλής. 9. Τροποποιήσεις Η παρούσα πολιτική μπορεί να τροποποιηθεί χωρίς προηγούμενη ειδοποίηση. Η συνέχιση χρήσης του forum συνιστά αποδοχή των αλλαγών. ✅ Σημείωση Οποιοδήποτε παράνομο περιεχόμενο δεν επιτρέπεται πουθενά στο forum, ανεξαρτήτως ρόλου, πρόσβασης ή status (VIP / Donator / Staff). 📌 FORUM RULES (English – Legal Compliant) By accessing or using this forum, you agree to comply with the following rules. Violations may result in warnings, restrictions, or permanent account termination. 1. Spam & Abuse Spam is strictly prohibited. One-word, low-effort, off-topic, or consecutive posts are not allowed. Bumping is allowed only in the Marketplace, once every 24 hours. Replying to topics older than 6 months is not permitted. Posts such as “wrong section”, “request lock”, etc. are not allowed — use the Report Section instead. 2. Conduct & Behavior Insults, harassment, trolling, threats, racism, flame posts, and toxic behavior are prohibited. These rules apply to all areas, including private messages and profile comments. Political discussions are allowed only within reasonable and respectful limits. 3. Prohibited & Illegal Content The following content is strictly prohibited anywhere on the forum: Any content that violates applicable laws or regulations Pirated software, warez, cracks, serials, or copyright-infringing material Malware, hacking tools, exploits, or harmful code Sexual, pornographic, violent, or extremist material Hate speech, discrimination, or incitement Content intended to provoke religious or social conflict ➡️ Such content will be removed immediately, without notice. 4. Advertising & Promotion Advertising of any kind requires prior administrator approval. Promotion of illegal or unlicensed services is strictly forbidden. Affiliate links, referral systems, and external promotions require approval. 5. Language & Formatting Do not mix languages (English in non-English topics and vice versa). Use [GR] or [EN] tags when creating a topic. Greeklish is temporarily allowed, but native characters are preferred. 6. Credits & Intellectual Property Proper credit must be given when using third-party content. Reposting content without permission is prohibited. Users are solely responsible for the intellectual property rights of their posts. 7. Cybercrime & Harmful Activities Strictly prohibited: Hacking, DDoS, flooding, botnets, booters Requests, guides, tools, or services related to cyber attacks Buying, selling, or searching for such services 8. Signatures Maximum allowed size: 800x300 pixels. Non-compliant signatures will be removed. 9. Accounts & Security One account per user is allowed. Stolen, shared, or multiple accounts are prohibited. The forum reserves the right to suspend or delete accounts immediately. 10. Respect Toward Staff Disrespect, threats, or harassment toward moderators or administrators will not be tolerated. Use the Report Section to address issues. ⚖️ LEGAL POLICY (English – Strict Compliance) This policy defines the legal framework governing forum operation. 1. User-Generated Content & Liability All content is created by users. The forum and its staff are not legally responsible for user-generated content. Reasonable efforts are made to monitor, review, and remove unlawful material. 2. Legal Compliance Content that violates: Local, national, or international laws Intellectual property rights Terms of third-party services is strictly prohibited. 3. DMCA – Copyright Policy The forum complies fully with the Digital Millennium Copyright Act (DMCA). Valid takedown requests result in prompt content removal. Repeat copyright offenders will be permanently banned. 4. AML – Anti-Money Laundering Prohibited content includes: Money laundering schemes or instructions Fraud, scams, or financial manipulation Promotion of unlicensed or illegal financial services The forum cooperates with authorities when legally required. 5. FCS – Financial & Compliance Services The forum does not provide financial, investment, or legal advice. Promotion of unregulated banking, investment, or financial services is forbidden. 6. Privacy & GDPR Publishing personal data of others is prohibited. Sharing private communications without consent is forbidden. The forum operates in compliance with GDPR regulations. 7. AI-Assisted Moderation Automated and AI-based tools may be used to detect violations. All enforcement actions involve human review. 8. Final Provisions Policies may be updated without prior notice. Continued use of the forum constitutes acceptance of all rules. Ignorance of the rules is not an excuse. PRIVACY POLICY – English Version This Privacy Policy explains how the forum collects, uses, and protects user data, in accordance with the General Data Protection Regulation (GDPR – EU 2016/679). 1. Data Collection The forum may collect the following data: Username Email address IP address Login timestamps User-generated content (posts, topics, private messages) No sensitive personal data is intentionally collected. 2. Use of Data Data is used solely for: Forum operation and security Account management Improving user experience Preventing abuse, fraud, or illegal activity Legal and regulatory compliance 3. User-Generated Content All content posted on the forum is created by users. Users are solely responsible for any personal data they choose to publish. 4. Cookies Cookies are used only for: Session management Essential functionality Security purposes No third-party advertising or tracking cookies are used. 5. AI & Automated Processing The forum may use automated or AI-assisted tools to: Detect spam Identify rule violations or illegal content ➡️ All enforcement decisions are subject to human review. 6. Data Sharing Personal data is: Not sold Not shared with third parties Except where required by law or competent authorities. 7. User Rights (GDPR) Users have the right to: Access their personal data Request correction or deletion Request restriction of processing Request account deletion 8. Data Security Reasonable technical and organizational measures are implemented to protect data. However, no online platform can guarantee absolute security. 9. Policy Updates This policy may be updated at any time without prior notice. Continued use of the forum constitutes acceptance of the updated policy. ✅ Final Note If you have concerns regarding privacy or data protection, please contact the forum administration. ✅ Important Notice Illegal content is not allowed anywhere on the forum, regardless of user role, status, or access level.
    • Hello everyone, This topic has been created to report any content that is considered illegal under applicable law or in violation of the forum rules. This includes, but is not limited to: Illegal software (pirated, cracked, or unauthorized software) Copyright-infringing material Malware, viruses, or any harmful code Scams, fraud, phishing attempts, or impersonation Illegal banking or financial services Money laundering activities or related instructions Any other illegal, unethical, or rule-violating activity — you name it If you encounter any such content, please report it here so it can be reviewed and removed promptly. Legal Disclaimer All content published on this forum is created and posted by its users. The forum administration does not take responsibility for user-generated content. However, we make every reasonable effort to monitor, review, remove, and maintain the forum by deleting illegal or rule-violating content as soon as it is reported or identified. By using this forum, you acknowledge and agree to these terms.     Moderator Notice We would like to inform all users that we are currently developing a custom AI-powered API tool that will assist our moderation team in scanning the forum database for illegal or rule-violating activity. This system will be used strictly as a support tool to help identify potentially problematic content, which will then be reviewed by human moderators before any action is taken. The goal is to improve forum safety, compliance, and response time while maintaining fairness and transparency. 🚧 Coming soon — more details will be shared once the system is ready. Thank you for your cooperation and for helping us keep the forum clean and lawful.
    • Reporting Illegal or Rule-Violating Content (post here)
    • If anyone is reading this, until we find the 488 protocol system that works with AuthD + Authgated from High Five (HF), just use L2Filter included in the leak as the login server to be able to play. hAuthd does not works with this chronicle, @Hint. do you happen to know about this?   Be aware of the system you use! If UseEMailAccount is set as true in l2.ini, your user_info table linked to your account must have email column not NULL with a valid e-mail, and you will use that e-mail to login instead of the account name. (Post merged)   OKAY! Nevermind about the above, I just figured it out, AuthD and Authgated from HF requires GameGuard to be enabled and UseEMailAccount set to false. Enable GameGuard at server side as per Fyyre instructions,  Add the missing GameGuard files in your client system: https://mega.nz/file/xZMWQBjK#triEj7My9B9roiLqAKk32HOLcLmPynoOm-QhBI_Ligw
  • Topics

×
×
  • Create New...

AdBlock Extension Detected!

Our website is made possible by displaying online advertisements to our members.

Please disable AdBlock browser extension first, to be able to use our community.

I've Disabled AdBlock