SRL Archive - General

Ok guys, we now have the Include Structure. I'll soon setup the svn write access when I have time; for now, you can start working locally. Basically there are 4 files that need to be planned out right now;
ItemInfo.scar , Banking.scar, Debug.scar, Walking.scar.

Remember, the most important thing is to have the plan, as in function name, params, result and description. This will allow us to ask SRL Members to do it, once we open the MSI SVN Forums; This will happen as soon as we have our things planned. If you feel that something is too complicated or complex to explain/ask of SRL Members, then feel free to do it yourself.

- - ItemInfo.scar Working on this: rogeruk
All colors and item information will be loaded from here. Remember to use constants for easier reading and scripting, no strings! If you want to only make one function to load all Items then I suggest two sets of constants:
[php]
const
Tool_Axe = 0;
Axe_Rune = 0;
Axe_Adamant = 1;
Axe_Mithril = 2;
//…
Tool_Pick = 1;
//…
[/php]

- - Objects.scar Working on this: NCDS
This file will be responsible for all the finding. Remember to make it flexible enough for all needs. Remember to also alter the types as you see fit. This file will need to be able to find objets in MS, Inv, Bank and wherever else might be needed.

- - Banking.scar Working on this: Nauman
This will deal with all banking/withdrawal, therefore it'll have to be pretty damn well organized. I would find it lovely if there was a function such as
DoBank(Deposit: TItemArray; WithDraw: TItemArray): boolean;
Which would just deal with everything.

- - Debug.scar Working on this: Rasta Magician
This will deal with all the debugging and progress report functions. Have a look here for what we are aiming for as progress report and a suggestion on how to do it, here.

- - Walking.scar Working on this: marpis
This will be the file in charge of all the main walking routines.
Place -> Bank, Bank -> Place, Lost -> Place;
It should also be able to 'ReCenter':
eg if not FindTree then ReCenter; //walks to the place where he is sure a tree should be, in case he walked away from it



So, who wants to plan out what?

~RM

Well, seeing as Bumblebee said he was interested in the ItemInfo.scar, I guess I can work on Objects.scar, if that's alright. :)

Banking.scar

I'll do the best I can to get you your all in one function ;)

I guess I can do Walking.scar.

I would like to kinda take object and item info, but I guess I can take just one or the other. Either or I have a few functions already made for both so Coh3n if you ever want some help or maybe just let you take a look at a few of my functions. Ill talk to you on MSN or something, I think I have yours :)

Seems like i'll get working on Debug.scar then.

Blumblebee: Contacts thread ;)

~RM

So, shall we start working? I mean, the base functions, core parts, SRL Playerform, types, etc.?

From: Cazax
So, shall we start working? I mean, the base functions, core parts, SRL Playerform, types, etc.?

Indeed we should ;)

/me has started already!

If you need any help with the walking, let me know :)

~RM

From: Blumblebee
I would like to kinda take object and item info, but I guess I can take just one or the other. Either or I have a few functions already made for both so Coh3n if you ever want some help or maybe just let you take a look at a few of my functions. Ill talk to you on MSN or something, I think I have yours :)

Well I'm sure I'll need some help, I'm not the best scripter around, so be prepared for some questions when they come up. And I'd gladly take a look at the functions you have, it'll help me with mine. :)

I can do autocoloring functions and I think someone should plan the mainloop and all other things were build around it. Like this

repeat
  case Players[CurrentPlayer].Integers[CurrentLocation] of
    Loc_EastMine: MiningLoopEast;
    Loc_WestMine: MiningLoopWest;
    Loc_BankEast: Banking(Loc_BankEast);
    Loc_BankGE: Banking(Loc_BankGE);
    ...
  end;
  if SwitchLocations then
    DoSomethingMaybe;
until(False);

Coh3n and Blumblebee are no longer working on these things;
I believe cazax hasn't done much in a while…?
And if I'm not mistaken, NCDS pretty much did the banking already, not sure how active he is now tho?

NCDS, you still up for this?
Cazax, I haven't heard from you in a while?

~RM

I'm still here, just been very busy. Though I can work again. I need some help in setting a path(SetupWalk IIRC) because I need the TPA's first. Without the paths I can't do much.

From: Rasta Magician

And if I'm not mistaken, NCDS pretty much did the banking already, not sure how active he is now tho?

NCDS, you still up for this?

I'm still here, and still ready to work.

Not sure what i can help with. First time ive actually looked at the MSI sections.

So… What do I start with? :confused:

From: marpis
So… What do I start with? :confused:

You need to talk with Rasta to figure out which part your going to be doing.

updated, let me know if anything is wrong or if you'd rather do something else.

~RM

Err, I'll just be lurking around every include and fixing stuff I can fix, if that's OK..?

RM I've been reading through a lot of the functions. I've seen a lot that have debugging for when they are successful but hardly any when they fail which is more important.

For a project such as this should have debugging for the critical functions every step of the way. For example the Object finding and Tool finding you guys have so far. I suggest a debug for every time it fails to find the Object/Tool in each of the finding categories that you have setup. That way if they ALL fail you know and the TItemInfo no longer works and should be updated.

I suggest a set standard or function (which I believe you have already) for debugging to be added to this critical spots. Maybe you were going to add them later idk, just something I've observed so far. ;)

{******************************************************************************}
{ Procedure MSIDebug(ProcName, TheMessage: string; DebugLevel:integer);        }
{ By: Rasta Magician                                                           }
{ Rev: 10                                                                      }
{ Date: 13 Sep 09                                                              }
{ Description: Used for Debugging. Will debug to DebugBox if                   }
{                DebugLevel >= Debug_LevelToDebug                              }
{******************************************************************************}
Procedure MSIDebug(ProcName, TheMessage: string; DebugLevel:integer);
var
  DebugMSG: string;
begin
  if DebugLevel < Debug_LevelToDebug then exit;
  DebugMSG := TheTime+': ';

  try
    DebugMSG := DebugMSG + Players[CurrentPlayer].Name+': ';
  except end;
  
  case DebugLevel of
    //to add some more detail
    Debug_PlayerActions: DebugMSG := DebugMSG + 'Player Action: ';
    Debug_Functions    : DebugMSG := DebugMSG + 'Entering Func: ';
    Debug_SmallDetails : DebugMSG := DebugMSG + 'Detail: ';
  end;
  
  DebugMSG := DebugMSG + ProcName + ': ';
  DebugMSG := DebugMSG + TheMessage;
  writeln(DebugMSG);
end;

Thanks for the advice Narcle :)

Guys, listen to him! I want to see MSI_Debug all around the place! :p

~RM

From: Narcle
RM I've been reading through a lot of the functions. I've seen a lot that have debugging for when they are successful but hardly any when they fail which is more important.

For a project such as this should have debugging for the critical functions every step of the way. For example the Object finding and Tool finding you guys have so far. I suggest a debug for every time it fails to find the Object/Tool in each of the finding categories that you have setup. That way if they ALL fail you know and the TItemInfo no longer works and should be updated.

I suggest a set standard or function (which I believe you have already) for debugging to be added to this critical spots. Maybe you were going to add them later idk, just something I've observed so far. ;)

I have all that stuff in the version of MSI_FindTool I used to test, I just figured it would be annoying to have it everywhere, but after your explanation it does make more sense to have it in.

Its better to have debug everywhere for such a large project. It may take a little more time to add it but it will be less work later on to maintain it.

From: Narcle
Its better to have debug everywhere for such a large project. It may take a little more time to add it but it will be less work later on to maintain it.

That is also why we have several debug levels;)

The most detailed debug levels will only be used when we're actually testing / looking for something that went wrong.

~RM

From: Narcle
Its better to have debug everywhere for such a large project. It may take a little more time to add it but it will be less work later on to maintain it.

You have me convinced. ;)