Jump to content

Recommended Posts

Posted

as i said before, use just one class. There, a static FastList<InetAddress> ips = new FastList<InetAddress>();

 

on cmd use

 

if(!YourEngineClass.ips.contains(player.getClient().getConnection().getInetAddress()) {

        YourEngineClass.ips.add(player.getClient().getConnection().getInetAddress());

        cmdstuff..

}

 

A List talking in java api terminology, is a Generic type, which implements the Collection interface

Posted

its a good idea, but dumb at the same time... like takhs7 said... the server would be restarting all the time b'coz ppl would find that interesting and they would restart it just for fun... but thats not all, they could exploit this option for example: bosses or something...

 

i've got takhs7's back for auto restarts =)

 

regardless, thank you for sharing!

Posted

on server start up

 

long minimunNonRestartTime = System.currentTimeMillis() + Config.MIN_RESTART_DELAY;

 

On cmd use:

 

if(System.currentTimeMillis() < YourEngineClass.minimunNonRestartTime) {

              player.sendMessage("Server restarted not much ago!");

              return false;

}

 

Fixed :)

 

Posted

1) You better  create a diff

2) You can handle all this engine within one class, avoiding creating new objects (1 objects is not problem, but avoid it its better than create)

3) Ppl cry when L2PcInstance is modified (cause update conflicts). Just make a list where all players who voted get inside.

On cmd use, if (list.contains(player)) return false;

 

for everything else, nice idea, really usefull

 

 

4) maybe make the vote number depend on how much online ppl...

 

anyway.. im rlly surprised you had the guts to do it without logging ips in the first place =P

Posted

Just merge it all into 2classes.

Some of those classes can be nested so it makes no sense.

The more classes you make the more problems you'll have ^^

  • 3 months later...
Posted

Nice dig-up. Another protection against stupid-restart from players, would be to introduced a derivative in the voting system. Votings can clear every 2 mins. Each 2 mins the system checks the votes/time, if that number is high, then it means that many people voted during that time. In other words it doesnt measure the "votes" in a long duration , but the votes/time. Usually votes/time will be high only when teh server starts lagging.

  • 8 months later...
Posted

Ποτε δεν ειχα φανταστει εναν τετοιο code (θεμα φαντασιας).

Απλα απιθανη δουλεια φιλε μου mossano.

Τελεια δουλεια οταν Κολαει ο σερβερ και δεν ειναι μεσα ο game master.

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

    • ## [1.5.1] - 2026-01-30   ### 🐛 Bug Fixes - **Top Voters**: Top voters list now loads correctly for inactive servers (previously showed "Server not found"). - **View Counter**: Server info page view count now records correctly for inactive servers.   ### 🔄 Improvements - **My Servers – Hide/Active**: The hide/active toggle now works correctly and is only shown when the server is approved (active) by an admin. Owner hide/show is separate from admin status. Toggling no longer causes a full page refresh. - **Accessibility**: Form fields across the site now have proper labels and IDs for screen readers and autofill — server info edit form, add server form, My Servers edit, Admin Panel (Email, Vote System, pricing, filters, logs), and related inputs.
    • 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:  
  • 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..