A small bug removed.(many space added to end of character.inc)
Not a big problem but maybe can make npc editor crash with time.
Printable View
A small bug removed.(many space added to end of character.inc)
Not a big problem but maybe can make npc editor crash with time.
nice one ricky30... thanks....
Sorry ricky30 but it still crashes.
Add me on msn please:
lesderid@hotmail.com
Sorry but the quest editor is bullshit...
Without correctly using offsets/pointers to worlddialog.dll and actually allocating more virtual memory upon load of the world server it's not possible to actually edit currently implemented quests on account of the fact the world server uses the offsets returned to reference the worlddialog.txt within it's self.
It has dynamic pointers it selects it's self upon allocating the memory it does where it loads WorldDialog.txt into memory and then the external dll is used to reference the keys for the npc's based on id and once referenced they return an offset to the pointer which leads to the function to be used/text being referenced within memory.
This application does nothing with WorldDialog.dll nor does it do any sort of hooking method to the World Server files thus why I call it bullshit.
Sorry but i never said i modify worlddialog.dll
the only goal of quest editor is to allow to play to few official event adding items needed for them to all monster.
i know worlddialog is too old for v14 but for sample the last event with snowman work well.
From what I remember, not all quests are at worlddialog.dll, just some like cw quest, those 3 party quest and some more, the rest like volcane teleport quest is at propQuest.inc
propQuest.inc is old, they're no longer controlled by that and ricky just proved him self to be a retard by claiming WorldDialog.dll was to old for v14.
It's actually the new method of text storage, and quest definition because aeon soft figured out that referencing data from memory can speed up the process of things greatly.
Which is exactly what I stated, the fact that you do not modify it meaning you're not actually doing anything with quests.
Thus making your application bullshit because the name doesn't even fit the purpose.
That's different I'm not talking about teleport locations... I'm talking about "keys" as I stated before.
but generally PropQuest.inc is not used any longer for the actual quest definition I've done minor tests in the past I've not actually coded anything new into it, other then that I've planned on just writing my own quest system via hooks anyway because of the way the NPC's have to be referenced it's a bitch.
Is there any way to edit the WordDialog.dll?
Deadly, can we replace this dll with our custom build?
It exports only 4 functions (FindScriptKey, InitWorldDialog, RunDialog, SetLanguage)
But I cannot find what exe or dll uses it..
why jpg? why not dds? xD
@manneke: Yes, i'm guessing olly, or hex xD
thank you thank you
If anyone wants to know a good way to view the exact offsets of the npc dialogs, then use a program called TextScan.
Knowing the offset isn't all you need to know really I'm sure, as you also have to know how to hook it amongst other things. But maybe it'll be a start for someone anyway.Quote:
Have you ever run across a piece of software that did something that you couldn't figure out how they did it? Or perhaps you suspect that some Microsoft application might be using an undocumented function? In either situation, AnalogX TextScan gives you a quick and easy way to find out details from just about any program.
AnalogX TextScan searches any binary file for a minimum and maximum string length, and then returns all occurrences in sorted order... But it doesn't just stop there, it also has the ability to identify most functions and DLL's inside of a file, and even has the ability to extract both char and unichar strings! This is a great first step in getting a better understanding of what's happening inside of a program you're interested in, or even for just looking for the occasional Easter egg!
http://i48.photobucket.com/albums/f2...h/untitled.jpg