[SOLVED] More information: 'GAMEOBJECT_TYPE_CAPTUREPOINT = 29'

[DarkAngel]

I am looking for more information in regards to this: 'GAMEOBJECT_TYPE_CAPTUREPOINT = 29' gameobject type.
Looking at kspn's data field information on the gameobject type I can see that many of them seem to contain unknown values.

Any information is appreciated!

Regards,
DarkAngel

 

[Tommy]

This is clear enough for me:

*GAMEOBJECT_TYPE_CAPTUREPOINT = 29

• data0: radius (Distance)
• data1: spell (Unknown ID, not a spell id in dbc file, maybe server only side spell)
• data2: worldState1
• data3: worldstate2
• data4: winEventID1 (Unknown Event ID)
• data5: winEventID2 (Unknown Event ID)
• data6: contestedEventID1 (Unknown Event ID)
• data7: contestedEventID2 (Unknown Event ID)
• data8: progressEventID1 (Unknown Event ID)
• data9: progressEventID2 (Unknown Event ID)
• data10: neutralEventID1 (Unknown Event ID)
• data11: neutralEventID2 (Unknown Event ID)
• data12: neutralPercent
• data13: worldstate3
• data14: minSuperiority
• data15: maxSuperiority
• data16: minTime (in seconds)
• data17: maxTime (in seconds)
• data18: large? (Boolean flag)

I've used this before in one of my 'radius' capture system. Only real thing you need to worry about is the radius. Radius determines where you can start capturing the point. Anyway, not sure if that's what you're really asking for.

 

[DarkAngel]

This is clear enough for me:

*GAMEOBJECT_TYPE_CAPTUREPOINT = 29

• data0: radius (Distance)
• data1: spell (Unknown ID, not a spell id in dbc file, maybe server only side spell)
• data2: worldState1
• data3: worldstate2
• data4: winEventID1 (Unknown Event ID)
• data5: winEventID2 (Unknown Event ID)
• data6: contestedEventID1 (Unknown Event ID)
• data7: contestedEventID2 (Unknown Event ID)
• data8: progressEventID1 (Unknown Event ID)
• data9: progressEventID2 (Unknown Event ID)
• data10: neutralEventID1 (Unknown Event ID)
• data11: neutralEventID2 (Unknown Event ID)
• data12: neutralPercent
• data13: worldstate3
• data14: minSuperiority
• data15: maxSuperiority
• data16: minTime (in seconds)
• data17: maxTime (in seconds)
• data18: large? (Boolean flag)

I've used this before in one of my 'radius' capture system. Only real thing you need to worry about is the radius. Radius determines where you can start capturing the point. Anyway, not sure if that's what you're really asking for.

Thank you, was exactly what I was looking for - the solution as to what to write in the different fields.
I was getting unsure because of all the 'Unknown Event IDs'.