Jump to content

Recommended Posts

Posted (edited)

Hello everybody, i've reading guides about editing interface.u file and everything was going ok, now when i wanted to compile the file again i got this error: Classes\AutoSkillWnd.uc(638) : Error, Redefinition of 'function IsTriggerSkill' differs from original. 

I tested with "original" file from random interface and still get the same error.

 

If i go to line 638 i have this, i dont know where the error is, because looks fine for me. Would appreciate if somebody can give me some help, thank you.

 O977W.jpg

 


function bool IsTriggerSkill (int SkillID)
{
	switch (SkillID)
	{
		case 60:
		return True;
		break;
		case 99:
		return True;
		break;
		case 196:
		return True;
		break;
		case 197:
		return True;
		break;
		case 221:
		return True;
		break;
		case 222:
		return True;
		break;
		case 226:
		return True;
		break;
		case 256:
		return True;
		break;
		case 288:
		return True;
		break;
		case 296:
		return True;
		break;
		case 312:
		return True;
		break;
		case 318:
		return True;
		break;
		case 322:
		return True;
		break;
		case 334:
		return True;
		break;
		case 335:
		return True;
		break;
		case 336:
		return True;
		break;
		case 337:
		return True;
		break;
		case 338:
		return True;
		break;
		case 339:
		return True;
		break;
		case 340:
		return True;
		break;
		case 414:
		return True;
		break;		
		case 422:
		return True;
		break;
		case 424:
		return True;
		break;
		case 1001:
		return True;
		break;
		case 1262:
		return True;
		break;
		case 1283:
		return True;
		break;
		case 4517:
		return True;
		break;
		case 4518:
		return True;
		break;
		case 4519:
		return True;
		break;
		case 4520:
		return True;
		break;
		case 4525:
		return True;
		break;
		case 4532:
		return True;
		break;
		case 4545:
		return True;
		break;
		case 5087:
		return True;
		break;
		case 344: //#Lethal Blow
		return True;
		break;
		case 263: //#Deadly Blow
		return True;
		break;
		case 409: //#Critical Blow
		return True;
		break;
		case 30: //#Backstab
		return True;
		break;
		case 16: //#Mortal Blow
		return True;
		break;
		case 321: //#Blinding Blow
		return True;
		break;
		case 1235: //#Hydro Blust
		return True;
		break;
		case 1265: //#Solar Flare
		return True;
		break;
		case 1341: //#Wind Vortex
		return True;
		break;
		case 1342: //#Light Vortex 
		return True;
		break;
		case 1417: //#Aura Flash
		return True;
		break;
		case 1231: //#Aura Flare
		return True;
		break;
		case 1267: //#Shadow Flare
		return True;
		break;
		case 1239: //#Hurricane
		return True;
		break;
		case 1340: //#Ice Vortex
		return True;
		break;
		case 1339: //#Fire Vortex
		return True;
		break;
		case 101: //# Stunning Shot
		return True;
		break;
		case 111: //#Ultimate Evasion
		return True;
		break;
		case 110: //#Ultimate Defense
		return True;
		break;
		case 445: //#Mirage
		return True;
		break;
		case 357: //#Focus Power
		return True;
		break;
		case 356: //#Focus Chance
		return True;
		break;
		case 410: //#Mortal Strike
		return True;
		break;
		case 1230: //#Prominence
		return True;
		break;
		case 1169: //#Curse Fear
		return True;
		break;
		case 1263: //#Curse Gloom
		return True;
		break;
		case 1218: //#Greater Battle heal
		return True;
		break;
		case 1148: //#Death Spike
		return True;
		break;
		case 1343: //#Dark Vortex
		return True;
		break;
		case 1234: //#Vampiric range Vampiric Claw
		return True;
		break;
		case 1159: //#Curse Death Link
		return True;
		break;
		case 358: //#Bluff
		return True;
		break;
		case 355: //#Focus Death
		return True;
		break;
		case 11: //#Trick
		return True;
		break;
		case 12: //#Switch
		return True;
		break;
		case 1409: //#Cleanse
		return True;
		break;
		case 1335: //#Balance Life
		return True;
		break;
		case 1311: //#Avatar
		return True;
		break;
		case 1401: //#Major Heal
		return True;
		break;
		case 78: //#War Cry
		return True;
		break;
		case 297: //#Duelist
		return True;
		break;
		case 94: //#Rage
		return True;
		break;
		case 176: //#Frenzy
		return True;
		break;
		case 420: //#Zealot
		return True;
		break;
		case 139: //#Guts
		return True;
		break;
		case 440: //#Braveheart
		return True;
		break;
		case 121: //#Battle Roar
		return True;
		break;
		case 413: //#Rabid Fire
		return True;
		break;
		case 424: //#War Frenzy
		return True;
		break;
		case 340: //#Riposte Stance
		return True;
		break;
		case 339: //#Parry Stance
		return True;
		break;
		case 287: //#Lionheart
		return True;
		break;
		case 19: //#Double Shot
		return True;
		break;
		case 313: //#Snipe
		return True;
		break;
		case 131: //#Hawk eye
		return True;
		break;
		case 1324: //#Summon CP Potion
		return True;
		break;
		case 1085: //#Acumen
		return True;
		break;
		case 1059: //#Empower
		return True;
		break;
		case 1004: //#The Wisdom of paagrio ( acumen from dominator)
		return True;
		break;
		case 1365: //#Soul of paagrio ( Empower from dominator)
		return True;
		break;
		case 1086: //#haste
		return True;
		break;
		case 1204: //#wind walk
		return True;
		break;
		case 1282: //#paagrio of haste (wind walk from dominator)
		return True;
		break;
		case 341: //#Touch of life
		return True;
		break;
		case 406: //#Angelic Icon
		return True;
		break;
		case 112: //#Deflect Arrow
		return True;
		break;
		case 82: //#Majesty
		return True;
		break;
		case 86: //#Reflect Damage
		return True;
		break;
		case 196: //#Holy Blade
		return True;
		break;
		case 197: //#Holy Armor
		return True;
		break;
		case 318: //#Aegis Stance
		return True;
		break;
		case 18: //#Aura Of Hate
		return True;
		break;
		case 28: //#Aggression
		return True;
		break;
		case 322: //#Shield Fortress
		return True;
		break;
		case 288: //#Guard Stance
		return True;
		break;
		case 92: //#Shield Stun
		return True;
		break;
		case 352: //#Shield Bash
		return True;
		break;
		case 121: //#Battle Roar
		return True;
		break;
		case 286: //#Provoke
		return True;
		break;
		case 181: //#Revival
		return True;
		break;
		case 337: //#Arcana Power
		return True;
		break;
		case 4: //#Dash
		return True;
		break;
		default:
		return False;
		break;
	}
}

defaultproperties
{
}

 

Edited by Kenzhal1997
  • 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

    • @Silvin Thanks    This will be very useful.
    • Hello, everyone. I am an American, looking to start my own server.... I am looking for a dev, to help me build & edit a pride-style server.  Basically, at this point: (being Lineage 2 is a dying game - with botters overtaking) I'm not looking to spend hundreds-thousands of dollars.... Even if it's a cheap not "pride-style" server, I'll be content with that, too. I have everything else as far as Name, Discord, website, and staff - I just need a dev, to help with the files.  Thanks! 🙂 
    • ## SuperPoint Editor   SuperPoint Editor is a practical visual editor for Lineage II PTS 'SuperPoint.bin' files. It is built for people who need to inspect, fix, rebuild, and draw server routes without digging through binary data by hand.   ### What You Can Do   - Open and edit 'SuperPoint.bin' files. - Export BIN data into a readable TXT format. - Save edited data back into a valid BIN file. - Validate routes before saving. - Work with SuperPoint routes, points, directed connections, and path records in tables. - Add, duplicate, delete, and reorder points. - Create direct and reverse connections between route points. - Automatically generate connections between neighboring points. - Edit raw point coordinates: 'X', 'Y', 'Z', 'Index', and 'Delay'. - Keep route names and internal route data organized. - Use either English or Ukrainian interface language.   ### C4 Server Support   Some C4 servers have 'SuperPoint.bin', but do not have 'superpointinfo.txt' in scripts. The editor supports this case directly. When 'superpointinfo.txt' is not found near the BIN file, the editor can open the BIN in C4 mode. In this mode, 'Fstring ID' is disabled because that value belongs to 'superpointinfo.txt', not to the BIN itself. The editor will not generate or modify 'superpointinfo.txt' while working in this mode. This keeps C4 data clean and avoids creating script files that the server does not actually use.   ### superpointinfo.txt Support   For chronicles that do use 'superpointinfo.txt', the editor can load and synchronize it together with the BIN data. When saving, the editor updates route nodes and coordinates while preserving existing metadata such as: - 'npc_name' - 'move_type' - 'fstring_index' - 'social_number' - 'delay' New nodes are generated with safe default values, so existing script metadata is not accidentally wiped.   ### Geodata Tools   The editor can also open converted geodata '.dat' files and display them as a map. This makes route editing much more visual. You can: - Load geodata and inspect the terrain by layer. - Zoom and pan around the map. - Create a new SuperPoint directly from a map cell. - Draw a route by clicking on the geodata. - Drag existing points to new positions. - Automatically snap 'X/Y' to the selected geo cell. - Use the selected geodata layer to fill the point 'Z'. - See all routes on the map or focus only on the selected one. This is especially useful when building new NPC movement paths or correcting bad route coordinates.   ### Connections and Paths   SuperPoint connections are directional. A connection from point '3' to point '2' is not the same as a connection from point '2' to point '3'. The editor makes this explicit by separating: - route points, - directed connections, - and the actual path records used by each connection. For simple cases, it can create direct path records automatically. For more complex movement, you can edit the path points manually. ### Built for Safe Editing The editor includes validation before saving, so common structural problems can be caught before a broken BIN is produced. It also verifies rebuilt BIN files through the converter engine. The goal is simple: edit quickly, but do not silently damage server data.   ### Unknown Field   This small 'Unknown' field is part of the original BIN structure. Most official-looking files keep it as '0', and for regular route editing there is usually no reason to change it. The editor exposes it so nothing from the BIN is hidden or lost. If you do not know exactly what your server uses it for, keep it at '0'. Download
    • NpcGrp não salva no interlúdio e da crítico quando coloca ele no cliente, já testei ele antes.
  • 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..