Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I no longer support this mod and place all my hopes on the community - creators of forks and analogues. I was pioneer in this modding direction and I'm glad the community began to work in the direction of creating computer mods. Now this mod will live on the shoulders of the community - each fork will carry the memory of the day when I first published the mod and started a new era - era of computers science in SM mods.
I hope that Scrap Mechanic developers will add support for creating render surfaces with GPU acceleration to LuaAPI one day. Also I hope they allow using of built-in Lua tools like 'loadstring' to avoid writing "VM on VM".
My last with is that BananaPen and NokoDev will become friends someday and stop arguing about their computer mods.
" ScriptableComputer: text here " , is their a way to disable it from naming its self when printing
so like it only prints the " text here " ?
вы можете изуть документацию SComputers по этой ссылке: https://github.com/igorkll/SComputers_docs
кста, не обязательно общаться так официально))
I can write to you privately if I can find any problems
1. Будет ли далее развиваться форк этого мода, который был здесь недавно? 2. И будут ли в (этот откат) модификации добавлены предметы со схожим функционалом, как были в форке?
Пожалуйста ответьте на все вопросы. И кстати, я ранее написал вам пару идей в Suggestions, просьба тоже обратить внимание.
Changes to FileSystem.lua:
function FileSystem.parsePath(pathStr) removed
function FileSystem.concatPaths(path, to) removed
Added function FileSystem._Decodepathname(path)
Added function FileSystem._Decodepath(path)
All functions changed to the new path system
It would be great if I could work on the project with you
based on the results of the surveys conducted, I found out that not everyone is happy with the transition of ScriptableComputer to SComputers. therefore, at the moment it will be rolled back to the original, and then I will transfer all optimizations and fixes from SComputers to the original, without transferring the contents (i.e. blocks)
if someone needs SComputers specifically, you can subscribe to it in my steam profile.
1.About my antena.If you mean the built in "sendTo" in the mods code (i constantly look up the mod scripts to know how something works cuz the guide needs to be expanded) then no cuz last time i checked it was disabled. So i made my own send to that is based on every device having a name (set in code) and the device only records messages that have their name in them or "" in case you need to send it to all on the same network.(network is also specified in the code and all antenas on that network can comunicate ignoring the divices with the different network name).
2.About your mod not having recipes. You should probably try to reach out to someone like 00fant or the devs behind the modpack. im sure they encountered it.
P.S Check out my display UI creator i posted it in comments below. My biggest completed project yet.(building looking thing) (tho im not very experienced with coding so it's probably a nightmare code wise)
It's 2 way and suports up to 128 devices at once.With naming and ability to separate them into separate networks.
there you can adjust, among other things, the display rendering range
(part 3/3)
A hint (from someone with >30years of programming experience) for any kind of updates/upgrade of published software:
Make the old settings the default, so that your new version doesn't break functionality of what's already out there using the old version. You don't want people to get angry, throw it in a corner, unstall that sh.., fire you, sue you, .... You get the point.
"(Backwards) compatible" means: Users (here: using programmers) don't have to change a single thing (no program, no configuration setting) and it keeps working. If you think you have to make breaking changes for new functionality (there are sometimes good reasons): Put a new mod next to the old one and add a higher version number to the new one's name and add a hint in the old version, that there is a better but incompatible new version. No spectacular new info here, that's just the common way to handle that.
(part 2/3)
Do these settings get permanently stored with the creation, so I can upload that to the workshop and it works for others, or do I need to add a "You have to find the duck and enter stuff you will not understand ..." description?
With those setting changes my programs technically "work" again as it seems (which is a relief), but:
If you stand further than about ~5 blocks away (player character eyes to display), only a seemingly random portion of the pixels (about 60%) drawn by the program (via commands drawText, drawCircle, etc.) are rendered, even when I set "display render distance:30" instead of your default of 15.
That was no problem with the old mod. (Yes there was a "nothing is shown at all" render cutoff distance, if you were much further away, but no: Hey I'm right here staring at the screen, but getting only about 60% of the pixels. That's quite close to unusable for many use cases.)
Any solution for that?