Results 1 to 3 of 3

Thread: GUID assignment is not fast enough

Threaded View

Previous Post Previous Post   Next Post Next Post
  1. #1

    GUID assignment is not fast enough

    Suppose we have an infinite bag that spams tokens and global empty list a, then

    for i = 1, 10 do
        a[i]= bowl.takeObject({})
    will print 10 identical guids. However, if you just save token objects into a and access it later

    for i = 1, 10 do
        a[i]= bowl.takeObject({})
    Some other function that are called much later
    for i = 1, 10 do
    will correctly print 10 different guids.

    It seems that game spawns 10 tokens at the same time and need more time than script to reassign guids.
    Last edited by Sowiks; 03-07-2017 at 02:10 PM.

Similar Threads

  1. nil GUID
    By JHolder84 in forum Scripting
    Replies: 2
    Last Post: 04-06-2017, 10:06 PM
  2. takeObject() GUID bug or intended behaviour?
    By Kronark in forum Scripting
    Replies: 3
    Last Post: 02-16-2017, 09:28 AM
  3. Copy text guid
    By Crazy in forum Scripting Bug Reports
    Replies: 1
    Last Post: 02-14-2017, 09:22 AM
  4. Sorting a Deck Causes it to Have a New GUID
    By urenoiro in forum Scripting
    Replies: 8
    Last Post: 10-31-2016, 10:59 PM
  5. Replies: 11
    Last Post: 12-22-2015, 12:55 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts