Jump to content

Recommended Posts

Posted

this is all u do as far as i can see,

help or keep it for u, since ur not right.

 

actually i am right with it you just lack of knowledge to understand it so please dont be that ignorant or dont point your finger at me with "he flamed him he flamed him" cause thats not the case.

Posted

actually i am right with it you just lack of knowledge to understand it so please dont be that ignorant or dont point your finger at me with "he flamed him he flamed him" cause thats not the case.

im just looking on ur current posts.

u just like to talk.

Posted

im just looking on ur current posts.

u just like to talk.

 

Like to talk?Okay than proove me wrong on anything regarding to l2j anything if you want open a topic somewhere and ask atleast we can leave the spam out of this topic...

Posted

Like to talk?Okay than proove me wrong on anything regarding to l2j anything if you want open a topic somewhere and ask atleast we can leave the spam out of this topic...

what l2j ? the one u fail :)) ?

Posted

as i said leave the spawm out of here and try to proove me wrong if you can :)

i dont want to prove u anything, since regarding to ur posts, u prove me a lot.

+ the chat i had with u on msn some time ago.

 

let this project finish his job, and dont talk about it when he is still in a egg.

and about spam, who's talking ? regarding to all ur posts that are the same. i dont know who spam moar.

Posted

trollty.jpg

 

Bha, IntrepidTroller :P.

 

If you read what I code, you will know I'm aware about Freya changes. "Know your enemy..." I didn't commit things like archer distance, static cooldowns, shield blocking magic (well it's what actually come in my mind). Or better say, I refactored as Freya is, but reverted to IL some parts of the code.

 

I don't need you agree with my project, you got an 'known problem' with IL and IL lovers (with people more simply), and as you seems to be back, I couldn't be "not" trolled about this personal choice.

 

Some choices have to be made, and I don't present the project to be retail-like, but the most "up-to-date" concerning features and methods. IL retail can't be reached, as L2Off IL isn't even retail-like. If L2J is 75% retail, L2Off is 95%. Still it's not retail. Retail can't be reached, but I can approach the 90% better than the original 75%, plus improving general code.

 

If I was copying skills from Freya, be aware I would have finished it since some weeks already... For you, "stupids demons of stupidity", I repeat once : I use IL as main build (values/effects/values effects), and refactor using Freya (isDebuff, saveVs, nextActionIsAttack,...). Some parts are even copied from Hellbound, as the ImmobileUntilAttacked effect (Meditation / ForceMeditation) which doesn't exist in Freya. Stop pointless offtopic then.

 

You try to fight with the wrong person talking with Sido, he's not aware about what I have changed, change and will change. Yourself, you do stupid (your favorite word fit well to you in this particular case) suppositions (like those ppl saying "aCis = fail" when they support a project using my own commits...) without even checking timeline.

 

I'm cold-minded and you make me more laugh than being upset.

 

Next time, do constructive posts. It doesn't have to be fully positive, nor positive. But avoids stupid attacks on non-existent problems. I know what I do, and if it's long, there is a reason. I verify what I commit using many websites, old answers from forums too.

 

-----

 

About next changes, to avoid to do a total offtopic (as Intrepid seems to like to bring chaos whenever he goes) :

 

PunishLevel (from Coyote share's idea), with a couple of adminhandlers refactors and shutdown refactor.

 

Yeah, from Freya. Admincommandhandlers will be disbalanced... MMOCore is disbalanced, friendinvite too... This is weird fork, really :(.

Posted

Bha, IntrepidTroller :P.

 

If you read what I code, you will know I'm aware about Freya changes. "Know your enemy..." I didn't commit things like archer distance, static cooldowns (well it's what actually come in my mind). Or better say, I refactored as Freya is, but reverted to IL some parts of the code.

 

I don't need you agree with my project, you got an 'known problem' with IL and IL lovers (with people more simply), and as you seems to be back, I couldn't be "not" trolled about this personal choice.

 

Some choices have to be made, and I don't present the project to be retail-like, but the most "up-to-date" concerning features and methods. IL retail can't be reached, as L2Off IL isn't even retail-like. If L2J is 75% retail, L2Off is 95%. Still it's not retail. Retail can't be reached, but I can approach the 90% better than the original 75%, plus improving general code.

 

If I was copying skills from Freya, be aware I would have finished it since some weeks already... For you, "stupids demons of stupidity", I repeat once : I use IL as main build (values/effects/values effects), and refactor using Freya (isDebuff, saveVs, nextActionIsAttack,...). Some parts are even copied from Hellbound, as the ImmobileUntilAttacked effect (Meditation / ForceMeditation) which doesn't exist in Freya. Stop pointless offtopic then.

 

You try to fight with the wrong person talking with Sido, he's not aware about what I have changed, change and will change. Yourself, you do stupid (your favorite word fit well to you in this particular case) suppositions (like those ppl saying "aCis = fail" when they support a project using my own commits...) without even checking timeline.

 

I'm cold-minded and you make me more laugh than being upset.

 

Next time, do constructive posts. It doesn't have to be fully positive, nor positive. But avoids stupid attacks on non-existent problems. I know what I do, and if it's long, there is a reason. I verify what I commit using many websites, old answers from forums too.

 

-----

 

About next changes, to avoid to do a total offtopic (as Intrepid seems to like to bring chaos whenever he goes) :

 

PunishLevel (from Coyote share's idea), with a couple of adminhandlers refactors and shutdown refactor.

 

Yeah, from Freya. Admincommandhandlers will be disbalanced... :(

 

hehe ofc i just mentioned that it can happen after some time i really dont mind what project whoever works on just mentioned a thing that can be happen :P

Posted

flame what?seriously i've seen the changes and its clear adaptation of things from freya to il...

 

hehe ofc i just mentioned that it can happen after some time i really dont mind what project whoever works on just mentioned a thing that can be happen Tongue

 

One word : You are exceptional :P. Ok it's 3, but still you worth it.

 

Back to topic plx :).

Posted

thanks for this nice share

this is not a share. it's a project (spamzor).

 

So after your next commit, you will refactor friendinvite or all of the commands? :)

Posted

See, it's those sorts of comments which are bad, or at least who show how bad are ppl :P.

 

Friends/blocklist are refactored since rev 46 (since 1 month ago). http://trac.assembla.com/acis_project/changeset/46

 

I will continue on skills, but begin admin commands aswell to split the boringness of skills XMLs.

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

    • 🏆 UPDATE: CLAN RACE — R$ 300 (PIX in Brazil, or the equivalent in USDT/PayPal) for the first clan ready for World B PvP Worlds opens on Friday, September 25, 19:00 BRT (GMT-3). Everyone starts together, from scratch. The challenge: the first clan with 9 members ready to enter World B wins. Ready = level 51, World C registered and the full C set equipped (weapon, armor and jewelry) with at least 3 attributes on each piece. Only Queen Ant stands between you and World B. Rules: main character only; 9 different people, each on their own PC; the server records the exact time each member became ready. Deadline: October 14. Sign up your clan on our Discord (link on the site): l2mog.com/pvp
    • 🚀 L2-Gold Custom PvP – Beta Test is LIVE! 🚀 Hey guys! We are opening a brand new Custom PvP server and looking for passionate players to help us test it out before the official grand opening! 💥 What we offer: High Rates & Custom PvP Gameplay Custom NPC Buffer, GM Shop & Global GK Balanced classes and epic custom items Interlude with c4 skills 🎁 Beta Rewards: Every active tester who reports bugs or gives feedback will receive Exclusive Custom Rewards on the official launch day! 🛑 No website needed yet! All files, patch, and support are inside our Discord. 🔗 Join Beta Test Here: [https://discord.gg/9qkSxQtTq]
    • "CAN YOU DO A BULGARIAN REVOLUT?" – WE DID. FIRST DRAFT, NO EDITS The request came in short: a photo of a bank card, Bulgaria, Revolut. We said yes and asked the only question that matters – what data. The client was on the road, asked for a couple of hours, then sent the lot: number, expiry, CVV, payment system, bank, cardholder name. Then came the part the client never sees: - ran the number through Luhn – the check digit has to add up, otherwise the card is dead the second anything automated looks at it - matched the BIN to the issuer: Revolut in Bulgaria isn't a "local bank", the cards run through Revolut Bank UAB. The number range has to actually belong there, not just start with the right digit - built the current design, not a five-year-old picture: vertical layout, flat laser print instead of embossing, correct chip module, contactless mark where it belongs - the payment system logo – with the right gradient where the circles overlap and the wordmark sitting exactly where it should. A small thing that kills half the fakes out there - and finally, physics. Plastic has to catch light: a highlight along the edge, a micro-shadow under the chip, a faint fingerprint. A phone shot, not a render Sent the draft for approval. The client looked it over, signed off with zero corrections – final files went out. One pass, no rework. A card is a deceptively simple document. Looks like a rectangle and sixteen digits. In reality it's maths in the number, a tie to the issuer, a current design and light on plastic. Miss any one of the four and the file gets exactly two seconds of attention. Need a card for a specific bank and country? Message us. We'll tell you straight what's realistic for your case – then build it. { all data published with the client's consent} › TG: @mustang_service_ms ( https:// t.me/ mustang_service_ms ) › Channel: Mustang Service ( https:// t.me/ +JPpJCETg-xM1NjNl ) #drawing #card #photoshop #revolut #case
    • ============================================================               CLExt Classic Interlude: v7.80 ============================================================   01. Fixed ValidateLocation handling and player/client position synchronization. 02. Added protection against invalid coordinates and characters falling under the map. 03. Improved XY/Z position and heading validation. 04. Fixed MoveToLocation and MoveToPawn packet conversion and target validation. 05. Fixed TargetSelected, TargetUnselected and MyTargetSelected packet handling. 06. Improved GeoData Z-location handling and disabled unsafe PathNode modifications. 07. Added ExUserInfoInventoryWeight support. 08. Fixed inventory weight and maximum load synchronization. 09. Fixed incorrect 0% inventory weight after character login. 10. Added automatic inventory weight updates after EnterWorld and inventory changes. 11. Added inventory weight packet spam protection and safe weight caching. 12. Fixed BuyList and SellList inventory, slot and weight synchronization. 13. Improved NPC target and Buy/Sell packet validation. 14. Reworked mail attachment inventory and weight validation. 15. Added all-or-nothing mail attachment receiving and safe retry handling. 16. Fixed stackable mail attachment validation and INT_MAX overflow protection. 17. Improved COD Adena validation and post-mail inventory weight refresh. 18. Improved Warehouse Deposit and Withdraw validation. 19. Added protection against malformed warehouse item counts, DBIDs and amounts. 20. Added warehouse INT_MAX, CItem and pSID validation. 21. Improved warehouse anti-dupe protection. 22. Reworked the HTML Cache system for improved stability and memory usage. 23. Added lazy HTML loading instead of loading ~20,000 files during startup. 24. Fixed HTML Cache startup crashes with large HTML collections. 25. Added thread-safe HTML Cache access and Clear/Reload support. 26. Added bad allocation, invalid HTML and oversized HTML protection. 27. Reduced HTML Cache RAM usage, startup allocations and disk I/O. 28. Added HTML Caching ON/OFF with live HTM loading support. 29. Fixed ToggleCachingHook and added VS2005-compatible live HTML handling. 30. Fixed ShortcutInit processing and skill synchronization order. 31. Improved shortcut item validation, augmentation handling and va_list safety. 32. Added LiveMode Ability Point system. 33. Added inventory-item-based Ability Points with configurable pointItemId. 34. Preserved the original level-based Ability Point system as fallback. 35. Fixed incorrect Ability Point display and inventory synchronization. 36. Improved Ability skill learning and point validation. 37. Improved OfflineShopRestore loading and FakePC/DBID handling. 38. Added safer OfflineShopRestore socket limits and batch processing. 39. Prevented thousands of restore sockets from loading simultaneously. 40. Added delayed, non-blocking OfflineShopRestore after server startup. 41. Improved OnEnterWorld initialization order and stability. 42. Improved inventory weight, SkillList and acquired-skill initialization after login. 43. Added VIP integration to the EnterWorld process. 44. Added safe UserExtData initialization without modifying the native User structure. 45. Improved duplicate Bronch Jewel and equipped-slot protection. 46. Improved Bracelet, Belt, Bronch and general UseItem validation. 47. Improved general packet, UserSocket, User, pSD and Creature validation. 48. Added safer INT32/INT64 packet handling and malformed-packet protection. 49. Improved L2Server startup memory usage and lazy resource loading. 50. Reduced unnecessary startup allocations. 51. Improved account-only KeyEngine authentication and remote account validation. 52. Removed account expiration-time requirements. 53. Added updater/restart design without requiring CLExtUpdate.exe. 54. Improved CLIEXT HWID, shared-memory and client/server version validation. 55. Improved ReadFile/WriteFile hooks and MemoryProtector handling. 56. Added UoPilot and Extreme Injector detection handling. 57. Reworked VIP point loading, saving and database synchronization. 58. Fixed VIP Level 0 initialization and first VIP activation. 59. Fixed vip.htm activation after login and from party-shared points. 60. Fixed VIP points being incorrectly reset before successful activation. 61. Improved VIP progression from Level 1 through Level 7. 62. Added proper VIP Level 7 MAX/DONE behavior with no Level 8 requirement. 63. Disabled further VIP point collection after reaching maximum level. 64. Reworked VIP BonusInfo/ReceiveVipInfo packet synchronization. 65. Fixed VIP tier, points, duration and level requirement packet fields. 66. Added VIP duration, tier, point and User validation protections. 67. Added safer 64-bit VIP EXP and party EXP calculations. 68. Preserved subclass maximum EXP protection. 69. Improved ItemDataEx validation during character loading. 70. Fixed augmentation loss during login, relog and server restart. 71. Added safe restoration of augmentation IDs directly from the database. 72. Added CItem, pSID, pExItem and User validation during ItemDataEx loading. 73. Improved Shadow Item mana and item lifetime loading. 74. Preserved item protection timeout data during character loading. 75. Added augmentation loading diagnostics and protected valid augmentation data. 76. Preserved database value 0 for genuinely non-augmented items. 77. Added RaidBoss Status synchronization with the World Map. 78. Fixed alive/dead RaidBoss status updates after spawn and death. 79. Added RaidBossStatus as the source of truth for RaidBoss map packets. 80. Fixed RaidBoss map status synchronization after server/database loading.
  • 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..