Jump to content

Recommended Posts

Posted

And? works on Freya?

sorry i didn't .. something appeared and i couldn't check it

 

anyway

 

WHY IS THIS PEOPLE STILL POSTING HERE WHEN LINK DOESN'T WORK ? xD!..

 

SOMEBODY CLOSE THIS TOPIC .. AS I SAID LINK IS NOT WORKING

  • 2 weeks later...
  • 4 months later...
Posted

i didnt work over it for so long, but its an abstract engine, it can be coded for any chornicle.

About what event contains, it only comes with tvt to test it. The goal of this share isnt to give many events, but to decrease the time and work needed to code one

  • 3 months later...
Posted

This diff contains a Event Engine: An engine capable to execute datapack-sided scripts to run a event. Those dp-side script will extends, inherit and override when needed basic methods needed for most kind of events, so it makes you able to make an event just in the same way as a quest.

All events are fully configurable ingame, with a full of tools admin panel (Data can be saved manually, but is unneeded, it will be saved automatically at server shut down).

The engine supports events with many event rounds and teams (All you have to do is add them ingame)

It also contains a vote system, ppl will be able to vote which event will be the next one comming up (Can be disabled of course)

 

The code is very young (i just tested all administration side and the event i translated (TvT, which can be found at data/scripts/events/Team_vs_Team/)). I mostly share for those who wanna help me on testing the engine. All ppl who test it can tell me what it lacks, what does not work and what throw catched exceptions or errors.

I dont recommend to use it in any live server for now.

 

Code side, the code is a little messy (will reorganize and go to the optimisation side when ill sure  100% that the engine is working fine)

 

Is coded for l2jserver, last revision of gracia epilogue branch

http://www.mediafire.com/?5514r3dwq7v3qjh

 

thank you

  • 2 weeks later...
Posted

i got difficulties in adapting it to high five there is many methods that not working in h5 like isInEvent()

 

L2JServer alredy have it.

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

    • <dailyReward days="28" autoOpen="true" minimumOnlineTimeSeconds="30" oneRewardPerIP="true" resetIfMissDay="true">   For now, I have these settings in the XML—this is the V1 version I created, though I plan to make further improvements over time. Of course, I’ll also add more protections—MAC, HWID, and perhaps others like account-based restrictions—to make it more secure. We can also implement non-tradable items to further enhance the system's security. I’ll keep posting updates and refining both the system and the interface. I might make a video tomorrow; if you look at the top, you'll see the "auto-open" feature can be toggled on or off, allowing users to rely solely on the `.daily` command. Cheers! Note: If I sell it in this state, I’ll provide support and roll out updates to users. I’m not forcing anyone to buy anything; I’d even provide the patch files so that anyone with the necessary skills can add features, modify it, or improve it further.
    • If the problem is that the target is lost, the action of aiming at another character, upon losing collision, does not allow aiming.   This one works as it should, allowing you to target characters
    • MICROTEXT AND WATERMARKS BREAK MOST RENDERINGS Microtext and watermarks aren’t just small decorative details. They are one of the most common reasons a document fails verification, even when it looks decent at first glance. The issue is that these elements are almost impossible to reproduce “by eye.” Microtext requires precise geometry and legibility at a very small size, while a watermark needs the correct density, transparency, and accurate placement relative to other security features. Any deviation becomes obvious during detailed inspection. ▪ What’s most often done wrong: - microtext is drawn too thick or blurry - the watermark is made either too visible or almost invisible - the positioning between microtext and watermark is ignored - the original printing technology isn’t taken into account when choosing density and shape - The stronger the document’s security features, the less room there is for approximation. What matters here isn’t visual similarity, but accurate reproduction of the original technical characteristics. If your document contains microtext and watermarks, this is always an area that requires extra attention. Write to us in DMs. We’ll review your case and point out exactly which details need the highest precision during rendering. › TG: @mustang_service_ms ( https:// t.me/ mustang_service_ms ) › Channel: Mustang Service ( https:// t.me/ +JPpJCETg-xM1NjNl ) #drawing #microtext #photoshop #editing #watermarks
    • GoldRush launches tomorrow! July 18 16:00 GMT+3 Europe / International Register your account in the website, connect wallet and be ready to dominate!
  • 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..