DaveMcW wrote:

Code: Select all

local tiles = {}
for x = 1,10 do
    for y = 1,10 do
      table.insert(tiles, {"grass",{x,y}}
    end
end
set_tiles(tiles)

That still won't work without "name" and "position" as keys.

Emmm... using them in cycle will not work? for x = 1,10 do for y = 1,10 do set_tiles({"grass",{x,y}}) end end From LuaSurface::set_tiles : Note: It is recommended to call this method once for all the tiles you want to change rather than calling it individually for every tile. As the tile ...

LuaSurface::set_tiles

Bizobinator wrote:Is there something wrong with my syntax? Does the if statement have to be outside of the

Code: Select all

data:extend

?

Yes.

I'd rather not add to the button spam. there's way too much of that already. Then find a different way of letting players change things around, like a key binding or whatever. The reasoning behind desync for any print function eludes me. That'd mean a whisper message should also cause desync. The m...

Well, having different settings for different people is a great way to cause desyncs, yes. Everyone needs to agree what everyone else is printing to the console. Maybe use an in game GUI that people can click to change their settings in a way that stays synchronized across clients. Then instead of u...

So how about

Loewchen wrote:I assume you started the map with mods. Try

Code: Select all

/c game.forces.player.recipes["sulfuric-acid"].enabled=true

Keep in mind that you will not be able to get achievements from now on.
If this does not do it, post the save.

layers needs to be a table of tables. You're just missing some {}.

Something like
(adjust player numbers to taste)

This already breaks in single player after a few seconds with
(when commenting out the modded ores so it starts at all.)

Proxy wrote:

prg wrote:

Proxy wrote:I already Removed it from all of those Files.

You modified the base game files?

Yes.

Don't. This will only cause sadness when updating the game or trying to play with other people. Make a mod and set stuff to nil that you don't want to see in the game anymore.

Proxy wrote:I already Removed it from all of those Files.

You modified the base game files?

You just use ingredient.amount instead of ingredient[2] in the second case.

Try math.floor() for the conversion problem.

How about you fix the cause of the desync then? If it's caused by the base game, file a bug report. If it's caused by a mod, complain to the author. If it's caused by a piece of code you wrote yourself and have no idea how to fix it, ask in the modding help forum. If you could disable desync reports...

Unzip all the mods and search for the string "xlarge-equipment-grid". It must be mentioned somewhere.

Chocolatetthunder wrote:wow that is crazy, here i was not wanting to post bugs from the scenario because I thought it was just some shitty code we wrote.

If your shitty code results in a segfault/assertion failure/uncaught exception/anything else that produces a stack trace, file a bug report.

In a temporary directory, do the Windows equivalent of

i can't find anything called "low-density-structure" ANYWHERE in any file... is it hard-Coded? data/base/prototypes $ grep -n low-density-structure -r . ./item/item.lua:781: name = "low-density-structure", ./item/module.lua:116: "low-density-structure", ./technology/te...

Code like
is simply the easiest way of iterating over all elements of a table. This is the normal way in Lua. There's also a numerical for loop, but it doesn't make this any easier.