Missing "me"

[Benninger]

Hi there,

after some months I returned to ArcheAge and ArcheBuddy - and I am missing the "me" object.
I want to read the x, y and z coordinates using me.x
But VisualStudio does not recognize the me object. What am I doing wrong?
ArcheBuddy.Bot.Classes is imported. I can access other object there, too.
Log("test"); works e.g.

Best regards,
Benninger

 

[Benninger]

[...]
Imports ArcheBuddy.Bot.Classes
[...]
Namespace DefaultNameSpace
   Public Class Routebuilder
      Inherits Core
[...]
      Public Sub PluginRun()
         Log("START")
         Do
               Log(Me.x, Me.y, Me.z)
            Application.DoEvents()
            Thread.Sleep(1000)

         Loop Until [...]

In the "Log" part it is said, that x,y,z is not a member of Routebuilder.DefaultNameSpace.Routebuilder

 

[Out]

vb casesensetive?
maybe you should try
Log(me.X + " " + me.Y + " " + me.Z);

 

[Benninger]

Unfortunately that does not help
VB is not case sensitive
even Log(me.x) does not work,

To which class does me belong?

 

[Aeon]

Unfortunately that does not help
VB is not case sensitive
even Log(me.x) does not work,

To which class does me belong?

Try to transition to C#. VB is old.

 

[Benninger]

Try to transition to C#. VB is old.

Sorry Sir, that is not an answer, but bullshit.

If I reference to the ArcheAge.dll I reference to an IL dll - nethertheless if I use vb.net, c#, F# or whatelse
If I compile my project I generate an IL dll used by the bot - nethertheless if I use vb.net, c#, F# or whatelse

What is that for an argument "VB is old"? Do you only drink wine from 2015? VB.net supports .NET-FW 4.5.1 (and 4.5.2) and is in a current state.

 

[Aeon]

Sorry Sir, that is not an answer, but bullshit.

If I reference to the ArcheAge.dll I reference to an IL dll - nethertheless if I use vb.net, c#, F# or whatelse
If I compile my project I generate an IL dll used by the bot - nethertheless if I use vb.net, c#, F# or whatelse

What is that for an argument "VB is old"? Do you only drink wine from 2015? VB.net supports .NET-FW 4.5.1 (and 4.5.2) and is in a current state.

I agree, but VB is just bad as a language, hard to maintain, doesn't have any structure, simply ugly

 

[Benninger]

I agree, but VB is just bad as a language, hard to maintain, doesn't have any structure, simply ugly

But for me VB.net has a very big advantage: I am more familiar with it

It might be a name problem? The "this" in c# is "me" in vb
Soooo: Log(Me.me.X) works
LoL

VB is just bad as a language

Okayyyy...

Thanks for giving the idea for a new approach!

 

[Aeon]

But for me VB.net has a very big advantage: I am more familiar with it

It might be a name problem? The "this" in c# is "me" in vb
Soooo: Log(Me.me.X) works
LoL


Okayyyy...

Thanks for giving the idea for a new approach!

You can jump to C# pretty quick, despite being more familiar with VB.NET I'm primary a web developer, got it within days.

lol very possible yeah! And no prob, I was just telling from experience, had some bad times with VB back then.