Feedback 20.11
-
Hello. ... Well.
- Rollback. This is what's really needed in the new version, unfortunately. The core elements should be stable and native( and chain-like ). Experimentation and optimization should be separated.
The mobile version has issues with the cursor, information (ctype, count), and frames.
WEB - await keyboard .
Edited 2 times by Interface-operator. Last: 22nd November -
No new version has been released since February. Can you explain what the "core elements" are? What does "native" mean in this context?
Features get fairly thorough testing before they get published, and bugfixes are usually posted into the snapshots within hours of the bugs being discovered. I'm not sure that elements need to be made more chain-like either. We already have SOAP, which makes enough chain-like elements for my liking.
-
A long time ago. - No problem. Basic elements(translator).
Are you talking about this "new experimental set of interfaces"? - look. Better than the previous version.
But illogical. the problems are easier to solve and show through nature.
Nothing remains of the solenoids, and the cramped LED matrix(is not display) with the metl in the chain is completely out of reach.
A RAY now equal Draw the ray and "a ray".
dialect - that's what it reminds me of.
And more, but I'm focused...
Edited 3 times by Interface-operator. Last: 20th November -
If the logic layer is good, then standart works - chips, objects - were be able to be presented in grid forms, element per element, with single texspacing for default case. And intersections of the "soft P-hard N". With laconic behavior. As described in
https://powdertoy.co.uk/Browse/View.html?ID=3306350
- A rag-like appearance. Where sparks would flow like fractals. Like element Q present in
https://powdertoy.co.uk/Browse/View.html?ID=3172589
Then filt would be useful without concurence
the specification is violated, in general.
Edited 6 times by Interface-operator. Last: 21st November -
So this translation is VERY rough, so I am somewhat struggling to understand what you mean. That said, looking at your saves, it seems like you want to be able to remotely turn on and off swch, or better, to have pscn/nscn on different layers compared to the metl and swch, so that you can make really compact chips.
I sincerely doubt this will ever happen, as it would require some very complex new placement mechanics, and would also be hard to visualize in game, and probably difficult to code. It would be better to use cray to remotely toggle if there is or is not metl where you currently have swch. -
In general, old mechanics support it all ~(table "nice" in "example"). Layers - no. And no hard inclusions.
- more understanding is needed here :)
Logic(chip) and more - if you try to remember materials based on grid overlays,
Structures for their building.
Lead motivation: i see several directions for using the game as a real presentation (outside of production). It is: short-diagrams, models, show.
*
There's really a problem with the "and" logic here. For aray+led based. And i can solve it, but not for insaray absciss.And it is bullshit(8x11).
Edited 7 times by Interface-operator. Last: 22nd November
