Jump to content

Recommended Posts

Posted

Hello, i was searching for this command but i didnt found it in our forum so i decided to share it, below you can preview the html's


 


 

 



fnvm36.giff0n4vs.gif
How to install it? EASY:

 

 



1. GameServer\data\html\mods (add here the repair FOLDER not only the files)
2. GameServer\data\scripts\handlers\voicedcommandhandlers (only the file Repair.java)


  (dont forget to edit your masterhandler.java script)

 

 


This is the hidden content, please



Credits: Szponiasty

 

 

 

 

  • 1 year later...
  • 2 years later...
Posted

How would you look in the parts of the connection to the database? These parts here,

 

UPDATE characters SET x=17867, y=170259, z=-3503 WHERE charId=?"

 

 

and

 

SELECT charId FROM characters WHERE char_name=?"

 

Because that way nothing happens, I already changed

 

that

 

charId

 

for that

 

obj_id

 

 

And it's still happening, he does not even notice the other player.

  • 10 months later...
Posted (edited)

HTML repair button does nothing, like @l2jkain said, for acis the charId needs to be changed tp obj_id, and on character_shortcuts needs to be like this:
 "DELETE FROM character_shortcuts WHERE char_obj_id=?"

 

if you run ".startrepair charactername" it will do the repair, but if you run the HTML and press the "REPAIR" button nothing happens.

Update:
 

in repair.htm edit the repair button to match this:
<button value="Repair" action="bypass -h voice_startrepair $name" width="75" height="26" back="L2UI_ct1.button_df" fore="L2UI_ct1.button_df">

From there on ti should work

Edited by abumini
  • 1 month later...
Posted

Hello! I ask to help with one problem.
Installed this share on aCis 374 and, like, everything works, but it's not entirely correct.
the .repair command launches, the window opens, but after clicking on the Repair button, it always comes out - Repair Attempt: Failed. And if you enter manually .startrepair <crar_name>, then everything works as it should.

As if in a line     

<button value = "Repair" action = "bypass -h voiced_startrepair $name".....

$name - the repairChar value is not defined and the query is in the string
      

 if (command.startsWith ("startrepair") && (repairChar! = null))

is always "null", so the error also gets out. I'm just starting to understand all this. Thank you.

Posted
On 06/03/2018 at 7:10 PM, Seemann said:

Hello! I ask to help with one problem.
Installed this share on aCis 374 and, like, everything works, but it's not entirely correct.
the .repair command launches, the window opens, but after clicking on the Repair button, it always comes out - Repair Attempt: Failed. And if you enter manually .startrepair <crar_name>, then everything works as it should.

As if in a line     


<button value = "Repair" action = "bypass -h voiced_startrepair $name".....

$name - the repairChar value is not defined and the query is in the string
      


 if (command.startsWith ("startrepair") && (repairChar! = null))

is always "null", so the error also gets out. I'm just starting to understand all this. Thank you.

It's not the .repair thats wrong.
Your VoiceCommand probably doesn't have a condition in the RequestBypassToServer.java for the command "voice_" or "voiced_", it depends on what version you created.

 

Try adding this:
https://pastebin.com/ttb3FW5Q

Posted

At me bypass it is "voiced_", in that continually that the command passes (if I specifically specify the wrong command in repair.htm, I receive the message about its absence), and here the name which should be substituted instead of $name is ignored, if the command did not pass I would not see a log Repair Attempt: Failed in the terminal. This log appears only if the name is not specified, I can also just enter the .startrepair command without a name and the same log "Repair Attempt: Failed ". May be problem in htm? x_x

Posted

try to debug it. and see what's missing.

Mine is working witouth a problem. if you bypass states "voiced_" then the htm command should be:
 

<button value="Repair" action="bypass -h voice_startrepair $name" width="75" height="26" back="L2UI_ct1.button_df" fore="L2UI_ct1.button_df">


You don't need to edit anything else in the htm.
If it didn't work, try it on a fresh instance and track down the culprit.

 

 

  • 2 weeks later...
  • 1 month later...
  • 2 weeks later...

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

    • Thank you for your feedback. To help me improve the system, please leave your comments or report any bugs. I will try to release weekly updates. 
    • Thank you for your feedback, SkyLord — even the negative kind.   Let me give you some context on who we actually are, since you asked. L2-Scripts has been around for nearly 20 years. Over that time, we've worked with a large number of developers — I've personally seen probably half of every serious (and not-so-serious) developer in this scene. The most significant figure in our studio's history was Bonux. Together with a small team of assistants, he was essentially the backbone of our old codebase, and we were the ones who brought virtually every chronicle to the community — Essence, Classic, Main — all of it came through us.   Back then, we worked at scale. That era is over. Today, L2-Scripts is no longer a studio in the traditional sense. It's more of a developer collective. I work alongside the best developers I've encountered in 20 years. Bonux is still with us on Classic. A new developer named Den has joined — in just 3 years he became one of the top Essence developers in the world. Every one of us works independently, but we're united by long-standing friendships and shared projects.   We no longer chase every chronicle or every client. For the past several years, we've been focused exclusively on specific long-term projects where we're paid a proper salary — and when you focus like that, with 20 years of experience behind you, the quality of what you produce is on a completely different level. Our code is currently running on nearly all top Essence and Classic servers. We're now bringing Main (Last Protocol) up to that same standard.   You mentioned Nexvil. Yes, he worked with us. That was a difficult period — the lead developer at the time was not up to the standard we hold ourselves to. It was a short period, and it's long behind us.   As for the prices — I'd ask you not to judge a product by whether you personally can afford it. That's not a fair measure of value. The people running top-tier servers understand what they're paying for. If our pricing doesn't fit your budget, that's completely fine — but downvoting a service simply because it feels expensive to you doesn't reflect well, and it certainly doesn't make the product worse.   A special thank you to eMommy and Zenith for the honest and fair words — it genuinely means a lot. It's good to know there are people in this community who judge things as they are.
    • Just because someone does professional sales doesn’t mean everything is overpriced. If the products he provides are stable and good quality, then I see nothing wrong with it, and those prices aren’t even bad. Remember, we’re living in 2026, not 10 years in the past. Your mindset is probably stuck on buying the cheapest products because maybe you can’t afford better ones. And of course, there’s always someone who likes blaming others. I think you should mind your own business instead of blaming someone for how they run theirs. If you really think his prices are too expensive, then do better than him.
    • I have to be fair here and state that almost all 'good' servers on Essence/Classic are using bonux/l2scripts files and 10k for a decent essence build imo is not that bad of a price as long as nexvil is not touching these files
  • 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..