Jump to content
  • 0

Question

Posted (edited)

Hello.

 

So I was messing around with ExServerPrimitive packet on aCis and I was trying to draw a circle around a capture point (dominion event).

 

But I've noticed some very strange behaviour of this packet. From my understanding, each primitive is saved in the client under a unique (?) name, like an object id. In addition to that, you need to actually send an empty packet of the name you are modifying if you wish to clear the packet in the client (or exit and open up again).

 

However, if for example I log in 2 clients from the same PC, only the first will get the primitives drawing (even tho the server sends them correctly, I checked).

EDIT: Even stranger, some times it does show it some times it doesn't. I checked for bugs in the code but there are none.

I haven't tried to send a diffrent names for different characters to see if they will be drawn, but I doubt it.

 

So I was wondering if someone knows if the client has any limitations or where is the data from the primitives stored.

Edited by An4rchy

3 answers to this question

Recommended Posts

  • 1
Posted (edited)
On 3/17/2021 at 4:19 PM, An4rchy said:

However, if for example I log in 2 clients from the same PC, only the first will get the primitives drawing (even tho the server sends them correctly, I checked).

EDIT: Even stranger, some times it does show it some times it doesn't. I checked for bugs in the code but there are none.

 

So here is what happens and trust me it took me a fuck ton of time to figure this out when I originally used it in L2BattleRoyale. This is also unique to Interlude and I don't think in happens in future chronicles which means they fixed it. 

 

If both players spawned near the area where the initial creation of the packet happens then they can both see it fine because I am assuming you are using current location as the ExServerPrimitive initial center point. However, if you spawned away from where the packet is created then you cannot see it.

 

In order to fix that you have to store the original Location (x, y, z) of the player when they EnterWorld.

When you create an ExServerPrimitive package you need to provide a name, an x, a y and a z. These values NEED to be the X of the spawn location and the Y of the spawn location. The Z can be -65535 to ensure that the icon will be below the ground.

 

Once you do that this will stop happening.

 

Here is how I handle it in Autobots:

Create Circle Packet method

Using EnterWorld location to initialize the package

Storing the EnterWorld location

Edited by Elfocrash
  • 0
Posted

In High Five you can even create 2.500 lines and it won't have any trouble. In Interlude after few lines client will receive severe delay as if you're trying move while connected to a 0.0005 KB's Dual core 512 ram VPS in Pakistan.

 

In an Interlude server i was working months ago, sometimes it was visible some other it was not (it was like up to client's mood). I don't remember if eventually we gave up on that packet or we did as you wrote different name for each player using his object Id as ExServerPrimitive's name.

 

Still be aware of the lines keep it low "quality". 

  • 0
Posted

Thanks for the insight.

 

I was curious as to why aCis stores enter world location.

 

I got it fixed the way you told me only not knowing it was a bug that required enter world location, just by following what Tryskell did on geo debug.

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