Welcome to the Forum. Yes, we need to see your code. There are no "scripts" in Arduino programming. It's called "source code". Before posting, please read the two posts
How to use this forum - please read. and
Read this before posting a programming question ...
Please read the two posts at the top of this Forum on guidelines for posting here, especially the use of code tags which make the code look
when posting source code files. It makes it easier to read, and can be copied with a single mouse click. Also, if you don't do it, some of the character sequences in the code can be misinterpred by the forum code as italics or funny emoticons.
Many questions can be answered by simply reading the documentation which is provided with the IDE, available under the help tab, or online here.
There are many other things that programmers do to make their code understandable. Please do them, as a courtesy to the members who volunteer their time to help you here. One is to use a standard indentation to clearly show the code blocks. Never put more than one statement per line. Place any brackets by themselves on a separate line. Before posting the code, use Ctrl-T in the IDE to reformat the code in a standard format, which makes it easier for us to read. Another is to give things descriptive names. You can name numerical constants, pin numbers, variables and many other things in this way. For example, you can refer to a pin and an output level by number, like
digitalWrite(3,0). But such a statement doesn't reveal anything about the purpose.
digitalWrite(hornRelayPin, LOW) does. You can do that by declaring
const byte hornRelayPin = 3; before setup() in your program. Many such names are already defined for you by the compiler and the Arduino IDE. Here are some:
#define HIGH 0x1
#define LOW 0x0
#define PI 3.1415926535897932384626433832795
Use them. There are many more. Use compiler math to compute values so you can see where they came from (or at least document them). For example, if you see the number 73, you would be hard put to explain the significance of it. But if you see "daysPerYear/5", it is obvious. One more thing. When you work on program continuously, you become familiar with it. So many things seem obvious even if they are not spelled out explicitly. But try looking at your own code six months later. It will be as if a stranger wrote it. So write for strangers, not yourself.