Jump to content

Recommended Posts

Posted

it give me errors when i try save it.. in fileedit... my fileedit is good.. idk .. i have try put this there

 

0	80000	1	1	6	1	0	LineageWeapons.dragon_slayer_m00_wp	LineageWeapons.dragon_slayer_m00_wp		LineageWeaponsTex.dragon_slayer_t00_wp	LineageWeaponsTex.dragon_slayer_t00_wp		icon.weapon_dual_sword_i00	icon.weapon_dragon_slayer_i00	icon.weapon_dragon_slayer_i00			-1	2080	8	1	0	0			14	3	2	LineageWeapons.dragon_slayer_m00_wp	LineageWeapons.dragon_slayer_m00_wp	2	LineageWeaponsTex.dragon_slayer_t00_wp	LineageWeaponsTex.dragon_slayer_t00_wp		4	ItemSound.public_sword_shing_8	ItemSound.sword_great_4	ItemSound.sword_mid_2	ItemSound.public_sword_shing_4	ItemSound.itemdrop_dualsword	ItemSound.itemequip_dualsword		10	400	400	8	6	8	0	0	0	0	325	0	1	1	1000	0	-1	0	LineageEffect.c_u004	LineageEffect.c_u004	0.0000000	0.0000000	0.0000000	0.0000000	0.0000000	0.0000000	2.3000000	2.3000000	2.2000000	2.2000000	LineageWeapons.rangesample	LineageWeapons.rangesample	1.8000000	1.0000000	1.0000000	1.8000000	1.0000000	1.0000000	13.0000000	0.0000000	0.0000000	13.0000000	0.0000000	0.0000000	4	4	-1	-1				

 

 

and it gave me error when i tryed save someone know why ??? ... :(

 

itemname.dat works, but weapongrp.dat no it give me errors... someone know why ? ?..

Posted

First of all, get oryginal table for your chronicle - if You use for example CT2 and You are trying to put table from Interlude, You will need to change it :]

So...get the oryginal table from your weapongrp.dat and change it for your weapon :] Simple...and You will not get error :]

i tryed it.... i have copy from weapongrp duals damascus and i have changed it ... to dragon slayer.. and it too error me .. :(

Posted

Try this and tell me if it works.

0	80000	1	1	6	1	0	LineageWeapons.dragon_slayer_m00_wp	LineageWeapons.dragon_slayer_m00_wp		LineageWeaponsTex.dragon_slayer_t00_wp	LineageWeaponsTex.dragon_slayer_t00_wp			0	0	0	0	0	1	1	0	icon.weapon_dual_sword_i00	icon.weapon_dragon_slayer_i00	icon.weapon_dragon_slayer_i00			-1	2080	47	1	0	0		1		7	3	2	LineageWeapons.dragon_slayer_m00_wp	LineageWeapons.dragon_slayer_m00_wp	1	1	2	LineageWeaponsTex.dragon_slayer_t00_wp	LineageWeaponsTex.dragon_slayer_t00_wp			4	ItemSound.public_sword_shing_8	ItemSound.sword_great_4	ItemSound.sword_mid_2	ItemSound.public_sword_shing_4	ItemSound.itemdrop_dualsword	ItemSound.itemequip_dualsword		10	342	132	8	5	8	0	0	0	0	325	0	1	1	1000	0	-1	0	LineageEffect.c_u006	LineageEffect.c_u004	0.00000000	0.00000000	0.00000000	0.00000000	0.00000000	0.00000000	0.80000001	1.00000000	0.80000001	1.29999995	LineageWeapons.rangesample	LineageWeapons.rangesample	1.39999998	0.80000001	0.80000001	1.50000000	0.80000001	0.80000001	12.00000000	0.00000000	0.00000000	11.50000000	0.00000000	0.00000000	6	4	-1	-1				

Posted

you were trying to put a weapon from c2.2 i think to ct2.3. you need to know how cuz they have different columns

aha...

Posted

yes works thank you so what was the problem then ? :d

Nothink special.Just copy files from dragon slayer to other duals px tallum dark legion edge and change id only..I am glad helping you.;)

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

    • Hello, I'm completely sharing my first attempt of functional PvE & PvP level/gear based independed phantoms. This source is completely made by AI so no hard critisism please. The extension is in a very early stage and it's not tested properly so its NOT supposed to be used in a live server yet because it still needs stability/optimization improvements.   The architecture is already done, third class behaviors are looking good (but still needs adjustments mostly for melee classes). I am currently dealing with second occupation classes functionality (most of them are functional).   The extension will automatically create the lucera_autobots table on starting the gameserver and then you will be able to populate the table with many rows of bots manually or save them to DB through the ingame bot's panel, you can also create temporary bots by not hitting the "Save Bot" button. The clan can be added to the bots as clanID through lucera_autobots DB table, the clan has to be owned by a real player with or without alliance, the bot will be spawned with the clan or clan+ally crest.     Request for advices and ideas: At the moment i haven't figured out an easy way (other than building a full navigation system of the world) to make the bot understand the geodata, avoid all the city obstacles and walk to gatekeeper, then travel back to the farming location on foot and avoid any obstacles and town layout so at this current state the bots are doing this: on death > go to village > stay idle for 30 seconds (time delay can be configured from the bot's management panel or through the DB table) > directly teleport back to death location.   On in-game, use //autobots command and create bots normally through the panel's options. NOTE: The bots will not attack a gm character.               LATEST CHANGELOGS SINCE BUILD M28: M29: Improved the mechanics and behavior for all the second and third classes. Added/adjusted PvP skills and self-buffs for many classes. Improved Tyrant/Grand Khavatari combat and force-charge behavior. Added tank skill/auto-attack rotations. Added Bladedancer dances/debuff behavior. Added mage skills such as Silence, Curse Fear, Aura Flash, Ice Dagger and Frost Bolt with usage limits. Increased dagger Switch usage to 25%. Added obstacle escape movement when bots get stuck while RETURNING to their farm area. M30: Reduced the pause after tank and archer sidestep movements so they re-engage faster. Improved Titan/Destroyer combat recovery and added Braveheart condition. Started fixing Gladiator/Duelist charge/combat behavior. Verified all classes can use Idle, AttackFlagged, and AttackEveryone. Reinforced the rule that skills are used only when actually learned by the bot. M31: Fixed offensive mage combat-entry logic for AttackEveryone. Prevented hostile mage debuffs from being used as the initial action against peaceful players. M32: Added a farming-area watchdog so bots outside their configured farm range return instead of remaining stuck in FARMING. Fixed automatic teleport recovery so it cannot silently replace the bot's configured farm origin. M33: Removed the newer broken Gladiator/Duelist charge state-machine and restored more of the older M27-style combat logic. M34: Completely rewrote Gladiator/Duelist combat behavior Gladiator/Duelist now use the same core combat system in PvE and PvP. All skills remain level/learned-skill dependent. M43: Fixed a visual “jump/teleport” issue during PvP. Removed the extra manual position correction that was interfering with Lucera’s normal movement updates. Kept the old movement safety protections that prevent real long-distance rollback bugs. Added Vicious Stance toggle always ON for fighter classes when learned. Added Arcane Power toggle always ON for offensive mages level 78+ when learned. Improved potion usage so bots follow Lucera’s normal item cooldown behavior. Changed Warsmith weapons/shields for several level ranges. Added None as a buff package (the bot will spawn without buffs). Removed Greater CP Potions from level 1–39 bots. Reworked starter fighter equipment for levels 1–10 and 11–19. Corrected several starter class names in the autobots UI panel. Improved the Autobots panel layout. Improved spacing and descriptions on the Create Bot page. Added basic pagination to the autobots UI panel. Changed buttons toward Lucera’s native button style. Improved spacing around the bot list and search area. Added a search layout. Reworked the main page, Create Bot page, class selection and manage pages. No AI, combat, movement, inventory, or DB behavior was changed.   Next update milestone: Ensuring stability and optimization changes.  
    • ASocks.com provides residential, mobile and datacenter proxies with a pool of 7M+ IPs across 150+ locations. Built for web scraping, market research, ad verification, and automation, it offers flexible rotation, city- and ASN-level targeting, 24/7 support and transparent pricing with no traffic expiration.
    • SX.ORG is a global proxy platform offering residential, mobile,  and datacenter IPs for SEO, web scraping, ad verification and multi-account management. It provides flexible IP rotation, precise geo-targeting, HTTP(S)/SOCKS5 support, API access and pay-as-you-go pricing based only on the traffic you use.
  • 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..