Jump to content

Recommended Posts

Posted

logoeyr.png

 

I ask everyone to use the correct section of the PhoenixEngine site for bug reports instead of pming me! Thanks!

 

 

A new unique event engine for popular Lineage 2 emulator L2J. Coded by two Java developers Rizel & hNoke.

 

The goal of this project is to make a bug-free java based event engine which contains all of the current/new events and be compatible with all the popular L2 server emulators.

 

The engine is fully automatic (with Vote system, which allows players to choose next event) and contains complete ingame administration, including creating new maps, editing configs for each events or maps, scheduling new events, disabling them, etc. It has two different event types: Main events - global events running for all players on the server, and Mini events - running for single players or parties.

 

- Manager - a NPC which handles both voting and registrating for players and also shows informations about the currently running event.

- Scorebar - Every event shows a text scorebar to all the players inside, with the time left, score and more!

- Scheme Buffer - Players can set up their buff schemes for all their characters/subclasses and on the event respawn/teleport, those buffs will be automatically applied on them. The ammount of buffs and allowed buff skill IDs are configurable.

- Statistics - You can check all the players overall event statistics and also statistics for individual event types.

- Reward System - Configurable rewards for all events and all possible places.

- Pop-up vote window - You can enable a pop-up vote window whichs shows at a certain time in the voting phase for every player.

- Automatic party creation - In team events (like TvT) the engine create parties automaticly.

 

sshotb.th.png    stat1.th.jpg    stat2.th.jpg    ss2m.th.jpg

 

The free version is no longer available.

 

More info about the engine/event list can be found at

www.phoenix-engine.net

Posted

"I ask everyone to use the correct section of the PhoenixEngine site for bug reports instead of pming me! Thanks!"

 

some moderator pls delete his post. and instead of screenshots send the console log. BUT IN THE PHOENIX SITE not here

Posted

Sticky?

Why?

Anyway good luck

 

Because it's the only unique share made the last 3 or 4 months in this section, from 2 skilled developers.

Although, I'd like to ask the team to put a download link here.

Guest
This topic is now closed to further replies.



  • Posts

    • ⚡ Fast order delivery is active 24/7! Upgrade your personal Gmail to Gemini Pro with full 2TB storage and premium Google One features today.
    • Update M54: Global HP/MP/CP consumable handling expanded beyond combat-only usage. Offensive mage idle recovery with learned skill Battle Heal. Spellhowler/Storm Screamer prioritizes Hurricane, using Vampiric Claw mostly below 90% HP. Major structural refactor initialized: Added category/class organization such as Archer, Dagger, Tank, Mage, Healer, Support and Specialized class files. Further structural cleanup. Extracted combat memory/state and more class-policy logic from the main controller. Added global stuck/inactivity watchdog for bots blocked by terrain/geodata. Added unreachable dropped ground-item timeout/temporary blacklist. Reworked Necromancer/Soultaker PvP: Dominator level 78+ maintains learned Arcane Power toggle on. Overlord/Dominator level 44+ maintains learned Soul Guard toggle automatically. Stability/scalability update: Bot controller ticks staggered instead of all starting in the same phase: Same 350 ms update rate retained Reduces simultaneous AI workload bursts. Removed the old manual aggressive-monster EVT_AGGRESSION bridge. Phantoms now use native Lucera setActive() behavior so monsters aggro them naturally. Reduced unnecessary NPC scans and native AI event pressure. Added saved-bot equipment overrides using a separate database table:         lucera_autobots_items Existing lucera_autobots remains the main saved-bot identity/state table. Equipment rows are linked to saved bots through bot_id. Added optional convenience view to show bot name together with equipment overrides:         lucera_autobots_items_view Added editable equipment slots in columns: Weapon Shield Helmet Chest Legs Gloves Boots Necklace Left/Right Earrings Left/Right Rings Equipment override values: 0 = use normal class/level profile item -1 = force slot empty >0 = equip that Item ID Custom equipment works only for saved database bots. Default class/level equipment profiles remain unchanged. Supports custom equipment from No Grade to S Grade, regardless of the bot's current level. Added validation for invalid item IDs and incompatible equipment slots. Added handling for: Two-handed weapons vs shields Full-body armor vs separate leggings Added all-grade Soulshots and Spiritshots to bot inventory/replenishment so custom lower-grade weapons still use the correct shots. Mage profiles that already use Blessed Spiritshots keep that behavior with all relevant grades available. First save the bot normally so it exists in table:         lucera_autobots Then open:         lucera_autobots_items Find the row with the same bot_id and edit only the equipment slots you want. Example: weapon_id = 6608 shield_id = -1 helmet_id = 0 chest_id = 0 legs_id = 0 gloves_id = 0 boots_id = 0 This means: weapon_id 6608 → custom weapon shield_id -1 → no shield all 0 values → keep normal default profile equipment After editing the DB, despawn and respawn the saved bot so M54 reloads its equipment overrides. Do not edit bot_id. Use it only to identify which saved bot the equipment row belongs to.   DOWNLOAD
    • It will be multi client so it will detect the client from the files and adapt the packets and asset loading. I am aiming for C4 and H5 after IL
    • this is just to simplify your life, time, and can be done for free by yourself just watch some tutorials, in case you don't wanna waste time check it out!   https://l2getwork.art   https://l2getwork.art/showcase.html  
  • 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..