Jump to content

Recommended Posts

Posted (edited)
On 4/11/2024 at 5:02 PM, Starfire868686 said:

My ide was to doi in steps, first just the basic terrian, to all field. No staticmash etc. Next the texturing, so like this, but i don even know where to buy the stuff, how much is it etc.

 

well you can actually paint terrain heightmaps using the editor, if you just wan tto start with basic terrain texturing. u can use it to paint texturelayers aswell. but i recommend using other unreal editors for painting terrain textures since the one here on this forum tends to crash whenever it wants ^^

 

Just open the Editor and use a nearly empty example map to get map dimensions. Here I am using 15_22, since it has asingle water volume and a plain terrain texture only. perfect for demonstration:

 

Unbenannt1.png

 

Open terraininfo and move the terrain layer up the Z axis so it will stay slightly under water:

 

Unbenannt2.png Unbenannt3.png

 

Open Terrain Editing Tool und use the Paint method to raise terrain in order to create an island:

 

Unbenannt4.png

 

now that we have edited our ground heightmap texture in order to save it you must save the texture file using the texture viewer (before editing the ground u need to open it with the texturewiever). In our case it is T_15_22.utx. Just save it by klicking on File->Save. Overwrite the existing T_15_22.

 

Unbenannt5.png

 

Now by opening15_22.unr our ground will be under water again (bcs. we didnt save the .unr map file), but still have our edited raised ground part.

 

U can use this method to raise actual ingame ground parts on retail maps ^^ In order to actually paint the ground and the ground textures I would recommend using another UE. The one u will find here tends to crash and malfunction a lot. for example you cant flatten terrain using terrain brushes. Also texture painting doesnt work correctly aswell. sometimes u can paint and sometimes it does nothing.

 

To paint texture layers, select a texture in your "texture viewer" and use the "layer" tab

 

Unbenannt.png

 

To paint 3d grass choose a grass mesh type and use "decoration" tab tocreate decoration layers (eg. grass, little rocks and any kind of debris

 

Unbenannt.png

 

So by using another Editor you can edit and create plain textured terrain. Just check the dimensions of the original map to create a compatible terrain texture 😇

 

Note: This should not break your map's lightning since we are editing a texture only. Also note that raising the ground will not raise the position of static meshes that already exist on your map.

Edited by Finn
  • 3 months later...
  • 3 months later...
Posted
On 11/1/2024 at 5:23 AM, John Mouling said:

hi people!! how are you?. I tryed to open L2Editor and i have this error.

Assertion Failed  INT Size > 0
file xxxxx\mallocDebug.h

do you know what is it?

yes this is if the editor and map files do not match

  • 1 year later...
Posted
On 7/20/2024 at 10:33 PM, maneco said:

The grass disappear then o build all map, how to fix grass?

Смотрите в эти классы UnTerrain.cpp UnTerrain.h

  • 4 weeks later...
Posted

Please is anyone who can share the compiled version of the l2editor source for interlude? Because i run the !GenerateLibs.bat with the corrected code by CriticalError and then i try to build with the vs 2013 but i get errors again and again and when i try anyway to open or create something with the UnrealEd.exe then it closes automatically.

  • 2 weeks later...
Posted
On 3/22/2026 at 12:39 AM, paparas22 said:

Please is anyone who can share the compiled version of the l2editor source for interlude? Because i run the !GenerateLibs.bat with the corrected code by CriticalError and then i try to build with the vs 2013 but i get errors again and again and when i try anyway to open or create something with the UnrealEd.exe then it closes automatically.

 

Here you are: https://l2crypt.com/l2-tools/l2editor-source/

  • 2 months later...
Posted

Hi! I downloaded the Topic's files but i have the same issue as others with black gras. but i do not have Illumination at Server Info in F6. Someone could help me with it? im using L2C4 client and L2Julvius. Thank you all!

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

    • Added the protection module to the demo.   DDoS Guard Pro v2.0 is a system protection module for PlayMMO CMS designed to reduce the load on the website during HTTP floods, bot activity, suspicious frequent requests, and attacks on individual pages or API methods. Unlike simple global limiters, DDoS Guard Pro v2.0 supports flexible rules based on routes and HTTP methods. This allows you to block the entire site in a targeted manner, rather than blocking the entire site equally. You can set up protection for specific areas of the site, such as login, registration, APIs, administration, forms, and other sensitive areas. What is the purpose of the module? DDoS Guard Pro v2.0 helps protect your site from basic L7 attacks at the HTTP request level. The module is useful when your site receives: frequent requests from a single IP address; HTTP page floods; login or registration form flooding; automatic requests from bots; URL scanning; frequent API requests; suspicious activity spikes; load on individual CMS methods or pages. The module helps to reduce the load on PHP and CMS by limiting suspicious activity before it starts to create a serious load on the site. Main features Per-route and per-method Rate Limit In the new version, protection is configured not only globally, but also according to specific rules. You can set limits separately for: GET; POST; PUT; PATCH; DELETE; ALL. This allows you to flexibly protect different parts of your website. For example: for the login page, you can set a strict limit; for registration, you can set a separate limit; for the API, you can set a limit for reading and a limit for changing data; for regular website pages, you can set a soft limit or not set a limit at all. This approach reduces the risk of accidentally blocking regular users and makes the protection more accurate. Flexible rule system The module supports setting rules in the following format: METHODS|PATTERN|LIMIT|WINDOW|BURST_LIMIT|BURST_WINDOW|BLOCK_SECONDS|IDENTITY|NAME Example of rules: POST|*login*|10|60|5|10|600|ip|login_post POST|*register*|8|60|4|10|600|ip|register_post GET|*api*|300|60|80|10|120|ip|api_get PUT,PATCH,DELETE|*api*|80|60|20|10|300|ip|api_write This allows you to specify exactly: which HTTP methods to protect; which URLs or URL patterns to consider; how many requests are allowed; over what time period; what burst limit to use;  how many seconds to block the offender;  by which ID to count the limit;  what the rule is called. Burst protection against sharp spikes  In addition to the regular request limit, the module monitors sharp spikes of activity.  This is useful when a bot makes many requests in a few seconds. In this case, the protection can be activated faster, without waiting for the overall limit per minute.  Burst protection is especially useful for: authorization pages; registration; API; search; data submission forms; administrative sections. Support for different types of requests DDoS Guard Pro v2.0 works not only with POST requests. The module can control: GET — regular pages, API requests, search; POST — forms, login, registration, data submission; PUT — updating data via API; PATCH — partial data update; DELETE — data deletion; ALL — all methods at once. This makes the module suitable not only for regular sites, but also for CMS with API, personal accounts, game panels and administrative actions. Limit storage: Redis, APCu and file fallback In the new version, the module supports several options for storing temporary data. Available modes: Redis; APCu; file fallback. The auto mode tries to use the most suitable option: Redis; APCu; file storage as a fallback. Redis or APCu are suitable for more efficient operation, while the file storage is left as a fallback option for simple hosting environments that do not have additional extensions. JSONL logging The module records protection events in JSON Lines format. Logs are saved in the following file: storage/logs/ddos_guard.jsonl This format is more convenient than a regular text log, because each event is stored as a separate JSON record. The logs can record the following information: event time; IP address; HTTP method; URL; name of the triggered rule; reason for blocking; number of requests; action status; user-agent; protection mode. The JSONL format is convenient for analysis by external tools, log agents, and monitoring systems. Prometheus metrics DDoS Guard Pro v2.0 adds an endpoint for receiving metrics in Prometheus format. Endpoint: /?ddos_guard_metrics=TOKEN The token is set in the module settings. Metrics allow you to track: the number of processed requests; the number of rule activations; the number of blocks; activity by limits; protection events; module status. This allows you to connect monitoring and configure alerts so that the administrator can see when suspicious activity starts on the site. LOG ONLY mode The module has a LOG ONLY mode. In this mode, DDoS Guard Pro does not block users, but only records events and potential triggers in the log. This mode is recommended to be used after installation, in order to first see which rules are triggered, and only then to enable the real blocking.  This helps to avoid too strict limits and random blocking of regular users.  Support for Cloudflare and proxy  The module supports working behind Cloudflare or another reverse proxy.  With proper configuration, it is possible to take into account the real IP of the user, and not the IP of the proxy server.  This is important for sites that use:  Cloudflare; nginx reverse proxy; load balancers; CDN; hosting proxy protection. Nginx-recommendations DDoS Guard Pro v2.0 contains an example nginx-config: modules/ddos_guard/nginx-ddos-guard-example.conf This allows you to use the module as an additional application layer of protection, and to move the main coarse limits to the nginx level. Recommended protection scheme: Cloudflare / nginx / firewall → DDoS Guard Pro → PlayMMO CMS This approach is more correct than trying to solve all problems only at the PHP level.
  • 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..