Jump to content
MaxCheaters Official Group on Discord
Top.MaxCheaters.com is now OPEN – Lineage 2 Top Listing

Don't bullshit me

PwNNNz0r.^

By PwNNNz0r.^
in Report Section

 Share

Recommended Posts

PwNNNz0r.^ Iron Initiate

PwNNNz0r.^

Posted
Posted

Just to know, there are no more warns for old people here at mxc.

You must all know the rules already looooooong time ago.

 

This is the most idiotic thing EVAH!

Only because someone is older then other members that doesn't mean he shouldn't be warned before being punished or something.

If someone had never done something punishable in the past it's just not fair to punish him w/o even warning him before.

All members should receive the same damn treatment, no matter if he's new or old. Whenever someone joins a community, the first thing he should do is reading the rules, so there's no reason the new members shouldn't know the rules and the old ones yes.

So being old in a community it's not a reason for being punished at the first rule infringement.

 

EboLLa Iron Initiate

EboLLa

Posted
Posted

 

If someone had never done something punishable in the past it's just not fair to punish him w/o even warning him before.

 

Very true... because he is very old and never had done something he should get a second chance not be punished without warning...

Reptant_ Iron Initiate

Reptant_

Posted
Posted

I am talking to specific people, that have got to all this situation.

 

I got mad with his topic ' I wasn't warned atleast 15 times yet'

 

 

Do you wanna know what i mean by that?

 

In spam section, 3 people get banned cause of abusing karma/playing with karma.

We warn them public, and 'Gregor' (in this case) sees all warns, and all this shit

 

then, he makes an abuse.Are we supposed to warn him again and again?

(This is just an example btw)

 

Come real please,it's like saying, 'I have 1 abuse to do till i get punished' (lol..)

 

And dekarma = warn somehow, in this case

 

PwNNNz0r.^ Iron Initiate

PwNNNz0r.^

Posted
  • Author
Posted

I'm not talking about gregor or anyone in specific, I just quoted your sentence and told that it has no sense, it's totally a bullshit for me.

 

Come real please,it's like saying, 'I have 1 abuse to do till i get punished' (lol..)

It also depends on the case, if someone does something really serious and does it on purpose of course he should be punished, but, since you talked about gregor, he even told he didn't realize the topic was in EN because the previous guy posted in gr too, and as he said the other guy didn't got punished and he got punished (dunno if it's true im just giving you an example)

Global warnings, like posts in topics, are useless, maybe the guy you wanted to warn with misunderstands and thinks the warn is not for him but for someone else. Better warn via PM

 

And no, we are not supposed to give you 15 warns, before we actually give the lowest punishment..

Did i said that?
PwNNNz0r.^ Iron Initiate

PwNNNz0r.^

Posted
  • Author
Posted

You still didn't got that I'm not talking about gregor, but about the thing that old members won't be warned before being punished.

Because among the old members there are a lot of non-greek members.

PwNNNz0r.^ Iron Initiate

PwNNNz0r.^

Posted
  • Author
Posted

Think before you post too, your sentence can be easily misunderstood.

You told you (plural) won't warn people anymore here at MXC, so you were referring to everyone.

PwNNNz0r.^ Iron Initiate

PwNNNz0r.^

Posted
  • Author
Posted

Dont worry pwnnnzor, you are not old member  if you're scared :D

oh then you can lock it, or maybe not

 

Actually to be honest, finito is totally right on this.

then explain me why, 'cause i already explained why this isn't fair
Vazelos Iron Initiate

Vazelos

Posted
Posted

A member here from 2009 for example, supposed to know the rules. He don't need a warning in order to get punished for his actions. Warnings are for newcomers.

yhn Iron Initiate

yhn

Posted
Posted

A member here from 2009 for example, supposed to know the rules. He don't need a warning in order to get punished for his actions. Warnings are for newcomers.

At least 1 warning should be done.

Anyway...

Guest
This topic is now closed to further replies.
 Share
Go to topic listing


  • Posts

    • Databay
      █ 7,000,000+ RESIDENTIAL PROXIES ✅ FROM 0.65$ / GB █

      By Databay · Posted

      This is a bump
    • L2 MOG
      [L2J] L2 MOG - PvP Worlds | Craft Retail

      By L2 MOG · Posted

      🏆 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
    • Kalami777
      [L2J] L2Gold Custom PVP

      By Kalami777 · Posted

      🚀 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]
    • NeoPacket0041
      HQ Photoshop | Verify Accs KYC, AML | Antiban 100% | PSD Tem

      By NeoPacket0041 · Posted

      "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
    • ZOUMHS
      PTS Vanganth Classic Interlude - P110

      By ZOUMHS · Posted

      ============================================================               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..