regarding 3rd class support (the don't ask, do topic)

Discussion about everything RO and OpenKore related. This place is NOT for ANY kind of support questions.

Moderator: Moderators

EternalHarvest
Developers
Developers
Posts: 1798
Joined: 05 Dec 2008, 05:42
Noob?: Yes

Re: regarding 3rd class support (the don't ask, do topic)

#11 Post by EternalHarvest »

Mushroom wrote:skillstatus.txt updated with new skills names + added some status that were unknown.

Code: Select all

+218 Bongun Drift
+219 Bongun Wall Shift
+220 Munak Reincarnation
+221 Death Passive Attack
+222 Death Passive Speed
+223 Death Passive Defense
+224 Death Passive Critical
+225 Death Passive Ranking
+226 Death Passive Triple
+227 Death Energy
+232 Death Aura
+233 Death Freezer
+234 Death Punish
+235 Death Instant Barrier
+236 Death Warning
+254 Dark Energy
+255 Dark First Fantasy
+256 Dark Head Defense
+257 Dark Twilight
+258 Dark Transform
+259 Dark Item Re - Build
+260 Dark Illusion
+261 Dark Soul Power
+262 Dark Ear Plug
+263 Black Gemstone Contract
+264 Black Gemstone Magic
+265 Collector Magic Cart
+266 Collector Crystal
+267 Collector Human Re - Build
+268 Collector Emperium Darkness
+269 Collector Emperium Guardian
+270 Collector Time Out
Is there any server with these skills?
Mushroom
Perl Monk
Perl Monk
Posts: 427
Joined: 04 Apr 2008, 14:04
Noob?: No
Location: Brazil

Re: regarding 3rd class support (the don't ask, do topic)

#12 Post by Mushroom »

I don't think so.
Quit.
Technology
Super Moderators
Super Moderators
Posts: 801
Joined: 06 May 2008, 12:47
Noob?: No

Re: regarding 3rd class support (the don't ask, do topic)

#13 Post by Technology »

added more to skillsstatus.txt, thanks to that file & kLab (should almost be complete now)

maybe spells still need some work

EDIT:
for headgears.txt indexes (aka. the line number or viewID) i've decompiled accessoryid.lub:
http://openkore.pastebin.com/1Hv1Wipi

to know what exactly needs to be on that index of headgears.txt i think we need to decompile: accname.lub

the flow: receive index (viewID) -> use lookuptable headgears.txt -> itemID

EDIT:
added a few entries to headgears.txt, its still unfinished
One ST0 to rule them all? One PE viewer to find them!
One ST_kRO to bring them all and in the darkness bind them...

Mount Doom awaits us, fellowship of OpenKore!
h4rry84
Moderators
Moderators
Posts: 234
Joined: 04 Apr 2008, 09:30
Noob?: Yes
Location: My House

Re: regarding 3rd class support (the don't ask, do topic)

#14 Post by h4rry84 »

Technology
Super Moderators
Super Moderators
Posts: 801
Joined: 06 May 2008, 12:47
Noob?: No

Re: regarding 3rd class support (the don't ask, do topic)

#15 Post by Technology »

yea, found those links a few days ago too.

Though, it seems accname.lub has the spritenames, not the itemnames.
* for the RO client (graphical representation) its viewID -> spritename
* for the kore client (textual representation) we need viewID -> itemID

However, I've come up with a solution, let me explain it trough an example:

Code: Select all

name: Goggles [0]
itemID: 2224
viewID: 1
accessoryid.lua

Code: Select all

ACCESSORY_IDs = {
	ACCESSORY_GOGGLES = 1,
}
accname.lua

Code: Select all

AccNameTable = {
	[ACCESSORY_IDs.ACCESSORY_GOGGLES] = "_°í±Û",
}
(spritename prefixed by _)

idnum2itemresnametable.txt

Code: Select all

2224#°í±Û#
So basically we can link viewID and itemID trough spritename:
1) viewID -> spritename (using: accessoryid.lua + accname.lua)
2) spritename -> itemID (using: idnum2itemresnametable.txt)

to conclude with: viewID -> spritename -> itemID
or finally, what is useful to us: viewID -> itemID

So in theory its possible to generate headgears.txt

Hmm, i guess we'll have to rename this topic to "The kore table files renewal project" or something. ;)
One ST0 to rule them all? One PE viewer to find them!
One ST_kRO to bring them all and in the darkness bind them...

Mount Doom awaits us, fellowship of OpenKore!
h4rry84
Moderators
Moderators
Posts: 234
Joined: 04 Apr 2008, 09:30
Noob?: Yes
Location: My House

Re: regarding 3rd class support (the don't ask, do topic)

#16 Post by h4rry84 »

hm... basically you can't simply put if the itemsID = viewID since some items use same viewID. for example rental items.
Technology
Super Moderators
Super Moderators
Posts: 801
Joined: 06 May 2008, 12:47
Noob?: No

Re: regarding 3rd class support (the don't ask, do topic)

#17 Post by Technology »

h4rry84 wrote:hm... basically you can't simply put if the itemsID = viewID since some items use same viewID. for example rental items.
Right, but this is exactly what we are doing right now too.
Unfortunately this is as accurate as it could ever get, since the RO client only cares about the appearance.

EDIT:
btw, recently another interesting lua file was added to the client: efstids.lua
this file contains useful info for skillsstatus.txt
ex

Code: Select all

EFST_PROVOKE = 0, 
One ST0 to rule them all? One PE viewer to find them!
One ST_kRO to bring them all and in the darkness bind them...

Mount Doom awaits us, fellowship of OpenKore!