more (preferably arbitrarily many) input rows for AND/OR/NOR/NAND gates
purpose:
simplify programming
currently if you want to make a signal that means ROTATE_RIGHT AND RESOURCE_FOUND AND ENEMY_NEARBY AND STUCK_UNDER_TERRAIN
you would need to first make an AND gate that combines ROTATE_RIGHT and RESOURCE_FOUND into ROTATE_RIGHT AND RESOURCE FOUND and then
use another AND gate to combine ROTATE_RIGHT AND RESOURCE_FOUND and ENEMY_NEARBY into ROTATE_RIGHT AND RESOURCE_FOUND AND ENEMY_NEARBY and then
use another AND gate tat combines ROTATE_RIGHT AND RESOURCE_FOUND AND ENEMY_NEARBY and STUCK_UNDER_TERRAIN into ROTATE_RIGHT AND RESOURCE_FOUND AND ENEMY_NEARBY AND STUCK_UNDER_TERRAIN.
why not just let us use 1 AND gate to take all 4 inputs? it's unlikely to affect the balance of the game since the partial AND statements are often useful in ones drone, but I see little reason why the logic gates are limited to taking so few inputs when their various functions can be so easily extended to allow arbitrarily many inputs.
possible implementations:
AND gate: take any number of inputs, gives output if all inputs are recieved.
OR gate: take any number of inputs, gives output if any inputs are recieved.
NOR gate: take any number of inputs, gives output if no inputs are recieved.
NAND gate: take any number of inputs, gives output as long as any input is not recieved.
Post
Roblin
Idea:
more (preferably arbitrarily many) input rows for AND/OR/NOR/NAND gates
purpose:
simplify programming
currently if you want to make a signal that means ROTATE_RIGHT AND RESOURCE_FOUND AND ENEMY_NEARBY AND STUCK_UNDER_TERRAIN
you would need to first make an AND gate that combines ROTATE_RIGHT and RESOURCE_FOUND into ROTATE_RIGHT AND RESOURCE FOUND and then
use another AND gate to combine ROTATE_RIGHT AND RESOURCE_FOUND and ENEMY_NEARBY into ROTATE_RIGHT AND RESOURCE_FOUND AND ENEMY_NEARBY and then
use another AND gate tat combines ROTATE_RIGHT AND RESOURCE_FOUND AND ENEMY_NEARBY and STUCK_UNDER_TERRAIN into ROTATE_RIGHT AND RESOURCE_FOUND AND ENEMY_NEARBY AND STUCK_UNDER_TERRAIN.
why not just let us use 1 AND gate to take all 4 inputs? it's unlikely to affect the balance of the game since the partial AND statements are often useful in ones drone, but I see little reason why the logic gates are limited to taking so few inputs when their various functions can be so easily extended to allow arbitrarily many inputs.
possible implementations:
AND gate: take any number of inputs, gives output if all inputs are recieved.
OR gate: take any number of inputs, gives output if any inputs are recieved.
NOR gate: take any number of inputs, gives output if no inputs are recieved.
NAND gate: take any number of inputs, gives output as long as any input is not recieved.
Link to comment
Share on other sites
3 replies to this post
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now