Jump to content
  • 0

Buffer/init problem plz help


Question

Posted

Hi you guys helped me a lot the last days with your shares!!

I am using Ct2 l2jfree

But i have a problem with my buffer.I install it corectly and when i go to press to take the buffs it says me you are not a quest or you dont meet the requirements!

when i go to init.py to add the quest the line Custom/9999.... guess what?init.py is empty

after the searced i did i find another buffer i find another solution that told me to go and copy this custom/9999_NPCBuffer/__init__.py

to scrips.cfg i did it but again nothing

plz can u help me?

5 answers to this question

Recommended Posts

  • 0
Posted

Since you are from Greece Read this topic about how to add a buffer...Your problem is on __init__.py

 

Open the __init__.py delete everything and add this

__all__ = [
'3995_echo',
'4000_ShadowWeapons',
'6050_KetraOrcSupport',
'6051_VarkaSilenosSupport',
'7000_HeroItems',
'8000_RaidbossInfo',
'9999_NPCBuffer'
]
print ""
print "importing custom data ..."
for name in __all__ :
    try :
        __import__('data.jscript.custom.'+name,globals(), locals(), ['__init__'], -1)
    except:
        print "failed to import quest : ",name
print "... done"
print ""

 

If you have any problems read this http://www.maxcheaters.com/forum/index.php?topic=33769.0 ~> Greek Language

  • 0
Posted

I did what u told me but nothing yet

i made click on the buffs but nothing happens any idea for what is the problem?

plz help

i see the buffs ww,shield etc but when i click on them nothing happens

  • 0
Posted

how u solved the problem?:SS

i have the same problem.

and with clan/ally quests..

help plz..

 

dont bump old topics i know hard to read rules...but atleast try it...

 

locked.open a new thread with your problem dont bump old ones.

Guest
This topic is now closed to further replies.


  • Posts

    • try this one instead. The one he shared affects every single NPC/player character in the game, the one I posted only affects player characters  https://drive.google.com/file/d/1UtccbD9e50x3WEnQBab2PTZnBHwpcGYM/view?usp=sharing or perhaps i misunderstood; if you could please post a full explanation of the problem you're having with the files, unfortunately i think whatever you're using to translate to english is a bit bad nevermind, i got what you mean, here's the fix   https://drive.google.com/file/d/1av7OHaGSdnVQtcBgb9MhtiIkxVXy3P2y/view?usp=sharing   CanIngnoreCollision=True CanBeIngnoredCollision=True  
    • <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
  • 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..