Jump to content
  • 0

Question

12 answers to this question

Recommended Posts

  • 0
Posted

lol multisell for what? For being teleported? It's for exchanging not being teleported x.x

 

I answered you already i think dayhunter..

 

This row means:

Description of the teleport: (dino island)

ID of the teleport (it is used on the html to call the teleport to.... ID): (90000)

loc (x): (26475)

loc (y): (-12129)

loc (z): (-2419)

Price (in adena): (10000)

fornoble (is that a noblesse only teleport?): (0)

 

You have to use int values for the last one (that one you asked), one or zero, zero stands for FALSE, 1 for TRUE...

  • 0
Posted

yep!...

I think the guy wants to change the price needed to tp to a place like dino isle...

anyway...

Change the (10000) with the number you want...

or change the xmls etC

  • 0
Posted

Nope you don't get the point, he wants to change the ADENA USAGE, not THE AMMOUNT x.x

 

And wtf r u all talking about? :P The only way that some1 can do it by changing the XML is to change the exchange XMLs for the scrolls that teleport you to any town, which i don't find it useful x.x I have never seen on a server using the scrolls that you get by exchanging tokens for teleporting around, it is a way retarded :P

  • 0
Posted

DROP TABLE IF EXISTS teleport;

CREATE TABLE teleport (

  Description varchar(75) default NULL,

  id decimal(11,0) NOT NULL default '0',

  loc_x decimal(9,0) default NULL,

  loc_y decimal(9,0) default NULL,

  loc_z decimal(9,0) default NULL,

  price decimal(6,0) default NULL,

  fornoble int(1) NOT NULL default '0',

  PRIMARY KEY  (id)

) TYPE=MyISAM;

this is wha are you talking about killer?

  • 0
Posted

lol dunno how .. u need multisell but it will not work .. so forget it

 

@thevortex What did you say that i didn't read?

 

@dayhunter Yes, but this is the sql command to request to make a table with the following columns and each column with these characteristics... The one you pasted here (first post) is a row from that table...

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..