Jump to content

Recommended Posts

Posted

You need to do more with instances.

 

As I checked the code, there is no checks/functions for doors. Doors are also part of L2Object, so in case of any "event" including doors there would be a mess.

 

Another shit is you need to connect the instance with the IdFactory, in order to be able to automaticly create events either solo or whatever you need to automaticly get non-exist dimensionId's.

 

Good luck ^_^

 

Well in general this dimension system is pretty basic in a sense that its made for simple things. Altho im pretty sure as the pack progresses it will be easier to remake/extend such features.

 

Changeset 23:

 

javolution moved back.

some file organization.

 

https://xp-dev.com/trac/l2jpes/changeset/22/l2jpes

Posted

Well in general this dimension system is pretty basic in a sense that its made for simple things. Altho im pretty sure as the pack progresses it will be easier to remake/extend such features.

 

https://xp-dev.com/trac/l2jpes/changeset/22/l2jpes

 

Then what's the point in commiting it if it's useless for now?

Posted

Then what's the point in commiting it if it's useless for now?

It is nowhere near useless, it can be used to for multiple farm areas, even pvp areas. Do they have to include doors?

Posted

Its not my work so ask Pauler tho i dont think its useless.

It's useless as it is, you can only change dimensions manualy or use pre-sets which means limited "space", and of course without any doors included.

 

 

Let's take a case of:

 

Solo farm event. Each player can get in and we have only 1 zone to use. 100 players join, so we need to generate 100 different ids. Until here it can be done on the event script. but what happens if someone has 2 events running at the same time? A mess. That's why you need to have connected generator for dimension ids. I think it's pointless using New-old stuff, since this system already exist on newer chronicles and it's been coded on L2j, tested and proven.

 

http://trac.l2jserver.com/changeset/2701

http://trac.l2jserver.com/changeset/2829

http://trac.l2jserver.com/changeset/2728

http://trac.l2jserver.com/changeset/3169

 

and so..

Posted

It's useless as it is, you can only change dimensions manualy or use pre-sets which means limited "space", and of course without any doors included.

 

 

Let's take a case of:

 

Solo farm event. Each player can get in and we have only 1 zone to use. 100 players join, so we need to generate 100 different ids. Until here it can be done on the event script. but what happens if someone has 2 events running at the same time? A mess. That's why you need to have connected generator for dimension ids. I think it's pointless using New-old stuff, since this system already exist on newer chronicles and it's been coded on L2j, tested and proven.

 

http://trac.l2jserver.com/changeset/2701

http://trac.l2jserver.com/changeset/2829

http://trac.l2jserver.com/changeset/2728

http://trac.l2jserver.com/changeset/3169

 

and so..

 

That would be a problem, if these two completetly different events are supposed to take place in the same area at the same. Even if that happens, a static list which will contain the used dimensions will easily solve it.

Posted

That would be a problem, if these two completetly different events are supposed to take place in the same area at the same. Even if that happens, a static list which will contain the used dimensions will easily solve it.

 

Also there aren't any checks for items.. Any dropped items will be visible to all dimensions.. Just implement L2j current system..

 

Seriously is this what anarchy was selling? Damn...

Posted

It's useless as it is, you can only change dimensions manualy or use pre-sets which means limited "space", and of course without any doors included.

 

 

Let's take a case of:

 

Solo farm event. Each player can get in and we have only 1 zone to use. 100 players join, so we need to generate 100 different ids. Until here it can be done on the event script. but what happens if someone has 2 events running at the same time? A mess. That's why you need to have connected generator for dimension ids. I think it's pointless using New-old stuff, since this system already exist on newer chronicles and it's been coded on L2j, tested and proven.

 

http://trac.l2jserver.com/changeset/2701

http://trac.l2jserver.com/changeset/2829

http://trac.l2jserver.com/changeset/2728

http://trac.l2jserver.com/changeset/3169

 

and so..

 

Appreciate the search, tho in my opinion its better to make a new system since we will have a lot of changes imvolving the workaround of the pack. This is a basic system that works thats all that is to it now. In the future ofc theres a possibility to extend/remake it, but thats the future atm i discover issues after issues after issues that need to get fixed asap.

 

Also there aren't any checks for items.. Any dropped items will be visible to all dimensions.. Just implement L2j current system..

 

Seriously is this what anarchy was selling? Damn...

 

Thanks for pointing these out.

Posted

Also there aren't any checks for items.. Any dropped items will be visible to all dimensions.. Just implement L2j current system..

 

Seriously is this what anarchy was selling? Damn...

This isn't Anarchy's one, even though I believe it was pretty close.

Posted

There are a lot things to do in order to make this system usable, remember you need to get rid of every L2Object, not only NPC/PC.

 

I suggested using L2j current because it's tested and proven, but you've made your decision.

 

Btw, you have to agree that atm it's useless..

Posted

There are a lot things to do in order to make this system usable, remember you need to get rid of every L2Object, not only NPC/PC.

 

I suggested using L2j current because it's tested and proven, but you've made your decision.

 

Btw, you have to agree that atm it's useless..

 

Its not useless, theres just a lack of function.

Posted

By the way, door extends l2character, which extends l2object. I believe it is working pretty fine with doors, too.

Posted

Then how to open close them on specified instances? ^_^

 

Tbh you rarely use doors in custom instances, looking at it i agree with you about many issues and lacking features the engine have but give it time, thats an experiment still ofc after testing and testing ohh and more testing it will be better. As i said before as the pack progresses we will have a much better chance reworking things like that and doing it in the best possible way. Till than patienace or if you really insist you can help us with some codes.

Guest
This topic is now closed to further replies.



  • Posts

    • cRazy??? If i just say good job its not even fair....
    • τι εκανες εκει παλι ρε τρελάρα; 🤣   welcome back mate, happy seeing you online again, well thats beyond l2 needs for sure and It’s rare to see anyone pushing Interlude this far technically anymore without trying to monetize it. definitely interested in seeing the source whenever you're ready to share it! keep it up!
    • your only choice brother cmon https://www.l2jsunrise.com/
    • Hello everyone  How are you all doing? I'd like to share with the community an open-source project I've been working on intensely: the **L2 Phantom AI Manager**. Tired of those static bots that just stand still in the city or sink into the map because of Geodata? Me too! That's why I developed a modular Phantom system with real Artificial Intelligence, initially designed for **L2J Mobius Essence (RoseVain)**, but which can be adapted to other chronicles. Main Features Modular architecture: the system is split into focused files such as PhantomAI, PhantomEngine, PhantomFactory, PhantomEquipment, PhantomHuntingSpots, PhantomGeo, PhantomMenu, and more. Automatic creation: create 10 or 50 phantoms from the menu or commands. XML persistence: automatically created phantoms are saved into PhantomPlayers.xml, so they keep loading after server restarts. Batch startup: .pstart and Start 10 load only 10 phantoms at a time. Batch disconnect: disconnect 10 active phantoms without shutting down the whole system. Origin towns: new phantoms spawn using PlayerTemplate.getCreationPoint(), respecting race and class. Geodata-safe spawning: spawn points use NPC-like coordinate validation to avoid under-map or floating characters. Real datapack spots: reads data/stats/npcs and data/spawns to build level-based hunting locations. Bad target filtering: ignores Training Dummy, tutorial objects, chests, and fake farm targets. Smart relocation: if a phantom cannot find useful mobs, it relocates to another spot for its level. Level goals: phantoms receive leveling goals, return to town, recover resources, and go back to farming. Mage MP rest mode: mages rest until MP is recovered; in PvP they try to escape when out of mana. Skills and buffs: phantoms try to use offensive skills and self buffs such as Might, Shield, Focus, Haste, Empower, Acumen, Wind Walk, Chant, Song, and Dance. Varied gear packs: gear packs by grade for mages and fighters, with multiple variants to avoid visual clones. Automatic shots: randomized Soulshot and Spiritshot restocking by class and grade. Inventory cleanup: unnecessary items are removed automatically while preserving Adena, shots, and equipped gear. PvP and PK behavior: some phantoms are aggressive, may become PK, and attacked phantoms try to defend themselves. Optional AI chat: optional Google Gemini integration for short social replies. TXT logs: the menu displays log state and can enable/disable logging. GM Menu Use .pmenu to open the control panel. Current options: Start 10 Disconnect 10 Create 10 Create 50 Reload XML Stop All Enable Log / Disable Log The menu also shows: active phantom count; XML ID count; current TXT log state. Commands .pmenu - opens the control panel. .pstart - starts 10 phantoms from XML. .pstop - removes all active phantoms. .pstop10 - disconnects 10 active phantoms. .pload - reloads PhantomPlayers.xml. .pcreate 10 - creates, starts, and saves 10 phantoms to XML. .pcreate 50 - creates, starts, and saves 50 phantoms to XML. .pm Name Message - sends a private message to a phantom. .pdebug - toggles TXT logging. Logs Logs are created in the GameServer log/ folder: log/PhantomManager.txt - global historical log. log/PhantomManager-yyyyMMdd-HHmmss.txt - separate log for each session. Useful logged events include: new level goals; travel to hunting spots; town rest; mob attacks; PvP defense; shot restocking; inventory cleanup; AI exceptions with stacktrace. Main Files PhantomManager.java - commands, logs, and bootstrap. PhantomEngine.java - start, stop, spawn, respawn, batches, and AI loop. PhantomAI.java - farm, PvP, PK, rest, targeting, and movement decisions. PhantomConfig.java - routes, gear, shots, and XML persistence. PhantomFactory.java - automatic character creation. PhantomEquipment.java - buffs, progression, shots, and inventory cleanup. PhantomHuntingSpots.java - real datapack NPC/spawn loader. PhantomGeo.java - geodata-safe coordinate handling. PhantomState.java - temporary phantom memory. PhantomMenu.java - GM HTML panel. PhantomBypass.java - menu button handling. PhantomChat.java - messages and optional Gemini integration. Copy custom/PhantomManager into: dist/game/data/scripts/custom/PhantomManager/ Place PhantomPlayers.xml in: game/config/Custom/PhantomPlayers.xml Compile scripts or restart the GameServer. Use .pmenu to create, start, and manage phantoms. https://github.com/miacodeweb/L2-Phantom-AI
  • 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..