Same behaviour noted for me as well using unicode geometric shapes (https://www.compart.com/en/unicode/block/U+25A0): Many unicode characters are replaced by spaces. I replicated this behaviour in the en, fr, ko, and zn-TW locales. For the ru locale I got "blank boxes" instead. blank box.P...

No data stage access for my use case, but I appreciate the follow up.

A continuation of https://forums.factorio.com/viewtopic.php?f=11&t=60767&p=366009 It seems that this was half-resolved: the locale data seems loaded, just unavailable to error while it is available to log. 3 control.luas for 3 test runs: 1) log in control init log({'apocalypse.apocalypse_alr...

Some extra information: though this crashed the install on my PC, this did not crash a headless server and instead generated the following error: Cannot execute command. Error: [string "game.surfaces.nauvis.destroy_decoratives()"]:1: bad argument #0 to 'destroy_decoratives' (Wrong number o...

Control.lua contains only the following: commands.add_command('name', 'help', function() return end) And `/help name` gives this as output (it was run twice in the image): https://cdn.discordapp.com/attachments/478251841184989186/550811628900319243/unknown.png An attempt was also made to use a Local...

No save file attached, you can get this result starting a regular new game.

Running the following crashes the game: /c game.surfaces.nauvis.destroy_decoratives()

Step to reproduce: query get_quick_bar_slot > 100 in whatever way you find easiest and observe crash.
/c local crash_now = game.player.get_quick_bar_slot(101)

The pic was taken with the redmew scenario which is quite large, and has a lot of framework which would make pinpointing the issue a chore. I'll upload a save with the barest code to clearly demonstrate the majority of the issue, and a save with the full redmew scenario for completion. In the redmew...

word_wrap seems to be acting in an inconsistent and unexpected manner. It is wrapping things far too short, but the wrapping behaviour changes when the string is being changed in vivo. Further, the wrapping behaviour reverts to being aggressive when you change away from it. Initial wrapping is aggre...

Having a water-only map for the purposes of scenario-based world generation is great since it gives you a map in its (nearly) most basic form: everything is the same tile and the only entities on the map are fish. It seems the switch from 16 to 17's map generation has closed off that possibility and...

Found out today that you did indeed change the logic of the lua version and wanted to give my thanks.
(Was hard to be sure since this issue could have been marked resolved when `inspect` was removed)

We ended up finding out what the issue with serpent is: block() chokes on large numerical table keys Is fine. /c game.print(serpent.block({[2147483646] = true, [2147483647] = true})) Is not fine. /c game.print(serpent.block({[2147483647] = true, [2147483648] = true})) 2147483647 being int32.maxValue...

Heya, A BP got uploaded/imported in MP and was corrupt (blank?). The server itself didn't realize this, nor did connected clients, but when new clients joined, they detected the fault and their clients corrected the issue... locally. I'm not sure the exact trigger, but when client and server disagre...

I don't mind adding it for debug reasons but this statement concerns me: you should *always* know what objects you're passing around are. If you've written your code such that you've lost that information then you're written incorrect code. Maybe I'm confused. Isn't that what debugging is for? Trac...

The use-case is debugging. You have some kind of LuaObject arriving somewhere and it's not what you expect. Knowing the type would help with knowing where it came from/where things are being contaminated. Currently we use: function Debug.object_type(object) local obj_type = type(object) if obj_type ...

Looking at the output from `help()`, there seems to be identification of the object type. Would it be possible to make these accessible? Being able to see the object type would be very helpful with debugging. is_player() is cool, but also oddly specific considering there are 76 LuaObject types in 0....

Heya, Currently, everything wants a position, whether it's an actual Position or a ChunkPosition. It would be nice if parameters that wanted a ChunkPosition would be renamed to indicate that they want a ChunkPosition. In the overview of classes (https://lua-api.factorio.com/latest/Classes.html) and ...

You can just use serpent.block

The reason I use inspect for debugging now is serpent.block's previous failure.



Thanks for addressing the bug I reported though.

The following code block in control.lua will run happily. However it will leave Factorio in a state where if you process the wrong bit of data, if you try to restart, or if you just try to quit to the main menu the game will crash to desktop (usually without a log): local inspect = require 'inspect'...