demodude4u / factorio-fbsr Goto Github PK

Refactor the assembly machine logistics to support a dynamic recipe that changes based on the input

Implement a reddit service that will scan for blueprints, generate images, and reply with an image in /r/factorio. Try to follow the guidelines detailed at https://www.reddit.com/wiki/bottiquette to keep with good standards.

In the following blueprint the belts being braided lose the path after the first underground.

Blueprint to test with

Adding detailed version info to the bot via the git repository would be a nice feature.

Something similar to what i do on my bot would be nice, (Fuzzy/Blurry due to github, click to see clear version)
Layout: *Version*+*Commits Since*-*Branch*-*Commit Short Hash*

The branch and Commit Short Hash link to the appropriate paths on git repository. An example would be like so, assuming that the first commit is v1.0.0, and at the time of creating this issue there are 42 commits.
v1.0.0+41-master-598676b

Demod - Today at 12:22 AM
it doesnt spit out an error if it goes beyond the embed char limit lol (edited)

This is important because I currently do not reload lua data if factorio was updated.

Example: https://pastebin.com/mqxjfirx

This would let concrete be rendered, and other things I may not have remembered.

Upon request of a web interface, return a compressed JSON file containing sprite information that can be used for rendering in any language the client so desires.

This is often used with testing blueprints, so it would be handy to support the entities for visual aid and logistic calculations.

Also add a warning that will notify if there was anything that has a prototype, but could not find a recipe for calculating totals.

This is not as trivial as it appears, as I currently do not support admin commands (owner + trusted roles), and also do not have a database to store preferences per server.

Currently all train stations are grey, even if they are colored in the blueprint itself. Example: https://cdn.discordapp.com/attachments/139677590393716737/324326167647748097/blueprint.png using https://gist.github.com/Bilka2/a4ecef9fb2e3e8c1c810e241994f52f6

Just a simple line that mentions that -help exists and that's what you'll need to get started.

Need to narrow down a list of widely-used mods and add them for blueprint rendering support.

Bob's and Angel's mods seem like a good start.

use a path format like, item1.itema[index].attrib

Using the snapshot 6.14.17, giving Java access to 10Gbs of ram, of 12Gbs total a fatal error occured.

The hs_err log file generated by Java: gist
The blueprint used: gist (This is @Bilka2's blueprint. It's all his fault.)

A quick look at the stack trace points towards a problem within Java2Ds scaling.

Labelled as Won't Fix, due to Demods plans of replacing the rendering system.

Probably will be a good thing to put the bot owner in the configuration file.

This will need me to add an equipment map into DataTable first.

Currently reporting is only for blueprints, but it would be handy to have a reporting scheme for other commands to help keep track of exceptions and warnings in those as well.

I end up using a lot of memory generating large files, and there is currently two approaches in mind to mitigate this:

• Prevent large rendering by adjusting map scaling before rendering. This can't really make a good guess to how big the resulting PNG file will be, but it can be restrained by counting how many pixels there are.
• Look into a tiled map service that can work with custom maps, and direct the user to a link where they can view it. This would be a cool idea moving forward, which could help support other future ideas.

If multiple prototypes are requested, append them together into one file.

It appears in the new handler for commands, you're ignoring all attachments which would be a regression and as a result makes using the bot harder for users who don't want to use 3rd party sites like gist/gitlab snippets/pastebin/hastebin.

Example: -blueprint https://pastebin.com/ETtqnNbF
Wires seemed to be defined only one-way, whereas a normal bp file describes the wire in both directions. This will require a new approach to drawing wires if we want to support this kind of blueprint.

currently names will overlap for different types with same names

Could improve help by modifying DCBA to reduce how much fluff is crapped out and follow a standardizing format that uses the builder to make help easier to flesh out.

• Reduce the -help command to only list commands and have a tiny blurb on how to use a "-help format for more details.
• Use the builder interface and design a context to add a title, syntax, description, related commands, and examples

or add a command option to enable them while you work on them

A circuit network can be messy to visualize and understand, so it could be valuable to present a breakdown of each circuit network and come up with a clean way to present the logic flow.