Bablosoft

notreuse Bag

Support

  • E

    How Can We Mask System Timezone?

    Support
    0 Votes
    6 Posts
    428 Views
    R

    Have you been able to fix it? I also got a spoofed timezone when I checked on pixelscan

  • K

    Updating Error?

    Support
    0 Votes
    3 Posts
    275 Views
    m4zuperM

    @korthresh
    What version of BAS are you using?
    What OS do you have?
    Do you use a fingerprint when the problem occurs?
    Does this happen constantly? Just on this page element or on other elements as well?
    How can I replicate this intentionally? Are there any specific steps?

  • S

    How can i save my nodejs variable, to a "BAS" variable?

    Support
    0 Votes
    7 Posts
    1029 Views
    Int64I

    @aryasena

    Before you start the Node.js part, drop helper functions into Tools > Execute Code :

    setGlobalVar = function () { var args = _function_arguments(); var name = Object.keys(args)[0]; PSet("basglobal", name, JSON.stringify(args[name])); }; getGlobalVar = function() { var name = _function_arguments(); var result = JSON.parse(P("basglobal", JSON.stringify(name)) || '""') _function_return(result) }

    Next time, use them in your Node.js code like this:

    await BAS_FUNCTION("setGlobalVar", {"TEST": 2}) var value = await BAS_FUNCTION("getGlobalVar", "TEST") console.log(value) await BAS_FUNCTION("setGlobalVar", {"TEST2": 222222})

    The variable inspector doesn’t see them, but they do exist!

  • S

    notreuse issue

    Support
    0 Votes
    12 Posts
    1379 Views
    GaGG

    Than you might use "global variable" and "OnAplicationStart" function parameter
    maybe to fulfill yourn tasks.

  • E

    I'm struggling to understand "notreuse" on resources

    Support
    0 Votes
    2 Posts
    888 Views
    GaGG

    "notreuse" should be understood in context of THREAD life.
    So if you use "notreuse", it will always use new value from
    resource during 1 THREAD execution. And if it is not used
    same thread will use same resource value during 1 thread
    life cycle.

    You just have to understand how to use BAS for your user case.
    BAS is already preconfigured to handle certain types of problems.

    So propper way to handle your problem in BAS would be as follows:

    Define resource list with your user:pass data in txt or csv format.
    Resource should be "Lines from file" and setting "Use each line
    one time" should be checked, along with "Only read" setting.

    You dont need to convert resource to list, since you want to use
    each line of resource in one thread. Simply parse resource line and
    use user and pass as you need in thread.

    That is how BAS handles such user problems.

    When you convert "Resource to List" it becomes a list suitable to be
    proccessed WIHIN ! THREAD. So in some cases this is desirable behavior.
    For example when you need to cycle through a list in ONE browser instance -
    aka in a single THREAD.

    But your user case means that you need new browser instance - new THREAD
    for each application of your user:pass combination. So you wouuld need to handle
    such behavior with LOOP and to use NOTREUSE, so in each iteration you get
    new line from list. In a word, you can achieve the same behavior if you follow
    default BAS behavior described under 1 and 2.

    So hope that you understood that you simply need to solve given user
    problems according to default BAS behavior.

    @ev0 said in I'm struggling to understand "notreuse" on resources:

    Also, second question: If I create the resource to "delete line" after each use, does it actually delete it? or just remove it from resources available?

    If you use "Delete line after use" resource parameter, the line will be deleted
    only after script is finished or restarted. During script execution lines in resource
    will remain undeleted, but BAS will "know" that those lines are already used and
    ready for deletion (scheduled for deletion), so BAS will delete ALL resource lines
    at once - at the end of script execution or when you forcibly stop the script.
    The developer said that such behavior is intended in order to reduce write-delete
    to local or remote HDD. So such functionality saves your local disk usage and speeds up script execution by not interupting its execution every time line from
    resource needs to be deleted.