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
... that would have been much more efficient than what I did do. Apparentloy I used an equals to check if it equals 1,2,3,4,5,6,7 or 8, and if it did then that was my remainder (with a separate check for 0)
Oh I also did it the other way around. I added from 0 until I got above the number to stop. I think then I subtracte where I was from the total and if it was 1-8 then we had the answer.
My answer does not meet the 'minimum nodes' criteria so I'll have to optimize that. Currently working on optimizing Greater.
Anyway to reprhase: If you subtract a negative number you get a positive and then input select will work on it. If you put a negative number into an input select (or a number greater than the available selections) you get '-'. Also having equals 1/2/3/4/5/6/7/8 works as well (which is why I needed that even though it bloated my node count)