Jump to content
  • 0

Error in loginserverthread


Question

Posted

Hi ! im having this error, when it happens, the login goes offline... its weird because te gameserver and loginserver keeps going without errors. but you cannot connect again until i restart both.  i looked into the code and i didnt found nothing "rare" . Im using acis 399 . this error occurs randomly  and its very annoying because the server goes off.. any suggestions ?
 

problema.jpg

5 answers to this question

Recommended Posts

  • 0
Posted (edited)

Provide the associated lines from GameClient, it's definitively not vanilla 399 (first line is a bracket, second error line is javadoc).

 

 

Edited by Tryskell
  • 0
Posted
40 minutes ago, Tryskell said:

Provide the associated lines from GameClient, it's definitively not vanilla 399 (first line is a bracket, second error line is javadoc).

 

 

 FIRST LINE (GAMECLIENT 686)   :
public void close(L2GameServerPacket gsp)
    {
        
        getConnection().close(gsp);
    }
SECOND LINE (GAMECLIENT 707) :
    public synchronized void closeNow()
    {
        // Prevent packets execution.
        _isDetached = true;
        
        
        
        close(ServerClose.STATIC_PACKET);
        
        // Cancel cleanup task, if running.
        if (_cleanupTask != null)
        {
            _cleanupTask.cancel(true);
            _cleanupTask = null;
        }
        
        // Instant cleaning.
        ThreadPool.schedule(new CleanupTask(), 0);
    }

THIRD LINE (LOGINSERVERTHREAD 335) ILL NOT POST THE FULL CODE ITS VERY LARGE..
                        case 0x04:
                            final KickPlayer kp = new KickPlayer(decrypt);
                            kickPlayer(kp.getAccount());
                            break;

FOURTH LINE (LOGINSERVERTHREAD 239)
    public void kickPlayer(String account)
    {
        final GameClient client = _clients.get(account);
        if (client != null)
            client.closeNow();
    }


I have an offline trade mod... i wonder if the problem is that ?

Guest
This topic is now closed to further replies.


  • Posts

    • ## SuperPoint Editor   SuperPoint Editor is a practical visual editor for Lineage II PTS 'SuperPoint.bin' files. It is built for people who need to inspect, fix, rebuild, and draw server routes without digging through binary data by hand.   ### What You Can Do   - Open and edit 'SuperPoint.bin' files. - Export BIN data into a readable TXT format. - Save edited data back into a valid BIN file. - Validate routes before saving. - Work with SuperPoint routes, points, directed connections, and path records in tables. - Add, duplicate, delete, and reorder points. - Create direct and reverse connections between route points. - Automatically generate connections between neighboring points. - Edit raw point coordinates: 'X', 'Y', 'Z', 'Index', and 'Delay'. - Keep route names and internal route data organized. - Use either English or Ukrainian interface language.   ### C4 Server Support   Some C4 servers have 'SuperPoint.bin', but do not have 'superpointinfo.txt' in scripts. The editor supports this case directly. When 'superpointinfo.txt' is not found near the BIN file, the editor can open the BIN in C4 mode. In this mode, 'Fstring ID' is disabled because that value belongs to 'superpointinfo.txt', not to the BIN itself. The editor will not generate or modify 'superpointinfo.txt' while working in this mode. This keeps C4 data clean and avoids creating script files that the server does not actually use.   ### superpointinfo.txt Support   For chronicles that do use 'superpointinfo.txt', the editor can load and synchronize it together with the BIN data. When saving, the editor updates route nodes and coordinates while preserving existing metadata such as: - 'npc_name' - 'move_type' - 'fstring_index' - 'social_number' - 'delay' New nodes are generated with safe default values, so existing script metadata is not accidentally wiped.   ### Geodata Tools   The editor can also open converted geodata '.dat' files and display them as a map. This makes route editing much more visual. You can: - Load geodata and inspect the terrain by layer. - Zoom and pan around the map. - Create a new SuperPoint directly from a map cell. - Draw a route by clicking on the geodata. - Drag existing points to new positions. - Automatically snap 'X/Y' to the selected geo cell. - Use the selected geodata layer to fill the point 'Z'. - See all routes on the map or focus only on the selected one. This is especially useful when building new NPC movement paths or correcting bad route coordinates.   ### Connections and Paths   SuperPoint connections are directional. A connection from point '3' to point '2' is not the same as a connection from point '2' to point '3'. The editor makes this explicit by separating: - route points, - directed connections, - and the actual path records used by each connection. For simple cases, it can create direct path records automatically. For more complex movement, you can edit the path points manually. ### Built for Safe Editing The editor includes validation before saving, so common structural problems can be caught before a broken BIN is produced. It also verifies rebuilt BIN files through the converter engine. The goal is simple: edit quickly, but do not silently damage server data.   ### Unknown Field   This small 'Unknown' field is part of the original BIN structure. Most official-looking files keep it as '0', and for regular route editing there is usually no reason to change it. The editor exposes it so nothing from the BIN is hidden or lost. If you do not know exactly what your server uses it for, keep it at '0'. Download
    • NpcGrp não salva no interlúdio e da crítico quando coloca ele no cliente, já testei ele antes.
  • 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..