Search results

Here is the save if you need a second look :cool: https://ufile.io/zgn6i Agree on the challenge thing. There are different kinds of challenges in Factorio worth a try. SpaceX Plus would be a resource-megabase challenge (our current base would not even count as starter base), angel or bobs are a...

Projects overview @asie "Developing an assortment of sandbox-friendly framework and content modules" @dacharya64 "Extending “Light and Shadow” Gameplay and Functionality" @Iaron da Costa Araújo "Event Recording Feature" @Inei1 "Improving the Server Facade" @jellysnake "Tower Defence Gameplay...

Server is up again with a new (peaceful) map :thumbsup: IP and password are available via pn to me or cervator :cool: I will wait a bit this time before building spaghetti to give the US people a chance to join first in 10-12 hours or so ;)

I think I will start another server for this weekend, maybe with peaceful settings this time for more building and less turret creeping :) Begin will be probably in 14-16 hours from now.

Sad to see you leaving but comprehensible due to some if the bigger organization discussions which costed everyone a lot of energy. Maybe you find a good chance to return to more pleasing tasks - like this thread title "Happy coding!". Was also nice to meet you in Zürich and to repeat myself...

"q" for clearing or picking like a pipette tool, "ctrl" for fast grab/insert and "alt" for enabling the ui overlay are your best friends ingame :)

Small reminder for everyone interested in the game who does not own it yet: The price of factorio will change from 20$ to 30$ at 16th April (https://www.factorio.com/blog/post/016-price-change). It is still pretty cheap for the amount of gameplay the game delivers but as the game has a no-sale...

I like the concept of L&S a lot, promising to see a nice proposal :thumbsup: The timeline looks way too stuffed for me though :eek:. I would suggest to start with the bare minimum which is fun like capturing a flag on a flat plane and let the player with the flag walk a bit slower or so. Then...

I will announce once we repeat it and with more time ahead then ;) Last save game, latest version is 0.16.31 due to a recent patch: https://www.file-upload.net/en/download-13037414/terasology_event_1.zip.html

Actual state of the map and a list of noteworthy points: We have the first 4 science packs running Power by solar and steam, nuclear is in progress (uranium processing takes ages) The surrounding area is almost secured The starting iron and copper patches are half way empty Nice little uranium...

All on one factory with shared resources, tends to be a fun/chaotic mix. I will send the server login around, lets see what we can build over the weekend :thumbsup:

Server is up and ready for tomorrow, we have a nice little spawn area with almost no stone but some oil ;) Note that the server is running 0.16.30 Beta, you will have to select the appropriate version. For example on steam, open the game properties, then select the branch in the "Betas" tab...

When? -> Saturday 17.03.18 to Sunday 18.03.18, no exact time yet. Server will be closed afterwards, likely on Monday. Who? -> All interested community members. Server will be private so leave a message if you want to participate. What? -> Launching a rocket to space, then another, then...

We still need a single place for our developer documentation ;) I will add a poll for the next two weeks to this thread, then start working on the docs again before GSOC 2018 starts. Overview of existing documentation: 1. Wiki https://github.com/MovingBlocks/Terasology/wiki contains most of...

I gave it a short try this day and tried to add an engine-api project and make core depend on it instead of engine. Did not work that well :unsure: one issue is that engine as project is hardwired in many places. One example is the ModuleManager which spawns engine as module in the constructor...

"engine2" as API layer sounds good, we may even call it engine-api then. A separate project will also force us to touch everything we need at least once :)

My main reason for a single repo is the developer workflow to keep the engine up to date. From the perspective of a developer who checks out the engine repo(s) once, then after 3 months wants to continue and be up to date: In the current state it would be a simple pull on the develop branch. If...

I don't want to say we should do all at once :D What we can do, even without touching the existing codebase: -create a new project engine2 (or a better name) -make PC and the other facades depend on engine2 -make engine2 depend on engine -keep engine-tests as is engine2 would be in a folder...

The v2 branch already includes a lot of features, most of them coming from the actual gsoc. I would like to use this thread for a discussion how the architecture of the engine should look like in v3. My main issue with the current project is the size. Everything is in the engine, all in one...

Im aktuellen Google Summer of Code gibt es ein Projekt für ein besseres Serverinterface von @gianluca_n : https://gianluca-nitti.github.io/GSoC-2017-devlog/