Sir R. M8gic1an
2009-11-22 22:45:26
Okay, as the topic suggests I am fucking pissed off at the moment.
When you are coding a 1k line script how the fuck is it easier to remember that mithril is 5 rather than 'mithril' ?
This means you would either have a StringToInteger function if you had the user choose his object name through a string, or the user would have to use it as a number. Again, how the fuck does this make anything easier?
Go read the damn fucking include or tut. There are NO RECORDS/OBJECTS in SmartColors include, users create them during runtime. Do you expect me to make a const fo every single RS MS Object just so you can use your stupid constants and save 0.000001 MS when they get cased?
This was my first thought. If you give it some more thought you'll realize that in a script you'll probably make a procedure called SetupObjects to set up your SmartColors and therefore you would need a Global Variable to keep EACH OBJECT. GLOBAL VARIABLES = BAD!
I totally agree! Clicking is like the most interesting and hardest part as well as individual part of scripting! There are just so many ways to click something that I could drone and drone about it al fucking day! Wow, give people a searching method, but make them learn how to click, cus clicking is so fucking complicated! Also, to your little script two points:
1. Yes, it does make scripts much shorter
2. You don't have to keep them short, you can perhaps take your brains and time to develop something new which we haven't already done a million times before. We've all done about a fucking million TPA searchers, and trust me, it's not a stupid clicking function that will make it any bigger. The same could be said for MMouse, makes scripts too short. Perhaps it shouldn't move the mouse, just return the TPA of points where it should move through?
How the fuck do you expect to use a constant to keep a value that is generated during runtime ? :duh:
And why the fuck are you so keen on having it return an integer if you'd still have to input a string?
And if you really want to use a var/const, why not string? for the 0.00001 delay of the case?
Finally, it now accepts a variant as I already said, so you CAN use a constant instead of a string, why the fuck would you also want it to return an integer.
Sick of petty arguments over such small shit. Pissing me off for 0.000000001 ms, pissing me off for a clicking function, and generally leaving me pissed off.
So finally,
Fuck off,
GNight.
Rasta Magician
From: RM
I was aiming for ease of use
From: mixster
It just means that the scripter has to remember which string he is using or setup a const for it, which means that an integer one would have been just as easy.
When you are coding a 1k line script how the fuck is it easier to remember that mithril is 5 rather than 'mithril' ?
From: mormonman
Don't we use player[].integers[] as numbers? I honestly don't think that it would be that user unfriendly…
This means you would either have a StringToInteger function if you had the user choose his object name through a string, or the user would have to use it as a number. Again, how the fuck does this make anything easier?
From: mixster
or, even better, sc_mithril = 10; sc_coal = 11; sc_ *ctrl+space* => all the smart colours defined.
Go read the damn fucking include or tut. There are NO RECORDS/OBJECTS in SmartColors include, users create them during runtime. Do you expect me to make a const fo every single RS MS Object just so you can use your stupid constants and save 0.000001 MS when they get cased?
From: MylesMadness
I would have done:
Code:
I:=MakeObj(4689280, 9, 0.05, 0.74, ['n Tr', 'ree', 'hop', 'own'], ['hop down']);
But what ever
This was my first thought. If you give it some more thought you'll realize that in a script you'll probably make a procedure called SetupObjects to set up your SmartColors and therefore you would need a Global Variable to keep EACH OBJECT. GLOBAL VARIABLES = BAD!
From: Nava
Because clicking should be customizable, this is too much like
Code:
MineRock();
Bank();
GoToMine();
//…
Clicking is something important that I believe should be done individually in a script.
I totally agree! Clicking is like the most interesting and hardest part as well as individual part of scripting! There are just so many ways to click something that I could drone and drone about it al fucking day! Wow, give people a searching method, but make them learn how to click, cus clicking is so fucking complicated! Also, to your little script two points:
1. Yes, it does make scripts much shorter
2. You don't have to keep them short, you can perhaps take your brains and time to develop something new which we haven't already done a million times before. We've all done about a fucking million TPA searchers, and trust me, it's not a stupid clicking function that will make it any bigger. The same could be said for MMouse, makes scripts too short. Perhaps it shouldn't move the mouse, just return the TPA of points where it should move through?
From: Nava2
Why not just make it return an integer, and you don't have to use it if you don't want to?
The 0.00001 ms delay of variable assigning the one time per creation seems worthwhile to me That way you can still use the constants/vars during runtime.
How the fuck do you expect to use a constant to keep a value that is generated during runtime ? :duh:
And why the fuck are you so keen on having it return an integer if you'd still have to input a string?
And if you really want to use a var/const, why not string? for the 0.00001 delay of the case?
Finally, it now accepts a variant as I already said, so you CAN use a constant instead of a string, why the fuck would you also want it to return an integer.
Sick of petty arguments over such small shit. Pissing me off for 0.000000001 ms, pissing me off for a clicking function, and generally leaving me pissed off.
So finally,
Fuck off,
GNight.
Rasta Magician