- 0
[HELP] UI Ideas
-
Posts
-
By Darafamboos · Posted
Tired of frantically switching between windows trying to find that specific Warlock who should be casting saves? Forgot which server you left your Warsmith on? This mod solves these problems! What it does: Turns the boring window title into an information panel: Server Name - Character Name [Class] Real-life examples: - ServerName - HardcoreFarm [Spoilerr] (who's been spoiling for 3 months already) - ServerName - ClericHelper [Buffer] (eternal buffer on standby) - ServerName - MainChar [Gladiator] (main character who's always AFK) Why you need this: For multiboxers - to avoid confusing where the DD is and where the healer is For the forgetful - if your memory is like a goldfish For streamers - viewers immediately see who's on screen For adults - when playing at work and need to quickly hide the window DLL only - no Interface files needed Installation (more complicated than making tea): 1. Download the DLL 2. Drop it into the System folder 3. Launch the client 4. Be amazed how you lived without this before! Purchase Conditions: Price: 100$ Payment Method: USDT. How to Buy: Contact me on Telegram: @kiselevwv for a quick response. I will answer all your questions and provide additional information if needed. I guarantee functionality at the moment of sale and prompt assistance with setup after purchase. -
I agree, l2damage crap to compare to l2java which was the father of pvp servers and till this days people playing there for good time.
-
📝 Registration — Account Registration Creating a new player account. Usually includes: login password password confirmation email Result: a new record is created in the accounts table (loginserver). 🔑 Change Password — Password Change The player changes the password knowing the current one. Required: current password new password new password confirmation Result: the password field is updated in the accounts table. ♻️ Password Recovery — Password Reset If the player forgot the password. Implementation only via email: the player enters their login, email the system sends an email with a link or code the player opens the link / enters the code sets a new password Result: the password is updated in the accounts table. All fields are validated (required, format, length, uniqueness, security checks). Price: 80$ and i can rewrite script for PTS server. Contacts: Telegram Discord
-
So dont plat that waste time&money server. GM promises pie in the sky, but does nothing. It's all about money, money, money. And wipe. SCAM server!
-
-
Topics

Question
dpbBryan
Hey everybody! I've started l2j development again (nice to see maybe the 2 people who will remember me).
Either way one of the next things I'm planning on implementing is permanent death (much like roguelikes).
Something I made a while ago was player graves. When players died all of their SP and Adena was removed from the player and attached to the grave. I was going to try to implement something like dark souls where if you die, your death site will have your remains and you have once chance to get back to it. If you died again with an active grave, the grave disappeared:
I've come back with this idea except I'm reworking it to add permanent death to players. So I've thought about:
1) Reporting the name of the player that deceased along with his/her level.
2) Reporting a list of items the player had on their possession when they died
Something like, this!
FYI the count for stackable items is corrected, little logic bug when working with the counts
You'll notice theres a 3 next to the Drac bow. I have a custom implemention of a grave item which'll store an item definition along with a quantity so I can neatly stack non-stackable items in a list. When they are returned from the grave it'll be converted into an L2ItemInstance:
public class _L2GraveItem { private int _count; private L2Item _item; public _L2GraveItem(int count, L2Item item) { _count = count; _item = item; } public int getCount() { return _count; } public L2Item getItem() { return _item; } public void setCount(int count) { this._count = count; } public L2ItemInstance removeStackableItem(int count) { if(count < 1 || count > this._count) return null; count -= this._count; return _createNewItemInstance(); } public L2ItemInstance removeItem() { _count--; return _createNewItemInstance(); } private L2ItemInstance _createNewItemInstance() { L2ItemInstance item = new L2ItemInstance( IdFactory.getInstance().getNextId(), this._item ); return item; } }I'll share because I love you guys, even though I don't know you. Theres obviously way more to it but it's too much to share.
Either way what I'm asking is ideas for creating an interface with the limited options of chat windows or multisells.
As of now I have a list I manually programmed in with a link between an item ID and it's icon on the client. I'm wondering what you guys might find better:
1) A chat window with a button allowing you to take the weapon (with condition checks of course such as if the item is still there and if you can hold it)
or
2) The grave will have a link to a generated unique multisell which will contain definitions of the items that exist on the grave when the player selects it. The grave will then instead just have a bunch of information about the player.
Whatca guys think? If you have other ideas say it :)
Also I'm using L2acis freemium build 270, thanks Tryskell and the l2acis team :P
4 answers to this question
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now