SRL Archive - News and General

I deleted my 2000 word post because I don't know how to be succinct at times. I'll make this quick since I honestly do ramble and haven't learned how to be 'to the point'. Also there should be a poll, I checked it, lets see if it works. If not, my bad.

If the following is unclear, post and I will clarify
I've made a 4000+ line reflection include. I can't really work on reflection because I'm not a developer, and there's some *serious* holes missing in reflection. Particularly the interfaces… not of any fault of the staff though, as I know most of them and they're pretty damn busy with RL [which is obviously foremost always].

Therefore I went on my own path making my own functions. I even tested them out in my guildminer as some of you have seen.

So what did I do?

1. Fixed holes in Reflection that are useful to many people
2. Came up with ideas for common problems (like irritating interface stuff)
3. Question handling in the chat interface
4. A banking script that took me FOREVER, but can flawlessly withdraw any item at any spot with failsafes, and even works with people's banks who are more or less retarded (aka: has nothing in the infinity tab but tons of items in other tabs, throwing off most things except DTM based stuff)
5. Flawless door handlers and object handlers (haven't gotten around to ladders yet)
6. Easy for first time coders, with my code as of this point you could make a script in 6 lines of code, two of which are include, 4 of which are bold letters like repeat/until– Ex:

procedure MainLoop;
begin
  repeat
    MineRocks (arg1, arg2...); // This function would have all the failsafes like antiban/antirandom embedded so people don't need to actually call it
    DropInvItems (arg1, arg2...);
  until (AllPlayersInactive)
end;

7. Probably throw my WorldWalker in there or something

Most importantly:
It is a place where I take the ideas of the community and implement them. A great example is the gaussian mouse function that I personally have no idea why it hasn't been implemented quicker if at all.


I don't know if the poll is going to work, but I'll try this anyways:
If this project ever gets off the ground, would you use it? Would you consider contributing code wise?


An example of the power with the include would allow someone to make a fisher for any location and bank with amazing technique, and have it all done within 10-15 lines of coding.
Yes you could make a guild fisher in 10-15 lines of code easily.

Opinions welcome. This wouldn't be staffed where you have to have perfect flawless "do it in 10 lines or bust" code, but rather code that *works* while being efficient. If you do 200 lines of code that can be done in 100, then yes that's a problem, it has to be sound standard wise, but sometimes we can bend the bush.

Lastly, this post does not mean it will come off the ground, nor does it mean it will ever see the light of day. I'm just really curious in what the community would think. This includes you registered users as well ;)


[BANANA]Too Long; Don't Read summary:
- Make an include for reflection that patches all the holes
- Allows easy coding that can be done in a few lines
- Make scripts like a guild fisher in 10-12 lines
- Solves problems like banking forever and flawlessly
- Has antirandoms/failsafes built into it so the coding is even shorter
- Uses the most innovative ideas from the community, which don't seem to be picked up[/BANANA]

EDIT: I voted 'I would probably use it, I would probably contribute' for obvious reasons :)
EDIT2: Too bad I didn't make it anonymous, usually gets more votes that way ;) I checked it, then was thinking of unchecking it but submitted before my brain could process the what my fingers did.
EDIT3: I must make this clear, if I make this new project, it will not require a whole new SVN to be updated apart from reflection. It would be dependant on both SRL *AND* Reflection, and would borrow commands from both, there wouldn't be a need to make a whole new repository and split it in a different direction.
Sorry if this caused confusion

Someone give him access to the reflection svn already?! Imho, even though I'm not a ref dev or anything near that, I think he's earned it…


Anywho. I voted "I would not use it, but I'd think about contributing because I like coding new things."

From: Zyt3x
Someone give him access to the reflection svn already?! Imho, even though I'm not a ref dev or anything near that, I think he's earned it…


Anywho. I voted "I would not use it, but I'd think about contributing because I like coding new things."

I mentioned it shortly after I got added to the SVN, but since he didn't get added, I suppose there are reasons against it.
Another SVN doesn't seem like it would be a good idea, reflection has had way too many SVNs already. We don't need to break it up again.

Just because you can't commit to the subversion repository doesn't mean you can't contribute to the include. You are still able to post changes you would like to see made and, if others agree with them, they'll be committed. I'm sure that if you're genuinely interested in helping the include grow like it appears you are, you'll be a developer soon enough anyways.

tl;dr Creating a new include seems a bit over-the-top. Post your changes on the forum and they'll be committed if they're useful.

From: pyroryan

Another SVN doesn't seem like it would be a good idea, reflection has had way too many SVNs already. We don't need to break it up again.

This.


I'm not an SRL dev but I still submit all my fixes etc. rather than just starting my own. If everyone always starts their own, nothing will ever get anywhere.

From: Method
Just because you can't commit to the subversion repository doesn't mean you can't contribute to the include. You are still able to post changes you would like to see made and, if others agree with them, they'll be committed. I'm sure that if you're genuinely interested in helping the include grow like it appears you are, you'll be a developer soon enough anyways.

tl;dr Creating a new include seems a bit over-the-top. Post your changes on the forum and they'll be committed if they're useful.

Oops I forgot to address this in the main post:

I would mainly be reflection, but would also have color functions.
In addition, some things would be independent of both color and reflection (ex: GMouse)




To your post:
While I agree, and thinking about it, potentially a whole include may not be the best action– rather a thought at the time if it really churned steam – though here is an example of something that should have been added (at least the first one should have), as it is critical for any reflection developer to access child components.
For me, I had to always create redundant functions again and again that I felt could be in the include (one of which was that :p), therefore, my question in return would be: Are they considered?



In addition:
Personally it would be cool for me to be a reflection developer, though hopefully this post did not come across as me wanting to become one.
It was rather for me to think of combining new ideas from the community– which would more or less have a big chunk of reflection in it– into an area for testing that could help everyone alike.
:)

The medium just happens to be reflection ;)

From: NCDS
I'm not an SRL dev but I still submit all my fixes etc. rather than just starting my own. If everyone always starts their own, nothing will ever get anywhere.

While I agree, I don't think SRL is one of those things you could make ones own include for :p
If everyone was starting their own thing, it would be something that could be pulled together. Thus far I personally haven't seen anyone start any projects recently (if they have post some links, I would be more than glad to be wrong on this one), or the only one that I know of [POMS] AFAIK is out of date?


The goal of this would be to make a place where people's innovative ideas can be pooled and/or tested, rather than collect dust.




EDIT:
I must make this clear as I messed up: if I make this new project, it will not require a whole new SVN to be updated apart from reflection. It would be dependant on both SRL *AND* Reflection, and would borrow commands from both, there wouldn't be a need to make a whole new repository and split it in a different direction.
Sorry if this caused confusion

From: cstrike

While I agree, I don't think SRL is one of those things you could make ones own include for :p
If everyone was starting their own thing, it would be something that could be pulled together. Thus far I personally haven't seen anyone start any projects recently (if they have post some links, I would be more than glad to be wrong on this one), or the only one that I know of [POMS] AFAIK is out of date?


The goal of this would be to make a place where people's innovative ideas can be pooled and/or tested, rather than collect dust.

MSI :confused:

From: NCDS
MSI :confused:

I would love to work on MSI :) + I have submitted code, but I really enjoy reflection so much and MSI is more color based. I think color is very unique in its own ways, and I would end up poisoning it with pure reflection. Not that I view reflection as a poison , but with what I've seen, I think MSI should continue on it's path for being as pure color as it can be.

If they did have reflection or were open to that idea, I would pool all my might into MSI.

From: cstrike
I would love to work on MSI :) + I have submitted code, but I really enjoy reflection so much and MSI is more color based. I think color is very unique in its own ways, and I would end up poisoning it with pure reflection. Not that I view reflection as a poison , but with what I've seen, I think MSI should continue on it's path for being as pure color as it can be.

If they did have reflection or were open to that idea, I would pool all my might into MSI.

Ahh I misunderstood what you meant in the above post. We will always be primarily color though.

There is no reason to make your own include, just post your ideas here and if they are good, then people will use them, and if enough people use them they will get added.

Also in your include, be sure to not have functions like MineRocks, and object specific functions. What could be done is maybe save all the ore's ids as variables or something.

I would say go ahead and make your own include, and if people want they can come and contribute to it and others may use it as well. There's no one to stop you from being creative and making your own project team and what not, since your really good with reflection I can see why you would want this.

-I would use it and contribute to it, when I come back that is xD; but im positive others will do the same. We could have MSI for our color foundation, and then Infinity (i think thats what you called it in your other thread) as a reflection sub-library. Its up to anyone if they want to use it or not, but it will be there, and thats all that matters.

[QUOTE=Camaro';749599]Also in your include, be sure to [b]not[/b] have functions like MineRocks, and object specific functions. What could be done is maybe save all the ore's ids as variables or something.

In this project, he wants to make a library of ready-to-go functions that on-to-go (leecher's / test dummies / busy people :P) can use. Of course his variables will include ore's and trees and whatnot, but those would be sorted out (im sure he already has a pool of ideas on organizing variables for this project). Reflection (even though I have never really used it :X or have yet to learn it) is a goldmine for scripters who know how to use it, and that best friend for new comers who just want a script to use and don't know how to script. This project would be beneficial to both.

People just think too much of the word include, they think its going to make people compete with SRL. This is more of a project, and it is simply a add-on which depends on everything that we always use.

I'll read all this in the morning, been gone competing in the weekend!
Sorry for my awayness, tihihi