Jump to content
  • 0

Question

Posted

Hello, i using this TvT Event on aCis re 362.

http://pastebin.com/GWcRXUXj

 

When i press SHIFT button i can target another players which are not participated at event....and players which don't participated at event can target with SHIFT button players wich are participated at event.

How i can fix it? :)

Recommended Posts

  • 0
Posted

What you mean about this?

Do you have a better way?

 

http://imgur.com/a/jgLvX

Ok, the formatting probably confuses you, there is the formatted method:

/**
* Starts the TvTEvent fight<br>
* 1. Set state EventState.STARTING<br>
* 2. Close doors specified in configs<br>
* 3. Abort if not enought participants(return false)<br>
* 4. Set state EventState.STARTED<br>
* 5. Teleport all participants to team spot<br><br>
*
* @return boolean<br>
*/
public static boolean startFight()
{
    setState(EventState.STARTING);

    // not enought participants
    if (_teams[0].getParticipatedPlayerCount() < Config.TVT_EVENT_MIN_PLAYERS_IN_TEAMS || _teams[1].getParticipatedPlayerCount() < Config.TVT_EVENT_MIN_PLAYERS_IN_TEAMS)
    {
        setState(EventState.INACTIVE);
        _teams[0].cleanMe();
        _teams[1].cleanMe();
        return false;
    }

    closeDoors();
    setState(EventState.STARTED); // set state to STARTED here, so TvTEventTeleporter know to teleport to team spot

    // teleport all participants to there team spot
    for (TvTEventTeam team : _teams)
    {
        for (String playerName : team.getParticipatedPlayerNames())
        {
            L2PcInstance playerInstance = team.getParticipatedPlayers().get(playerName);

            if (playerInstance == null)
                continue;

            // implements Runnable and starts itself in constructor
            new TvTEventTeleporter(playerInstance, team.getCoordinates(), false, false);
        }
    }

    return true;
}

After applying your patch, the code should look something like this:

/**
* Starts the TvTEvent fight<br>
* 1. Set state EventState.STARTING<br>
* 2. Close doors specified in configs<br>
* 3. Abort if not enought participants(return false)<br>
* 4. Set state EventState.STARTED<br>
* 5. Teleport all participants to team spot<br><br>
*
* @return boolean<br>
*/
public static boolean startFight()
{
    setState(EventState.STARTING);

    // not enought participants
    if (_teams[0].getParticipatedPlayerCount() < Config.TVT_EVENT_MIN_PLAYERS_IN_TEAMS || _teams[1].getParticipatedPlayerCount() < Config.TVT_EVENT_MIN_PLAYERS_IN_TEAMS)
    {
        setState(EventState.INACTIVE);
        _teams[0].cleanMe();
        _teams[1].cleanMe();
        return false;
    }

    closeDoors();
    setState(EventState.STARTED); // set state to STARTED here, so TvTEventTeleporter know to teleport to team spot

    // teleport all participants to there team spot
    for (TvTEventTeam team : _teams)
    {
        for (String playerName : team.getParticipatedPlayerNames())
        {
            L2PcInstance playerInstance = team.getParticipatedPlayers().get(playerName);

            if (playerInstance == null)
                continue;

            // implements Runnable and starts itself in constructor
            new TvTEventTeleporter(playerInstance, team.getCoordinates(), false, false);
        }
    }
    
    // Remove player from his party
    for (TvTEventTeam team : _teams)
    {
        for (String playerName : team.getParticipatedPlayerNames())
        {
            L2PcInstance playerInstance = team.getParticipatedPlayers().get(playerName);
            final L2Party party = playerInstance.getParty();
            if (party != null)
                party.removePartyMember(playerInstance, MessageType.Expelled);
        }
    }
    
    return true;
}

Do you notice the problem here?

  • 0
Posted

You mean that?

/**
* Starts the TvTEvent fight<br>
* 1. Set state EventState.STARTING<br>
* 2. Close doors specified in configs<br>
* 3. Abort if not enought participants(return false)<br>
* 4. Set state EventState.STARTED<br>
* 5. Teleport all participants to team spot<br>
* <br>
* @return boolean<br>
*/
public static boolean startFight()
{
setState(EventState.STARTING);
 
// not enought participants
if (_teams[0].getParticipatedPlayerCount() < Config.TVT_EVENT_MIN_PLAYERS_IN_TEAMS || _teams[1].getParticipatedPlayerCount() < Config.TVT_EVENT_MIN_PLAYERS_IN_TEAMS)
{
setState(EventState.INACTIVE);
_teams[0].cleanMe();
_teams[1].cleanMe();
return false;
}
 
closeDoors();
setState(EventState.STARTED); // set state to STARTED here, so TvTEventTeleporter know to teleport to team spot
 
// teleport all participants to there team spot
for (TvTEventTeam team : _teams)
{
for (String playerName : team.getParticipatedPlayerNames())
{
L2PcInstance playerInstance = team.getParticipatedPlayers().get(playerName);
 
if (playerInstance == null)
continue;
 
// implements Runnable and starts itself in constructor
new TvTEventTeleporter(playerInstance, team.getCoordinates(), false, false);
 
// remove party
final L2Party party = playerInstance.getParty();
if (party != null)
party.removePartyMember(playerInstance, MessageType.Expelled);
}
}
 
return true;
}
  • 0
Posted

 

You mean that?

/**
* Starts the TvTEvent fight<br>
* 1. Set state EventState.STARTING<br>
* 2. Close doors specified in configs<br>
* 3. Abort if not enought participants(return false)<br>
* 4. Set state EventState.STARTED<br>
* 5. Teleport all participants to team spot<br>
* <br>
* @return boolean<br>
*/
public static boolean startFight()
{
setState(EventState.STARTING);
 
// not enought participants
if (_teams[0].getParticipatedPlayerCount() < Config.TVT_EVENT_MIN_PLAYERS_IN_TEAMS || _teams[1].getParticipatedPlayerCount() < Config.TVT_EVENT_MIN_PLAYERS_IN_TEAMS)
{
setState(EventState.INACTIVE);
_teams[0].cleanMe();
_teams[1].cleanMe();
return false;
}
 
closeDoors();
setState(EventState.STARTED); // set state to STARTED here, so TvTEventTeleporter know to teleport to team spot
 
// teleport all participants to there team spot
for (TvTEventTeam team : _teams)
{
for (String playerName : team.getParticipatedPlayerNames())
{
L2PcInstance playerInstance = team.getParticipatedPlayers().get(playerName);
 
if (playerInstance == null)
continue;
 
// implements Runnable and starts itself in constructor
new TvTEventTeleporter(playerInstance, team.getCoordinates(), false, false);
 
// remove party
final L2Party party = playerInstance.getParty();
if (party != null)
party.removePartyMember(playerInstance, MessageType.Expelled);
}
}
 
return true;
}

Well, that is better. :P

/**
* Starts the TvTEvent fight<br>
* 1. Set state EventState.STARTING<br>
* 2. Close doors specified in configs<br>
* 3. Abort if not enought participants(return false)<br>
* 4. Set state EventState.STARTED<br>
* 5. Teleport all participants to team spot<br><br>
*
* @return boolean<br>
*/
public static boolean startFight()
{
    setState(EventState.STARTING);

    // not enought participants
    if (_teams[0].getParticipatedPlayerCount() < Config.TVT_EVENT_MIN_PLAYERS_IN_TEAMS || _teams[1].getParticipatedPlayerCount() < Config.TVT_EVENT_MIN_PLAYERS_IN_TEAMS)
    {
        setState(EventState.INACTIVE);
        _teams[0].cleanMe();
        _teams[1].cleanMe();
        return false;
    }

    closeDoors();
    setState(EventState.STARTED); // set state to STARTED here, so TvTEventTeleporter know to teleport to team spot

    // teleport all participants to there team spot
    for (TvTEventTeam team : _teams)
    {
        for (String playerName : team.getParticipatedPlayerNames())
        {
            L2PcInstance playerInstance = team.getParticipatedPlayers().get(playerName);

            if (playerInstance == null)
                continue;

            // leave party
            playerInstance.leaveParty();

            // implements Runnable and starts itself in constructor
            new TvTEventTeleporter(playerInstance, team.getCoordinates(), false, false);
        }
    }

    return true;
}
  • 0
Posted

Bubu, you should use

 

 

if (activeChar.isInParty())
    activeChar.getParty().removePartyMember(activeChar, MessageType.Expelled);
  • 0
Posted (edited)

 

Bubu, you should use

if (activeChar.isInParty())
    activeChar.getParty().removePartyMember(activeChar, MessageType.Expelled);

Why? As I see, leaveParty() does exactly the same...  :lol:

Edited by Tessa
  • 0
Posted

 

Yes and no :D

_party.removePartyMember(this, MessageType.Disconnected);

I'm considering it "leaving by own will", because you can't be expelled if you are the party leader. :D

  • 0
Posted

you can't be expelled if you are the party leader. :D

Ohh you can, in such cases :D Anyway, not big deal what message you will see, who cares ^_^

  • 0
Posted

Ohh you can, in such cases :D Anyway, not big deal what message you will see, who cares ^_^

Technically you can, yes, of course. :D

  • 0
Posted

This man uses leaked aCis sources. You all ready to help everyone the cheap user who don't respect a work of another people?  :dat:

 

one my friend give it to me bcuz of my problems with money... :(

Anyway...that what i use is all ready shared at our russian forums :P so... 

  • 0
Posted

one my friend give it to me bcuz of my problems with money... :(

Anyway...that what i use is all ready shared at our russian forums :P so... 

No money for food  :(

Guest
This topic is now closed to further replies.



  • Posts

    • Reconstructed the MSNP8 client/server chain in Lineage 2 (from C4 to HFp5) with full protocol capabilities + added Discord integration    Clean MSNP8:       MSNP8 + Discord Bridge:   
    • I'm looking for the GVE code for Luecera2.
    • Recommended seller, I'm using his services. Good luck @Ave
    • https://l2.gamedream.pl/ Update #2 — GameDream Interlude (C6)     This update focuses on Epic bosses, quest chains and overall QoL :cool Highlights: Frintezza access follows a full retail-like chain: Four Goblets → Last Imperial Prince → Journey to a Settlement Retail-like entry requirements restored (scroll + Command Channel) Four Goblets quest is now available in-game Shot visuals synced with attack/skill usage Community Board Premium Shop refreshed with classic Interlude buttons and cleaner tables Epic Raidboss access: Frintezza — 4–5 party Command Channel + scroll + Antique Brooch Antharas — Portal Stone Baium — Bloody Fabric Valakas — Floating Stone Queen Ant / Core / Orfen / Zaken — no quest gates Bug Fixes & QoL: Frintezza quest chain fully fixed TvT rewards — single reward + anti-abuse protection Shots — no double triggering Premium Shop — no blank tabs Mammon NPCs in Giran working correctly Cancel works retail-like (up to 5 buffs removed) Summon Friend fixed with anti-exploit guards YetiBuffer — Saved Buff Profiles (Save / Clear / Restore) PvE — increased aggro range + balance tweaks EXP toggle commands: expoff / expon / expblock Thanks for testing and feedback — more updates coming soon ❤️
    • Hello I would like to offer You my NEW 2026 Updater / Launcher with custom skins.   - UPDATER FEATURES -   1. Performance and Intelligent Resource Management: Smart Disk Detection (SSD/HDD): The updater automatically detects the user's drive type. For SSD/NVMe drives: Launches up to 8-12 concurrent threads, utilizing the full yet optimized connection speed. For HDD drives: Limits the thread count (to 2-3) to prevent computer slowdowns and avoid overloading the drive head. Multi-threaded Downloading: Instead of downloading file by file, the updater downloads multiple files simultaneously, drastically reducing update time. ZSTD Compression: Support for the modern Zstandard compression algorithm (.zst). Files are downloaded in compressed form and decompressed on the fly, saving bandwidth and accelerating downloads. HTTP/2 and Keep-Alive Support: Utilizing the HTTP/2 protocol and persistent connections allows for the instant download of thousands of small files without establishing a new connection for each one.   2. Modern User Interface (UI/UX): Transparency and PNG Graphics: Support for irregular window shapes, allowing for the creation of a unique, modern launcher look. Taskbar Integration: The progress bar is displayed not only in the window but also on the Windows taskbar icon. Built-in News Browser (Optional): The updater features a built-in browser module that displays news/changelogs directly within the launcher (without opening an external browser). Multi-language Support (Optional): Built-in language switching system (e.g., EN/PL/RU, etc.) with dynamic loading of button graphics and text. Animated Buttons (Optional): Dedicated, animated buttons redirecting to Discord, Facebook, YouTube, Instagram, and the website.   3. Technical Features and Application Security: Anti-Dual Run (Optional): The updater checks if the game is already running to prevent file conflicts during updates. Error Diagnostics: Built-in logging system (debug_log.txt) and hardware exception handling (SEH), facilitating the diagnosis of problems for players who cannot run the game. Internal Configuration: Updater settings are stored inside the .exe file, eliminating publicly accessible configuration files.   4. File Categorization (Normal vs. Critical vs. Once): Critical Files: Critical files are verified more thoroughly (via MD5 Hash) even in quick check mode to guarantee stability. Normal Files: Standard game files (textures, models, sounds) are checked depending on the selected mode (Quick vs. Full). Once Files (Overwrite Exclusions): Applies to user configuration files (e.g., Option.ini, User.ini).   5. Check Modes (Verification Algorithms): Self-Update: The updater can update itself before checking game files, allowing for easy deployment of launcher fixes. The updater supports two main operating modes that switch intelligently based on user action: Smart Check (Startup Quick Check): Runs automatically upon updater startup or pressing the START button (unless a full check is forced). Full Check (Full MD5 Verification): Manually triggered by the player via the "Full Check" button. Automatic Update Detection: If a newer version of a file appears on the server, it is automatically detected and downloaded without player interaction. Atomic Updates: Files are downloaded and verified first, and only then saved to the disk. This prevents game client corruption in case of internet connection loss. The entire process takes seconds, even with clients weighing 30GB+. - PATCH BUILDER FEATURES -   1. Professional File Structure Management (Tree-List Hybrid): Directory Tree Visualization: Instead of a flat file list, the Builder displays a clear structure of folders and subfolders. You can collapse and expand entire tree branches, facilitating work with thousands of files. Normal and Critical Division: A clear window division into two main zones: Normal Files and Critical Files. Ghost and Excluded Files Division: The interface visually informs about the status of unchanged files (existing in the previous patch version) and files excluded from the update. Show/Hide Ghosts: With one click, you can hide unchanged files to focus solely on what you are actually sending to players in this update.   2. Intuitive Interaction: Drag & Drop: Full Drag & Drop support. You can grab files or entire folders and drag them between the "Normal" and "Critical" lists. Transfer is intelligent – it moves the entire content of selected folders. Keyboard Shortcuts: Fast workflow thanks to keyboard support: Delete, Enter, Ctrl+A / Ctrl+C (select and copy paths).   3. Advanced Filtering and Searching: Context Search: The search bar works in real-time, filtering the file tree. Type /folder: Searches only within folder names. Type *ex: Shows only excluded files. Standard Typing: Searches files by name.   4. Automation and Security: Auto Self-Update: The Builder automatically detects the updater executable file. Real-Time Statistics: The status bar continuously shows the file count (Normal/Critical), total patch weight (in Bytes/MB/GB), and the last update date. System File Protection: Files marked as "Critical" cannot be accidentally added to the exclusion list – the program blocks such actions.   5. Performance (Backend): ZSTD Compression: The Builder uses the latest Zstandard algorithm to compress files before sending, ensuring a significantly smaller patch size than standard ZIP, saving server bandwidth and player time. Multi-threading: The packing and MD5 checksum generation process utilizes multiple CPU threads, drastically reducing patch building time.   - PRICING - NEW Updater standard price: 79 euro (if You ask for mods, price will change).   - CONTACT - Discord: ave7309   CLICK HERE TO CHECK LATEST TEMPLATES!                         * I have right to REFUSE to take an order. * Supported games: Lineage 2 / Black Desert / MU Online / Tantra / Rohan / Aion / Cabal / Fiesta any more...  
  • 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..