Jump to content

Recommended Posts

Posted (edited)

Hello dear Moderators, I would like to know @Designatix why you are not give warning points or ban - chatban to @xxdem ?

His general behavior to all members / posts is bad with offensive language like (fuck, trash, delete your server, trashcan etc.).

Also spamming in all posts*

The moderators are deleting his flame comments all the time but without any warning - ban - chat ban, why is that?.

 

Thanks for your time

Edited by SQL Developer
Posted
3 minutes ago, SQL Developer said:

Hello dear Moderators, I would like to know @Designatix why you are not give warning points or ban - chatban to @xxdem ?

His general behavior to all members / posts is bad with offensive language like (fuck, trash, delete your server, trashcan etc.).

Also spamming in all posts*

The moderators are deleting his flame comments all the time but without any warning - ban - chat ban, why is that?.

 

Thanks for your time

He simply don't care. He will make new acc and join. Maxcheater is 0 to him. He just spend his time.

Posted

@Designatix I was too fast i guess, sorry and thanks for your fast support.

 

@Kara` Well my personal point of view is, if a new member will see his flame post activity and will see that this guy is a member on MXC since 2015 (without a ban) will say "this forum haven't rules".

 

I mean you cant request from other members to be polite and follow the rules while this guy is a member without ban since 2015.

 

Anyway i guess you can lock this

Posted
13 minutes ago, Kara` said:

He simply don't care. He will make new acc and join. Maxcheater is 0 to him. He just spend his time.

isnt it your job? ;D 

Posted
10 minutes ago, SQL Developer said:

I mean you cant request from other members to be polite and follow the rules while this guy is a member without ban since 2015.

Actually his main account is banned. This xxdem is his alt.

 

In addition, ban > new acc > ban > new acc... Look on Kara :D

Posted

My opinion about new accounts > new accounts > new accounts...

Update the forum terms of use etc. and type:

In case of permanent ban, the member will lose any right to his topics and the administrator / moderators will have all the right to manage your topics.

 

Then you ban his profile (bye bye feedback's and reputation), junk all his market / server / project topics. (keep all the "useful" stuff that he shared on forum because he will accept the terms of use) and then lets see if he will flame again

 

Posted
18 minutes ago, SQL Developer said:

My opinion about new accounts > new accounts > new accounts...

Update the forum terms of use etc. and type:

In case of permanent ban, the member will lose any right to his topics and the administrator / moderators will have all the right to manage your topics.

 

Then you ban his profile (bye bye feedback's and reputation), junk all his market / server / project topics. (keep all the "useful" stuff that he shared on forum because he will accept the terms of use) and then lets see if he will flame again

 

First of all, we cannot controll banned users making new accounts. We do what you mentioned junking topics/posts etc from banned members but that doesn't solve anything.

And secondly and most important, there are way more serious reasons of bans than flaming, xdem, kara and some other users are banned for flaming, but there are scammers that scam every day and we cannot do a lot of things about it, there are users bulling other members and they're doing it by following rules (doesn't scam, flame, etc) and way more reasons that our forum is what it is right now with zero new shares and zero creativity.

 

Some users flame or act childish but tbh isn't so much harm than other users bulling and scamming people here.

The fact that xdem will write on l2prideful's topics that the server is trash it won't harm his server AT ALL.

But users saying the code someone shared is crap, the npc he made is ugly af, etc will harm the people trying to crete new things and share them with everyone.

 

The point is, we're at a point that we (the staffers) cannot do a lot about these situations, if members won't change their attitude baning them all will end up worst than having them here and won't change a thing.

If you remember the old days when tons of people got banned for stupid reasons such as staffer in a similar forum, spaming, flaming, etc (ofc i'm not speaking about scammers) ended up making a dead forum because these were the people that would bring activity into the forum. Now we're trying to bring activity using other ways like hidden content and people still bitching and not following rules at all but no one cares about that, you only care about a harmless post of a guy saying trash a server.

Posted
2 minutes ago, baksteen said:

You could make a group that can bypass moderation, then change all current members to the group that bypasses moderation, then set the forums to moderate messages, then when new members post messages you can approve the messages and change the member's group to the group that can bypass moderation, if their posts are not abusive. Then if a member tries to post "bad" posts you can set their group back to the moderated group. If they just sign up for another membership then they will be back in the moderated message sequence again. Over the years I did this with previous message board software and now use this idea with invisionboard software. I hope all goes well for you!

Yeah this can be done too but we will need like 5 gmods accepting new posts :p 

Posted
6 hours ago, SweeTs said:

Actually his main account is banned. This xxdem is his alt.

 

In addition, ban > new acc > ban > new acc... Look on Kara :D

 

At least i don't open server and use npc name "group 1"

Guest
This topic is now closed to further replies.


  • 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.
    • 🚀 L2AQUILA — GRAND OPENING TOMORROW! Lineage 2 Gracia Final — Like L2 Pride, but fresh. The server you've been waiting for opens tomorrow, Saturday 19/09, 16:00 (Greek time) — No Wipe · 24/7 · Anti-DDoS. ⚔️ What's inside: • EXP 9300x · SP 3000x · Adena 5500x · High drop • Max enchant +20 · Safe +3 · 24 buffs / 3 debuffs • 20 free Custom Coins for every new player on day one! • Custom farming zones (Cave of Trials, Cemetery, Ruins of Despair + more) • PvP Events · Olympiads · Offline Trading · Weddings · Balanced classes • Starter + Dynasty shops in every town — playable from minute one 📥 Download: Client + Patch at https://l2aquila.com/index.html 💬 Discord: discord.gg/5ZyBRvG4k · Facebook: facebook.com/l2aquila Be there at opening hour — bring your squad. See you at the Grand Opening! 🔥
  • 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..