SUOLootSub

[Cerveza]

I propose that we put together a sub routine to loot items. It would then be very easy to include in various farming scripts.

Here's my thought for the sub.

gosub SUOLootSub {item ID's} {container to loot} {destination container} {ignore loot container YES/NO}

To use it in a script you could use something like...

Code: [Select]

finditem YFM G_2
if #findCnt > 0
  gosub SUOLootSub POF #findID #backpackID YES
Just a down and dirty loot sub.

Code: [Select]

sub SUOLootSub
namespace push
namespace local SUOLootSub
set !loot %1
set !source_container %2
set !destination_container %3
set !ignore_container %4
finditem !loot C_ , !source_container
if #findCnt = 0
  {
  namespace pop
  return
  }
...
...
...
namespace pop
return
Maybe include Neo's safe drag drop

Thoughts?

[UoLugnutz]

I think a looter like this would be great. Been slowly updating my Leather farmer to a more generic Sampire hunter and the looting part needed a lot of work next and an idea like this is perfect.
One option I would like to see is to search for multiple corpses but that's really not part of the Sub but more part of the script I guess.
Anyways i m doing tonnes of resources farming for points and can test as needed.

[camotbik]

Just interested, what is the point of using name spaces in a looter? I mean would you run it in a separated window or what?

[Cerveza]

Namespace is a way to control variables in subs.

[camotbik]

Ok, just wondering, could you give me an example for something i could not do with out namespaces working in a 1window script?

[Neo]

Ok, just wondering, could you give me an example for something i could not do with out namespaces working in a 1window script?

Using local namespaces are pretty common in 1 window script... I use them in everything I write nowadays...

It's simply easier to organize and control the variables you use, that's all...

And also, it would make it easier to add new subs with new stuff to that script, even if it's someone else who's adding new things, not having to worry about conflicting var names...

Just my view on this of course...

[DPeterson]

Ok, just wondering, could you give me an example for something i could not do with out namespaces working in a 1window script?

This is about the best example I could envision.  Notice I set the !var to blue inside the namespace.  But on the other side of the namespace the !var still shows as green.  That's what namespaces are for.

Code: [Select]

set !var green

namespace push
namespace local !var
set !var blue
namespace pop

event sysmessage !var
halt

[camotbik]

Well but what is the purpose of this? I mean, you could use set, with even taking less space than with namespaces ( AND DO THE SAME THING!!!! )

Code: [Select]

set %var green

set %old_var %var
set %var blue
set %var %old_var

event sysmessage %var
stop


[Cerveza]

It's a way of controlling your variables more. You can use the same variable name for two different things by using namespace.

Code: [Select]

set %my_name Cerveza
msg %my_name $ ; returns Cerveza

namespace push
namespace local IMPOSTER
set %my_name NOT Cerveza
msg %my_name $ ; returns NOT Cerveza
namespace pop

msg %my_name $ ; I'm Cerveza again, yah!
halt

[Crome969]

I never used Namespaces in easyuo but i think its a good thing when you want consider Cases with using the same !var names.

[DPeterson]

Well but what is the purpose of this? I mean, you could use set, with even taking less space than with namespaces ( AND DO THE SAME THING!!!! )

camotbik, but without namespaces if you tried to use another persons sub in your script, you'd have to go through their code and make sure you both didn't use any of the same variables...  when you write subs for others to use, if you use a namespace to encapsulate  your code in the sub, and return your result, other's don't have to worry about your code, it's just drag and drop with your own code.  Even if it uses the exact same variables they wont interfere with each other.

[Crome969]

I only know namespaces from C# and Java and they have a different manner.
But the base Idea of Namespaces is not bad. Unlucky it would be when the other script using namespaces as well with same namespace using. Then you are on the same thing as without. Or may i be wrong?

[TrailMyx]

The main reason I use namespaces is to separate my variable names from others that might be used in a script.  That way, if I use a generic variable !test in different instances, the variable value will not get polluted or unintentionally changed in another section of code.

Another useful idea for namespace storage is for multidimensional arrays.  Take a look at this code so you can see how the data is "encapsulated" within each namespace:

Code: [Select]

; set up your times tables
for %x 1 12
{
  for %y 1 12
  {
    set %times %x * %y
    gosub AddToArray times_table %times %x %y
  }
}

gosub GetFromArray times_table 11 12
display ok 11 times 12 is , #SPC #RESULT

gosub GetFromArray times_table 5 7
display ok 5 times 7 is , #SPC #RESULT

gosub GetFromArray times_table 8 9
display ok 8 times 9 is , #SPC #RESULT

stop
; %1 = Arrayname
; %2 = Value to add
; %3 = index 1
; %4 = index 2
; ...
sub AddToArray
  namespace push
  namespace local Array , _ , %1
  set !var
  for !index 3 %0
     set !var % . !index , _ , !var
  set ! . !var %2
  namespace pop
return
; %1 = Arrayname
; %2 = index 1
; %3 = index 2
; ...
sub GetFromArray
  namespace push
  namespace local Array , _ , %1
  set !var
  for !index 2 %0
     set !var % . !index , _ , !var
  set #RESULT ! . !var
  namespace pop
return #RESULT


[Cerveza]

I make it write my name, TM makes it map a trajectory around 6 planets.

[TrailMyx]

I make it write my name, TM makes it map a trajectory around 6 planets.

Everyone would be disappointed if I didn't do that.