Jump to content
  • 0

Question

Posted

Hello, i have a little problem with drop RB

 

When RB drop some enchant scroll, server say : Npc died and drop : 3 enchant weapon S for example. The player loot the EWS but he has only 1 EWS in the inventory..

 

Other problem : When player loot (for example) 3 draconic bow shaft, the server display : you loot draconic bow shaft (as if he loot only 1 shaft) but he has 3 in inventory (it's a minor bug, but it's still a bug..)

 

And one question : How to make /vendor only on specific place in giran ?

 

 

12 answers to this question

Recommended Posts

  • 0
Posted

What client and pack u use?

 

about the shops, u will need to make new type of zone, make new class for it, after that u will need to find code which is checking if other conditions for making shop are satisfied and add there there check if player is inside zone u have just made, piece of cake :)

  • 0
Posted

When i dl your  pack, i look scripts.cfg and some of (at least 50% maybe more) are with # at the beginning of the line :S So isn't a pack for middle rate :S

 

Anyway thanks :)

  • 0
Posted

When i dl your  pack, i look scripts.cfg and some of (at least 50% maybe more) are with # at the beginning of the line :S So isn't a pack for middle rate :S

 

Anyway thanks :)

 

[fr]C'est l'excuse bidon ça, depuis le temps tu devrais savoir - si tu suis un peu le forum - que tout passe par un re-travail complet. A l'époque il y a eu les skills, après les items, maintenant les quêtes. Ca suit un cheminement parfaitement logique. Maintenant dis la même chose de Frozen, j'attends de voir ça :P. Frozen n'a pas de "#" à ses scripts, mais vla la pelletée de bugs que ce pack traîne dans son sillage.

 

Et oui, 30% *seulement* des scripts sont actuellement réécrits. Mais ils ont le mérite d'être autant retail que possible. Je peux te citer une dizaine de quêtes foireuses, une autre dizaine de quêtes purement customs, les AIs incomplètes (notamment Baium) et j'en passe.

 

Le syndrome L2J, "j'utilise beaucoup de trucs cassés plutôt que peu de trucs qui marchent correctement." Chacun voit midi à sa porte :P.[/fr]

 

And sorry if you're not french, so far you should :P.

  • 0
Posted

[fr] j'aimerais bien vous aider, mais mon niveau en .py est treeees limité x). Non mais je suis totalement d'accord avec toi mais dans tout les cas, le pack aCis, bien que treees performant et tres clean, les quetes sont pas finis, donc le pack ne peut pas vraiment fonctionner pour un middle rate :S. Et ouai, je peut pas en dire pareil pour Frozen x)[/fr]

 

 

  • 0
Posted

[fr]Y'a pas de quests/scripts en python sur aCis :P. Je déteste ce language en mousse. Pour ça que ça prend du temps le DP niveau quests, je (et les gens qui m'aident) corrige tout un par un.

 

Btw, je sais pas si tu as vu, ces derniers temps Frozen est "légèrement" refroidi (c'est le cas de le dire, muhaha), 2 commits en 1 mois.

 

Sur frozen, et si Scoria n'a pas changé ça (parce qu'entre nous, les gros changements viennent de Scoria, pas de Shyla/Nefer :P), toutes les quests avec des items sont exploitables (drop par terre en cours de dialogue, continue le dialogue comme si de rien n'était sans check).[/fr]

 

And for others, go Google translate it :P. It's for all the time I read freakin greek in english section !

  • 0
Posted

[fr]Si seulement je pouvais vous aider pour avancer.. Mais bon. C'est quel langage que vous utilisez pour les quests? Ouai je suis d'accord, mais bon niveau properties le pack est super utile . [/fr]

 

+1 for Tryskell

Guest
This topic is now closed to further replies.


  • Posts

    • LIVE VERIFICATION? SUMSUB? “IMPOSSIBLE”? ▪ Spoiler: it is possible — if you know who to work with. A client came in with a task to pass **live verification** on **WantToPay**, a Telegram virtual card service. On the platform side — **Sumsub**: liveness check, SMS, manual review. “Fast” and “by eye” simply don’t work here. › What was done: → analyzed the verification scenario and Sumsub requirements → built the correct flow: phone number, email, timing → **completed live verification remotely, without account handover** → handled SMS and confirmation codes → brought the process to final approval ▪ Result: → verification passed → access granted → no flags or repeat requests ▪ Live verification is not luck. It’s scenario-based preparation — not hope. › TG: @mustang_service ( https:// t.me/ mustang_service ) › Channel: Mustang Service ( https:// t.me/ +6RAKokIn5ItmYjEx ) *All data is published with the client’s consent.* #verification #sumsub #livecheck #kyc #case
    • IMPORTANT INFO: In a few days, I will switch to completely new code, written from scratch with a new download system, patch building and management system. The Updater will become true 2026 code with "foolproof systems". I'm going to create a Discord server for customers to request new ideas and features. FIRST CUSTOMERS ARE ALREADY USING THE NEW UPDATER ON LIVE SERVERS! Watch this topic for upcoming info because the new updater is around the corner! Yes, you can still use self-update on the previous updater! No, the new updater won't be compatible with the old patch system! A new build is required, but players who already have game files won't have to download the entire patch again! New templates and updates to existing templates are coming soon! Sneak peek:  
    • i used guytis IL project and source. i found in his project there are 3 Client version source... 1,CliExt_H5   --->this one cant be compiled in VS2005,i did know why..is it for H5 client? 2,CliExtNew  --->this one is IL version ,but when i compiled it and use it.player cant login game,MD5Checksum wrong.i check the source code,but not found any hints. 3,L2Server    --->this one for HB client?im not sure...   so my question is what are the differences between these three versions of cliext.dll?how can i fix the issue of the MD5Checksum not matching problem?   01/29/2026 21:04:11.366, [CCliExt::HandleCheckSum] Invalid Checksum[1130415144] vs [-721420287] packet[dd] len[29] sum[2698] key[30] HWID[] Account[]! 01/29/2026 21:04:11.366, SocketLimiter::UserSocketBadunknownprotocol 11111111111 01/29/2026 21:04:11.366, [usersocket]unknown protocol from ip[113.137.149.115]!      
  • 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..