Logic World News

Welcome back to another Logic World Wednesday! We’re back from the holidays, and the push for release is underway.

[h2]Checkerboard World - Jimmy[/h2]
The world you’ve been seeing in the LWW videos has been sort of a placeholder. The ground was completely static, with no customization whatsoever.

This week I’ve begun an overhaul of the world, starting with a lovely ground shader. The shader supports custom colors, as well as dual-color checkerboard patterns.



When you create a world with a grid ground, you’ll be able to choose the color or colors used and the grid size. It’s worth noting that Logic World will support several different world types, and mods will have the ability to add world types. But that’s a topic for a future LWW :)

[h2]Modding API Consolidation & Documentation - Felipe[/h2]
Over the holidays I’ve been working on documenting the Logic World mod API, known as LogicAPI. This documentation is done with XML comments in C#. When coding mods, Visual Studio will show what each method and class does while you’re typing. We are also going to upload a generated static site containing all of the documentation over at docs.logicworld.net. This is a preview of how it will look:



This site is generated by DocFX, and it will contain all the aforementioned code documentation as well as some concrete concepts that may require explaining.

We are also going to have a wiki at wiki.logicworld.net, which will contain broader modding guides and tutorials, as well as some other non-modding related info.

[h2]Tons of cloud stuff - Felipe[/h2]
I have also been doing a big revamp of our cloud architecture:

• We have migrated from having a single server to having two: Phobos and Deimos.
  
• Migrated from a monolithic architecture to a microservices one, which means that we now have a small service for tasks like emailing, logging, storage, etc.
  
• Migrated from regular Docker to Docker Swarm, allowing us to deploy these services very easily and scale them up by changing a single number in the configuration file. This will let us easily scale up the server to meet the demand if we find the need to do so.
  
• Migrated from Caddy to Traefik as our edge proxy.
  

Initially these services were written in C# just like the web application is, however, when migrating to Traefik I realised that every single application we were using in the server was written in Go. Go is a language that’s widely used in reliable and widely used software like Traefik, Caddy and Docker. This sparked an interest in Go inside of me, so I spent a few hours learning this new language and rewriting the logger service. This service is the simplest, all it does is receive messages from all the services and log them to the database, so I thought it would be the perfect opportunity to dip my toes in Go. When I was done writing this I noticed that the service was using just a fraction of the memory that the C# service was while being a lot more CPU efficient. To sum up, 5 out of the 7 services we currently have are written in Go.

Don’t get me wrong, I still love C#, however it’s become clear to me that Go is much more tuned towards web server-side software development.

[h2]Refined Building Mechanics - Jimmy[/h2]
I’ve done a pass of our basic building mechanics to ensure they are consistent, intuitive, and easy to use. Most notably, I’ve removed the Rotation Lock mechanic; the lock is now always on. Rotation Lock was sort of an awkward and unintuitive mechanic. It was sort of a holdover from when I was trying to copy Minecraft’s building mechanics, back in 2017. But Logic World has grown up a lot since then.

To help communicate the new objective nature of rotation, I’ve added a little compass rose to the UI with a pointer for the object placement rotation direction.



Notice the pointer above the hotbar on the left. As the inverter being placed rotates, so does the pointer.

---------------------------------------------

If you’d like to receive an email each time we post one of these blogs, you can sign up for our newsletter. Be sure also to join the official Discord and follow @LogicWorldGame on twitter.

See you next Wednesday!

View this post on logicworld​.net. More Logic World Wednesdays

https://store.steampowered.com/app/1054340/Logic_World/

(this blog was originally posted 2019-12-18)

Welcome back to another Logic World Wednesday! This is our last post before the holidays, and we’ve got some real goodies for you this week.

[h2]Draggable Colors and More - Jimmy[/h2]
Logic World’s color picker is something I keep coming back to and tweaking, but this week I think I’ve finally settled on its final form. I’ve shifted the menu elements around so that the HSV wheel is bigger, and I’ve packed the sliders together more closely to save space. I’ve also removed the ability to hide blocks of sliders; dynamically resizing the menu was causing some issues, and I literally never used the option anyway.

I’ve also added a number of new features to the color picker, including the much-requested draggable saved colors. You can see them all in this video:

[previewyoutube][/previewyoutube]

[h2]Mod Hooking - Felipe[/h2]
This week I’ve been working on the hooks system for mods. Hooks provide a way for mods to listen to game events, like placing a component or a wire, and optionally cancel it or modify it. Right now hooks are implemented through “handler” classes, which are abstract classes that contain a virtual method for each hook. Mods can then make classes that inherit a specific handler class and then implement any hook methods that they want.

This is an example of how a mod’s handler class may look like:

public class MyHandler : WorldHookHandler
{
    private int Counter;

    public override void OnPlacingComponent(PlacingComponentEventArgs args)
    {
        bool cancel = Counter++ % 2 == 0;

        if (cancel)
            args.Cancel();

        LConsole.WriteLine($"A user is placing a component of type {args.ComponentType.TextID}, cancel: {cancel}");
    }
}

This hook would stop the player from placing a component every second time they tried to. Handy for annoying your friends.

[h2]Player Identification - Felipe[/h2]
Up until now players in the server were identified only by a username they choose. While this works fine, if someone was to connect with the same username as you they would be able to impersonate you. Now players are instead identified by their logicworld.net user ID, which is unique to your account. You can sign in to the game with your logicworld.net account, and in the Steam version, you’ll be automatically logged in to logicworld.net with Steam.

Servers will also have the option to turn on “offline mode”, reverting back to the username identification system. This is useful in case logicworld.net goes down, as an offline server doesn’t need to verify the players’ identities.

[h2]Yet More Unexciting Code Work - Jimmy[/h2]
Last week I spoke of two very cool features I was working on, and I’ve continued that work this week. Unfortunately, I didn’t finish in time for LWW, but most of the architectural groundwork is now laid.

---------------------------------------------

Thanks for reading! We’re going to take a two week break over the holidays, during which time we intend to start beta testing. Logic World Wednesdays returns January 8.



If you’d like to receive an email each time we post one of these blogs, you can sign up for our newsletter. Be sure also to join the official Discord and follow @LogicWorldGame on twitter.

See you next Wednesday!

View this post on logicworld​.net. More Logic World Wednesdays

https://store.steampowered.com/app/1054340/Logic_World/

(this blog was originally posted 2019-12-12)

[h2]Better Saved Colors - Jimmy[/h2]
The old system for saving colors, and managing your saved colors, just wasn’t working; it was too complex and too clumsy to use. This week I’ve redone it, using the same UI as saving Display configurations.

[previewyoutube][/previewyoutube]

I’ve also added a button for sorting your saved colors - which is a surprisingly complicated thing - and a button for choosing a random color.

[h2]Website Work - Felipe[/h2]
I’ve been working on some minor website QoL adjustments:

• Post embeds on Discord, Reddit, etc are much nicer. before, after
• The Facebook link has been smited from the site. More info
• When logging in you will now be redirected to the page you were previously in
  
• Comments will now be counted recursively in the comment section
  
• All notification emails will now contain the reason why you got them
  

I’ve also been working on an updated “About” page for the site. This new page tells you a bit about us, and it lets your see our faces (to be revealed).



Unfortunately I haven’t been able to deploy these changes for this LWW (LWT?), but you can expect to see them shortly.

[h2]Unexciting Code Work - Jimmy[/h2]
I spent most of this week laying the architectural groundwork for two very cool features. I was really hoping to show at least one of them off today, but they just didn’t get finished in time.

These two features are the final building mechanics for Logic World, and they’ll complete the set of tools you have to manipulate the world.

---------------------------------------------

If you’d like to receive an email each time we post one of these blogs, you can sign up for our newsletter. Be sure also to join the official Discord and follow @LogicWorldGame on twitter.

See you next Wednesday!

View this post on logicworld​.net. More Logic World Wednesdays

https://store.steampowered.com/app/1054340/Logic_World/

As we discussed in a previous LWW, mods’ source consist of up to three Visual Studio projects as well as the assets and libraries you want to include. This week I’ve been working on a tool that lets you create these projects from a template and upload the source for it to be compiled: Logic Maker.



The UI is a WIP, it currently has no styles at all.

Logic Maker is meant to be a tool to aid you in creating and developing mods. While it isn’t necessary (you could for example just copy a template project), by using the tool you can create your mod solution with the features you want, and it will automatically output the minimal code to get your mod running.

Logic Maker can be used in one of two ways: through the UI or through the CLI. The UI is made with [Avalonia](https://avaloniaui.net/), which means that it’s completely cross platform and it will look the exact same way on Linux, Windows and MacOS. On the other hand, the CLI will let you perform the same actions as the UI, but with arguments instead of buttons:



In the future I’d also like for Logic Maker to let you build the project using the same Docker image that logicworld.net uses. That way you can locally verify your mod before you upload it.


The menus in Logic World have many small, circular buttons with icons on them. When you’re like me and you programmed all those buttons yourself, this isn’t a problem, but if not, it can be a little confusing. What does the button with a gear on it do? What does the button with a folder on it do?

Back in the Dark Ages of Last Week, there was no way to know. That’s why this week I’ve developed a system for displaying more detailed information about a button when you hover over it.



The size of the hover text is configurable, as is the delay between mousing over a button and the hover text appearing. You can also disable hover tags entirely.


When you’ve saved a board, you can view an interactable in-game preview of the saved board in 3D. This week I’ve upgraded the camera controller used in these previews. It is now much more configurable, and it now supports moving the pivot position by holding right click and moving the mouse. This feature was already present in the web previews, which you see when you share a board online - interactive demo of that here.

I’ve also added a button to reset the camera position, and saved boards now remember where you had the camera when you saved them.

Finally, I’ve refactored the system for rendering the models so that it can also render a static image of the models. This will allow me to generate thumbnails for saved boards.


I’ve spent most of this week going through the game and fixing various bugs that have cropped up. Multiplayer bugs in particular have been getting my attention. The game has been through several major code architecture upgrades in the past few months, so there were a fair number of these.

Now, though, Logic World has reached a very stable state. The core gameplay is smooth, incredibly fun, and mostly without issues. It was important that I go through and clean it up this week, because we intend to start beta testing soon.


Previously the website was using the ASP.NET Core 2.1 framework, which runs on .NET Core 2.1. However .NET Core 3 came out not long ago, so I’ve been working on upgrading to ASP.NET Core 3.1. This update comes with a ton of performance upgrades, which means that logicworld.net can now handle 5x the amount of concurrent users!

---------------------------------------------

If you’d like to receive an email each time we post one of these blogs, you can sign up for our newsletter. Be sure also to join the official Discord and follow @LogicWorldGame on twitter.

See you next Wednesday!

View this post on logicworld​.net. More Logic World Wednesdays

https://store.steampowered.com/app/1054340/Logic_World/

Oh yeah, it’s all coming together.

Logic World is nearing completion. All the various parts of the game are coming together to form a complete product, and we couldn’t be more excited about it.[/size]


This week I’ve finished the new Display Menu; you can now save and load configurations for displays, making it easy to create multiple displays with the same color scheme.[/size]

[previewyoutube][/previewyoutube]

The completion of this menu marks a significant milestone: it is the last new menu for editing a component. Previously I’ve made menus for:

• Circuit Boards
  
• Switches
  
• Labels
• Singers
• Drums
• Chairs
• Delayers
• Buttons
• Keys

[/size]
Since even before we announced Logic World, “make a menu to edit component [x]” has always been somewhere on my todo list. And now they’re all done.[/size]


The Logic World game client doesn’t have any logic at all, it’s all handled by the server, which means that the client by itself can’t really do much. This server is a standalone .NET Core 3.0 project, which means that it compiles into its own executable. Logic World’s singleplayer mode is based on an integrated server, like Minecraft, which boots up every time you want to load a world.

This week I’ve finished the work of integrating the server with the client. The client can now spin up instances of the server and connect to them. This is an important milestone towards shipping the game - now, you can actually play it without starting up a separate server program in the background.


Now that the integrated server is working, I’ve been working on menus for using it in singleplayer. The Sandbox Menu uses the same code as the Save Board and Load Board menus, so each world can have a title, a description, and a series of tags for sorting it. The list of saved games can also be searched.



This menu is still a WIP, you’ll see a video with it next week![/size]


I’ve made a fancy animation with our logos that plays when the game starts up.[/size]

[previewyoutube][/previewyoutube]

---------------------------------------------

If you’d like to receive an email each time we post one of these blogs, you can sign up for our newsletter. Be sure also to join the official Discord and follow @LogicWorldGame on twitter.

See you next Wednesday!

View this post on logicworld​.net. More Logic World Wednesdays

https://store.steampowered.com/app/1054340/Logic_World/