the autonexus code

This code is placed in the player update function because the code there executes very often and has the parameters that let us look up the information we need. The code is placed at the end of the function for convenience. It could be placed anywhere in the update function as long as it isn't nested in one of the conditionals.

Btw, the code in the mod selector has a bug in it. It should start off with a pop instruction.

Have a look here. It explains the code a bit more: http://www.mpgh.net/forum/655-realm-...ml#post6664352 .

ok
now what should i look in yodga for replacing strings like gs_, gsc_ , _-0Q for next release ??

I am guessing that gs_, and gsc_ stay the same, but you need to find the equivalent function for _-0Q.
Open up _-0Q in the current version, get an idea of everything (the layout) in the code, then find the similar _-## one in a new version.

ok
let assume this come will work in any version.
where should I look to find the new name of the following propertie : _-d7 , _-Kj, gs_ , gsc_ and _-0Q ?

Here what i tried to do, in order to understand how to find what means every property and to be able to find them in next version :
for _-K and _-d7 , both are defined in com\company\assembleegameclient\objects\GameObject .class.asasm as
trait slot QName(PackageNamespace(""), "_-Kj") type QName(PackageNamespace(""), "int") value Integer(200) end
trait slot QName(PackageNamespace(""), "_-d7") type QName(PackageNamespace(""), "int") value Integer(200) end

It seems they are the life bar ?

about _-0Q i have not find definition but this ... how can i replace _-0Q by the correct function in next version ? (same for gs_ , gsc_)
i looked and find this :

ok i read that

ok so for the latest Testing version (from today- new one)

I found same definition nearly for the lifebar properties :
trait slot QName(PackageNamespace(""), "_-0Xy") type QName(PackageNamespace(""), "int") value Integer(200) end
trait slot QName(PackageNamespace(""), "_-ln") type QName(PackageNamespace(""), "int") value Integer(200) end
which are the perfect candidates !

so I imagine i can inject at line 4909 of com\company\assembleegameclient\objects\Player.cla ss.asasm

regarding "gs_" fortunatly its same line in both version :
v2.0:trait slot QName(PackageNamespace(""), "gs_") type QName(PackageNamespace("com.company.assembleegamec lient.game"), "GameSprite") value Null() end
test :trait slot QName(PackageNamespace(""), "gs_") type QName(PackageNamespace("com.company.assembleegamec lient.game"), "GameSprite") value Null() end

regarding "gsc_" :/
v2.0:Line 211: trait slot QName(PackageNamespace(""), "gsc_") type QName(PackageNamespace("com.company.assembleegamec lient.net"), "_-03v") end
test :Line 211: trait slot QName(PackageNamespace(""), "gsc_") type QName(PackageNamespace("com.company.assembleegamec lient.net"), "_-0Ru") end

regarding "_-0Q"
I have no clue at all how to find the equivalent procedure in new version, what should be looking at ?

gorgor you need to read up on classes. What are properties and methods of classes and how one class can be built on top of other classes. Understanding classes will enable you to track down these names.

I know about class, and their methods... but I don't understand the link with "_-0Q"
should i try to find the method _-0Q somewhere, and if yes how does look like the definition of "_-0Q" ?
thank you for your patience and help.

---------- Post added at 08:51 PM ---------- Previous post was at 08:31 PM ----------

ok looks like i find a definition :
trait method QName(PackageNamespace(""), "_-0Q") flag FINAL dispid 4
....
then some manipulation on "XMLNode" stuff
I find the same.. I am now testing my new autonexus on test... I let you know

There is the possibility that a class will have a parameter / method that has the same _-name as one in another class. So searching for any old _-0Q isn't the best approach.

Look at this part:

This tells you where to find _-0Q. The first instruction tells you to get the property of the current classe "map_". The next instruction says to get the property "gs_" of "map_". The next instruction says to get "gsc_" of "gs_" of "map_". Finally the next instruction says to call the method "_-0Q" of "gs_" of "gsc_" of "map_". In actionscript 3 the call would look like this:

Realizing this, backtrack by looking in Player.class.asasm for what type map_ is (the class map_ represents). Then look at that class to find what class type gs_ represents. Then look at that class to see what class gsc_ represents. Then finally look at that class to find where _-0Q is.

Btw, if you don't know what the class type is, look at this:

trait slot QName(PackageNamespace(""), "gsc_") type QName(PackageNamespace("com.company.assembleegamec lient.net"), "_-0Ru") end

nice explain !
let me fight testing last version now ))
thanks i ll bring feedbacks !

For a little bit easier route that is not as conducive to learning as the previous approach, search the files in com/company/assembleegameclient/game/*.class.asasm . One of those contains all the hotkey info. There is a variable in there named "escapeToNexus". This is actually the area of code that gets run when you press your nexus button. It will contain the call to function you are looking for.

I have check an find this
but i see no common point with the "_-0Q" ... nothing at all ...

You'll probably have an easier time looking at actionscript code than flash assembly. The pic above is from AS3 Sorcerer.