error(LocalisedString) already works as far as i know, it was a part of my old hack for translating things in the debugger before localised_print!

Edit: just tested, apparently it's only translated in control, wonder how i never noticed that!

/c game.player.cursor_stack.set_stack('blueprint-book') game.player.cursor_stack.get_inventory(defines.inventory.item_main).insert('blueprint') produces an empty book, rather than the expected book with one print. Inserting does appear to work when there is already a print in the book and there are...

minor update: the captcha now seems to not appear on at least the first attempt so if your creds are good tools work again!

Another update seems to have added a captcha, totally thwarting my attempts to have automated uploading tools. Please can i have a real upload api?

For anyone else updating tools: the new login process is picky about the referer header on the submitted login form too, in addition to the form content (including csrf token of course)

The upload itself appears to work as-is.

I've just noticed the portal update broke my mod uploader (in the vscode mod debugger extension ), and thought I might as well ask for some real docs/support this time before i start reverse engineering again to update it! Is there (or can there be) a documented API way to get logged in for uploadin...

Minor follow up now that this is in resolved: We've changed the way the debugger `log()` hook works to no longer allow constructing this crash with the latest factorio(0.18.34) and debugger(0.18.25) when both are updated (if either is old it'll still use the old way).

Is this a horrible idea, now that we can run Factorio under a debugger? =) if mods['debugadapter'] then log("Creating " .. new_item_name) end Actually, would it be possible to do something like have a `debug_log` function that only gets turned on when Factorio has failed to load, and on the error d...

I'll dig into this more shortly, but yes, it is almost certainly caused by the debugger doing a little bit of evil to convert log() calls to debug console events with clickable links to source. You can disable this functionality for now by setting "hookLog": false in your launch.json, which should a...

I also looked into this a little and it seems to me that what is happening is that when the InfiniteRectangleIterator is being re-initialized for a new call to iterator(), it sometimes takes a path that leaves ->position on it null, but does *not* set the ended status, which later leads to that null...

A more useful list would be how many mods use only script_raised vs how many still raise on_x. Most of the ones using script_raised_ don't do anything else, so it does indeed look like it's a before/after split and just old mods not fully updated to raise the new events. Within the ones using scrip...

If I've understood correctly, the proposal has basically evolved into "raise_event can only be used for script_raised_* and custom mod events", which sounds pretty good to me.

I also happen to be spending a lot of time in the VM's guts along the way, so I'm looking for other unchecked assumptions that need testing as I go too, but most of the ones I've found so far are pretty boring (posila mentioned a few of the ones that seemed interesting and got some work). We also lu...

Aaron, the problem with restricting to bytecode produced internally is that i'm currently working on a project that is essentially a standalone compiler for a slightly extended language (things like ?. and += and type annotations in source rather than comments) that will ideally compile to lua52/fac...

After some digging, this same crash is also reproduced by `/c game.print(game.player.entity_copy_source.valid)` while the current player is dead, even without my debugger attached, so it looks like this is a base game bug that I simply revealed by attempting to access every possible property. A more...

...a special mode which allows a selected mod to hook all the Lua instances Factorio creates, at the cost of disabling multiplayer and only allowing one Instrument at once. doesn't mean ONE mod? One mod that's doing the instrumentation, not one mod that's being instrumented. Yes, exactly - one mod ...

vedrit wrote: ↑

Sun Mar 08, 2020 9:43 pm

Gergely wrote: ↑

Fri Mar 06, 2020 4:29 pm

What if we need to... you know... test if things are multiplayer safe?

Or if you're testing a mod that requires another mod? Like an add-on to Bob's or Angels

Then you enable those mods too? the *debugger* is the one running in instrument mode.

What if we need to... you know... test if things are multiplayer safe? Then you turn off the debugger for a while. For the most part if you write correct code in the first place it just is mp-safe. I'm hoping to add some static analysis tools eventually to detect many kinds of mp-unsafeness in adva...

Since we know have access to `debug` with `--instrument-mod`. Can we also get access to change `package.cpath` and `package.path`, it would make creating a remote debugger so much more simple :) we've had access to `debug` all along it turns out, Instrument Mode is a whole other set of super-powers...

Since we know have access to `debug` with `--instrument-mod`. Can we also get access to change `package.cpath` and `package.path`, it would make creating a remote debugger so much more simple :) we've had access to `debug` all along it turns out, Instrument Mode is a whole other set of super-powers...