Six Eyes
-
Download here: https://github.com/eclipse1408/six-eyes/releases/download/v1.0/six-eyes-v1.0.lua
AI WAS USED TO HELP EXPLAIN CERTAIN PARTS OF THE CODE TO ME! (all code was written by humans)
THE OFFICIAL SCRIPT SERVER DOES NOT ACCEPT SCRIPTS WITH AI ASSISTANCE. DO NOT ASK ME TO ADD THE SCRIPT TO BE DOWNLOADABLE.
A even-further extension of Maticzpl's Subframe Chipmaker, which in turn is a Lua port of krawthekrow's Subframe Chipmaker mod (this one is a mod as opposed to a script, it directly modifies the source code).
The script also consumes other utilities and assimilates them into its poorly-coded hive mind of doom and despair.
INSTALLATION GUIDE
- Drop this into your scripts folder, the path of your file will look something like this:
C:\Program Files (x86)\Steam\steamapps\common\Powder\userdata\scripts\six-eyes-v1.0.lua
v1.0 Features
- Merges in PowderNotSolid's Layering Helper Reforged.
- Fixed setting Ctype and Tmp.
- Columns for setting Tmp3 and Tmp4 have been added.
- You can move rows up and down with the set of ^ and v buttons provided.
- Likewise, you can move columns left and right with the set of < and > keys provided.
Subframe Chipmaker
- Merges in Subframe Chipmaker.
- A slightly improved stack HUD is provided.
Planned Updates
- Line Tool+ Port.
- Integration with Maticzpl's Alloy Brushes: I would like to be able to create "temporary alloys" as to avoid having to duplicate stacks in order to produce a sizeable amount.
- Subframe animation: I want to port krawthekrow's subframe animation thingy into a Lua script.
- Subframe recording: Same as above.
- I do not know if these two are possible.
- Integration with Castleastle's Castleutils, provided he publishes the script.
Edited 3 times by TheFPSKiller. Last: 23rd September -
This is just a bundle of Lua scripts with a couple of minor features and bugfixes added. I would rather people just use the original scripts, that are already on script manager.
Subframe Chipmaker: https://starcatcher.us/scripts/?view=210
Layering Helper Reforged: https://starcatcher.us/scripts/?view=176
Alloy Brushes: https://starcatcher.us/scripts/?view=232
I'm pretty open to patching other people's scripts with bugfixes. Some scripts on there have glaring flaws, but the author is inactive or doesn't care. A couple times, I've had users DM me fixed scripts, for me to patch on the script server. Sometimes people just create cloned copy of the scripts too (that's why there's like 4 Layering Helper scripts). If it gets too deep into "new feature" territory I'd rather see a cloned script than me patching the original.
Anything you submit to the script server shouldn't use AI. You can use it to explain what it does and write the code yourself, features like adding tmp3 and tmp4 aren't that hard and our wiki is pretty extensive. We can give advice if you need help. -
Also, scripts involving AI are banned brom TPT.
-
This post is hidden because the user is bannedEdited once by KyleTheCreator. Last: 22nd September
-
To be fair, it does say that AI usage isn't allowed. So I think it's pretty just.
Edited once by Aklego-777. Last: 22nd September -
They are banned from the official script server. TPT cannot simply ban lines of code, that's not how it works. I'm saying that I won't request for it to be added so please do not ask me.
-
I have implemented the temporary alloys feature and made some (one) (1) attempt to optimization.
-
@Aklego-777 (View Post)
You're pretty wrong. Any AI written code is banned, but using AI to get the definition of the code is a very good use case; in fact you should use it. Just don't make AI write the code. So the verdict is, ANY ai generated code is banned, but any code that is not AI generated / human generated is allowed. -
I want to clarify a few things about my stances
My stance on this script is that it is bad, it's just a modpack that takes existing Lua scripts and merges them into one. Collaboration options are limited, but I would still rather see bugfixes and improvements upstreamed into those scripts. TheFPSKiller already said they don't plan on doing that though.
My stance on AI is that it's killing the ability of programmers to understand what they are writing (in addition to killing the environment and the economy). If everyone wrote code that way, writing code would become a lost art. AI is capable of writing very large amounts of code in a short time, that may not have much thought put into it, or may change TPT into another game entirely. It's very difficult for me to review it. So for all these reasons, plus the previous inability of AI to write valid Lua scripts, it's banned from the script manager.
Best to kill AI scripts now, before they become a cancer (where AI-generated scripts start defining how people use and interact with TPT).
I haven't checked if this script is AI, when I looked earlier it was just a bundle of existing scripts with minor changes made.
Last, my stance on posting scripts to the forum is that it's currently, not banned. But I am thinking of mandating that large Lua scripts be posted to the script manager. Posting scripts here is just bypassing the review process, and could lead to malware / unwanted scripts spreading. We also talked about having allowed hosts for scripts (something like github, that has proper diffs).
