Model Switcher

[PlantiX]

Originally Posted by blablaRoyal

No you say "its way more harder". Don't even try to change what you said. Not knowing how to do **** and then lying about it. Wow.

And yeh, as Wicket said, everything you do is cheatable as ****. And I'm pretty sure that you did NOT have these model switcher to change any item from 1DG to 13DG in terms of look.

Very very sure. Don't lie about that either.

2 options, egy B, d12. We dont want more. Also just possible if you have a Job weapon.

[WickedNite.]

Originally Posted by PlantiX

2 options, egy B, d12. We dont want more. Also just possible if you have a Job weapon.

Dat refitemID restriction can be done by any rookie.

It's cute how you avoid what i said about your features being useless, you can't do anything about it coz u probably have not enough brains for it.

[PlantiX]

I just wont start a war again. Im out.

[WickedNite.]

Originally Posted by PlantiX

I just wont start a war again. Im out.

You shouldn't have been here in the first place

[Dragonz2105]

sorry if im asking much
is there anyway to make detection between weapon ?

like 1 scroll item can work for all weapons instead of doing scroll for every item

[Syloxx]

Originally Posted by Dragonz2105

sorry if im asking much
is there anyway to make detection between weapon ?

like 1 scroll item can work for all weapons instead of doing scroll for every item

sure it works, if you want such a scroll feel free to add me in skype, note that it will not be free

[​Exo]

Originally Posted by Dragonz2105

sorry if im asking much
is there anyway to make detection between weapon?

like 1 scroll item can work for all weapons instead of doing scroll for every item

Okay, I guess it could if there's only 1 model for every item, then yes it can work.
PS: You will have to add a static code like ITEM%_SKIN_1 so you can detect them.

[Dragonz2105]

Originally Posted by xExorcist

Okay, I guess it could if there's only 1 model for every item, then yes it can work.
PS: You will have to add a static code like ITEM%_SKIN_1 so you can detect them.

that u talking about i already did thanks
but what im talking about is like 1 scroll can handle

if i activate the scroll with bow sos it gives bow and sos / spear moon = spear moon

hope u get it ..

[​Exo]

Originally Posted by Dragonz2105

that u talking about i already did thanks
but what im talking about is like 1 scroll can handle

if i activate the scroll with bow sos it gives bow and sos / spear moon = spear moon

hope u get it ..

Dude, ITEM%_SKIN_1 if this exists then it will give the other one no matter what so A_RARE should give %A_RARE_SKIN_1 it just depends if it exists or not. This is why I said you must have a static in your code / query

[magicanoo]

You don't have to make 1 scroll for each "item". You can make 1 scroll for each "model", for example : 1 scroll for D9 model. The script will detect the ID of the item used and replace it with the new item ID.

Let's say that the sos BOW with d8 skin ID = 5000 / sos bow with d10 skin ID = 90000
and som spear with d8 skin ID = 6000/ som spear with d10 skin ID = 99999

SELECT @newItemID = CASE @OldRefItemID
WHEN 5000 THEN 90000
WHEN 6000 THEN 99999
ELSE
--item is not listed -do whatever here-
END
--do your update statement here.

*That code is not tested, it's just to give you a general idea*

[​Exo]

Originally Posted by magicanoo

You don't have to make 1 scroll for each "item". You can make 1 scroll for each "model", for example : 1 scroll for D9 model. The script will detect the ID of the item used and replace it with the new item ID.

Let's say that the sos BOW with d8 skin ID = 5000 / sos bow with d10 skin ID = 90000
and som spear with d8 skin ID = 6000/ som spear with d10 skin ID = 99999

SELECT @newItemID = CASE @OldRefItemID
WHEN 5000 THEN 90000
WHEN 6000 THEN 99999
ELSE
--item is not listed -do whatever here-
END
--do your update statement here.

*That code is not tested, it's just to give you a general idea*

No offense but this completely sucks, having a static code is better. And yes that's what I said 1 for each model--"static". Then you just check the code of the item-> exisits -> add _SKIN -> regenerate the itemid. Avoid any static codes cuz that sucks if you have **** loads of items you will have to write a **** long query so this works better.

[magicanoo]

[Syloxx]

Originally Posted by magicanoo

in CASE its still the same, you have to set EVERY old + new ItemID.

there is something is silkroad called TypeID's try to use that!

CustomTable

RefItemID, TypeID2, TypeID3, TypeID4, Rarity, ItemClass

and you have all required informations

[​Exo]

Originally Posted by magicanoo

Which part of avoiding writing 1000 lines of codes didn't you get, you're trying to manually set each ID for its corresponding.

I meant a static CodeName eg(ITEM%_SKIN_10)

It's not my fault that you didn't get what I meant....

P-S. I'm not here to argue, just telling you that manually setting ID's for every item isn't the best choice!

[magicanoo]

How is it the same?

Adding every scroll separately :
-18 weapons x 4 different skins = 72 scrolls
-adding 72 "if" statements in the _addtimedjob
-each if statement will contain separate (select weapon id/check if the old item ID is correct/update the new ID).
What if a user used a spear switch scroll on a sword scroll? execution will fail? you'll give him another scroll after teleporting him?
does he have to buy a specific scroll for each item? are you serious?


one scroll per skin degree:
-4 scrolls
-4x "if" statements
-each "if" statements will contain (select weapon id/case statement with all the possible items/update the new ID).
This way it becomes GENERIC and with LESS code.