ParticleEmitter/Emit has a misspelling and thus broken link in the first sentence of the description:
The Emit method will cause the ParticleEmitter to emit the given number of particles similar to how ParticleEmitter.Rate does on ParticleEmitter/Enalbed emitters.
ParticleEmitter/Enalbed should be ParticleEmitter/Enabled
Although it’s a minor edit, this mention makes ALL the difference in understanding data limits in the DataStore.
Nowhere in the official DataStore documentation is it clear whether the 4Mb limit is for the entire DataStore (summing all keys), per scope, or per key.
This raises a lot of doubt (as I’ve had so far), where I just confirmed this by finding the announcement of the increased limit to 4Mb, where it mentions that it’s ‘per-key’:
As programeow mentions in his/her post, you wrote in the PreloadAsync it only receives instances. But, it clearly can accept URIs like in the example at the bottom of the documentation.
Also, confirmed in this 2017 post, it should accept image URIs
I am unable to create a thread in this category so this is my only option
The example usage of GetRangeAsync is incorrect
function PrintAllKeys(map)
-- the initial lower bound is nil which means to start from the very first item
local exclusiveLowerBound = nil
-- this loop continues until the end of the map is reached
while true do
-- get up to a hundred items starting from the current lower bound
local items = map:GetRangeAsync(Enum.SortDirection.Ascending, 100, exclusiveLowerBound)
-- print all keys retrieved in this call
for _, entry in ipairs(items) do
print(item.key) -- this line is using a variable that doesn't exist
end
-- if the call returned less than a hundred items it means we’ve reached the end of the map
if #items < 100 then
break
end
-- the last retrieved key is the exclusive lower bound for the next iteration
exclusiveLowerBound = items[#items].key
end
end
The line with “print(item.key)” uses the variable “item” which doesn’t exist anywhere in the example. There is also no documentation on how the returned array is formatted which is (from my knowledge):
the GetNameFromUserIdAsync() API reference code example shows the incorrect code example it shows the " Playing in Third Person" code sample instead of the " GetNameFromUserIdAsync" code sample. Please fix it if you have the ability to.
In “An adornee what it shows up on”, there should be an “is” between “what” and “it”. I think there should also be an s at the end of “require”, the second word in the sentence, though maybe the correct fix would be to make SelectionBox plural. I think there should also be a comma after “objects” in the first sentence.
Currently, it says that the rotations are applied in Y, X, Z order. It should instead say that rotations are applied in Z, X, Y order because CFrames multiply from the right.
The function table.getn() shouldn’t be in the documentation if it’s deprecated (at least add a comment that it’s not working). Btw, why on earth is it deprecated? What’s more common than getting the length of a table??