Night

Soo the source of 2089 is still on internet?

it was not released or maybe it was not stolen who knows i have seen comments saying that the src that where stolen from ymir was the first src (2004) by china hackers (or at least thats what i remember) the secound time the last leak any way a leak is a leak thinking about the past insted of learining from it is just a waste of time. dont let your source get public ^^.

 

 

0413 00:21:02685 :: 
introLogin.py(line:566) introLogin.LoginWindow.__LoadScript (introLogin.c:11073)
ui.py(line:2792) ui.PythonScriptLoader.LoadScriptFile (ui.c:67759)

LoginWindow.__LoadScript.LoadObject - <type 'exceptions.KeyError'>:'window'

0413 00:21:02685 :: ============================================================================================================
0413 00:21:02685 :: Abort!!!!

some error im sure about this introLogin.py(line:566) look at what you have there you should at least know what is the reason if the bug (btw the smallest error might cz the client to crush so be carefull)

 

introLogin.py

	def __LoadScript(self, fileName):
		import dbg
		try:
			pyScrLoader = ui.PythonScriptLoader()
			pyScrLoader.LoadScriptFile(self, fileName)
		except:
			import exception
			exception.Abort("LoginWindow.__LoadScript.LoadObject")

ui.py

	def LoadScriptFile(self, window, FileName):

		Body = self.ScriptDictionary["window"]
		self.CheckKeyList("window", Body, self.BODY_KEY_LIST)

		window.ClearDictionary()
		self.InsertFunction = window.InsertChild

is there anything above that syserr ?

0413 00:21:02685 :: 
introLogin.py(line:566) introLogin.LoginWindow.__LoadScript (introLogin.c:11073)
ui.py(line:2792) ui.PythonScriptLoader.LoadScriptFile (ui.c:67759)

LoginWindow.__LoadScript.LoadObject - <type 'exceptions.KeyError'>:'window'

0413 00:21:02685 :: ============================================================================================================
0413 00:21:02685 :: Abort!!!!

some error im sure about this introLogin.py(line:566) look at what you have there you should at least know what is the reason if the bug (btw the smallest error might cz the client to crush so be carefull)

CLIENT_DESC [db_clientdesc] trying DBPacket() while not connected

yeh if the db crush then you get this as a gift

"connection: refused" the main reason for this is your proto no matter what the reason might be (ident or syntax or anything)

 

try using per_qc

pre_qc just replaces the defines

 

i know this ^^ , btw it is possible to get such an error if the quest does not have the correct number of

end

try using per_qc

i think that windows is detecting something that make it do that  (>.< stupid idea anyone can think of)

any way i did not get this when i had win 7 nor in 8. + that logo -.- you were drunk when you made that right?

File "uifastequip.py", line 32 copy

 

Hello, mainline_released... 

40250.

ok thanks

this binary source is mainline_released or novaline?

 

a mix most likly . if i remember correctly it does use quest category packet from novaline (this does not affect the client or cz any harm) .

if this does not bother you could you upload the script you are using?

you can backtrace it using   : bt

for full backtrace use :

bt full

well just a question :

what system are you tring to complie on ? (x86/x64)

(on freebsd use uname -a to get such info)

the latest update contain 2 new sub type for ITEM_COSTUME :

COSTUME_ACCE
COSTUME_MOUNT

and one new apply

APPLY_ACCEDRAIN_RATE

thats why you can not unpack the latest item proto , you will have to update your bin to support those new type , if anything else this will became realy bothersome

its about the table size the current table has new item type/subtype many new one like -> claw wolfman antiflag and the sash system you can not unpack it with the current public tools

if you are trying to unpack your item proto with a newer proto extractor you will get the same you need to unpack it with the old version the update it

too old libs for the complier or none existing . add them or  update them.

btw you have already passed the compile phase you have already compiled the src you are stuck with linking which is kind of a bit hard.

Errors

"No module named xxx" are of case sensitive.

Change uitooltip for uiToolTip.

not always true but this can fix it , i hade a simlar problem where i had to import the module like this :

	def __anything(self):
		from something import first
		if self.something.first_shown == 1:
			self.somthing.Hide()
		else:
			self.somthing.Show()

insted of importing at the begining of the file

Yes, but in 40k it's impossible to decrypt and crypt item_proto from client...

And secondly, 40k have that "item_names.txt" and "item_proto.txt", and I hate it...

34k -> end of 2012

40k -> 2013

we are on 2015 , you should realy consider upgrading , the use of the ".txt" is not necessary there are many releases when it comes to changing the item/mob proto reading from txt to sql , it's free and way better then 34k that is too risky to use compared to your own complied core.

Night so if Ymir make something for CopyRight then i will have problem or the host?

everyone will have problems . not just you and the host but any way thats a bit far there are at least 10k private server on the world they can not do much in short amount of time .

Hello I have got many questions about Copyright!

1)If i am hosting at eterhost is there a way to close my server of lience?

2)Is there a way for uploading a client without be afraid of lience because i am using m2m maps , mobs etc ....

1- the hosting does not realy change much when it comes to copyright in my opinion  , if ymir wanted to shut the PS off they could have done this long ago.

2- wtf ? i mean what can they do anyway as far as i remember they themself have done more then that so do not worry about it. no matter what you do when it comse to metin2 no one can clame copyright exept for ymir.

 

Thanks, but i think you should put a guide of how to repair the errors give the *.py files when you are cythonicing, a lot of people cant use the system if dont know how repair it. <-- this is not going for me, I know how to fix it.

Only to increase the information in the post.

The only two errors you could get when you compile your root are:

• "Decoding error, missing or incorrect coding"

  Since all the .py files are processed as korean strings, all of them written with a different charset (arabic) will trigger this issue.

  It's explained in the .txt file, and you can simply bypass this just writing the text in the locale_game.txt file.

• "Expected an increase in indentation level"

  This happens when the .py file has a bad tabulation, so bad written:

  It's clear that you won't be able to compile unworkable/unrunnable/broken .py files.

 

i rarely do something like that but some encoding error happened , well ppl should use what was made for such a thing (localeinfo/uiscriptlocale)

+ nice tuto

and thanks for the Credits ahah

as far as i have seen in this forum there are less then 3 diff posts you wont find that much for r40k for two main reason :

1-bcz the src is public sence 2013 .

2-no one will waste his time makeing them while he can edite the src directly.

but its not imposible.

you should add the new event motion types 11-12.

or buy them from martysama/ken(ellie)(rise)(what ever his username)

you should at least have directx8 or 9 in your pc , download it from microsoft website :

http://www.microsoft.com/fr-fr/download/details.aspx?id=34429

item_number  item_id  how_much  rate
          1      120         1    20

this is how it is. +respect the [TAB]

https://mega.co.nz/#!ZAYQmRwR!RQ4BIuKUFZs2fLZF5TfqXOte58yu5ZyFi5lvOjRnQGc

that variable was a small dec i forgot sorry