RRL Randoms Development

If you wish to hate, please refrain from posting and bomb me via PM or MSN.

Why not help out the development of RRL today?
For those of you that don't know what RRL is, here's a quick nutshell explanation:

• A fast include to utilize reflection
• Stable
• Flexible
• No memory-leaks
• Actively developed
• Cross-support for SCAR/Simba
• Can work independent from the SRL include

For the others, who have tried out RRL, how would you like to help make it more expansive?

---

RRL is currently in a serious lack of functionality--in the area of Random Events. As you know, Random Events play a huge part in an includes success.
RRL currently covers two random events, of which neither are fully tested. This is a problem!

In the includes current state, it is licensed under a very restrictive license to outside modification (CC BY-NC-ND 3.0), this is for reasons obvious to ensure the includes success. So what I ask of you, is if you would be so kind to lend me a few accounts out of your army that have experienced random events.
Once the include is nearing completion, the include will be switched to a less restrictive license (CC BY-NC-SA 3.0), and will be more open to be adapted to communities, such as SRL, and be open to development by third-parties.

Please lend all accounts via SRL PM or MSN.
MSN: Timer150@Gmail.com

Any temporary account donations would be greatly appreciated.
Helping out will be rewarded with:

1. A warm feeling that you helped RRL grow. :)
2. Your name in the random-specific file.

Random's Statuses
Working
Testing
In-Development

Abyss
Beehive
Box - 60% (In working state to an extent!)
Captain Arnav
Certer
Drill Demon
Exam - 80%
First-Time-Death
Freaky Forester's Forest
Frog Princess
Grave Digger
Maze
Mime
Molly
Pillory
Pinball
Prison
Quiz
Sandwich lady
Scape Rune Island

CURRENT DONORS:
Mylesmadness - [3] Account[s] with [3] Box, [1] Drill Demon, [1] Mime, and [1] Pinball. :)
Zyt3x - Donated whole army of 20 characters temporarily (omg!) and [1] Exam.

Nice.

Quote:

---

Originally Posted by i luffs yeww

Nice.

---

Why thank you. :)

Good luck. :)
It will just take time.

I would gladly help you by lending accounts in randoms, but I'd rather give them to a more trusted member. Thats just my opinion, the work you have done on this include is great, but shouldn't you rather work on SRL's reflection? I read that you said it was messy, but make this a new base?

I really don't see why you would want to make this your own include instead of fixing SRL's reflection.

I completely agree with frement and marpis. This seems ridiculous to me when RRL will use SRL anyway. Why would users want to download two includes rather than one. I've had a quick look through RRL and it looks fantastic, it's a shame that you are not developing it on top of/as part of SRL.

Edit: I just reread and I see RRL plans to be independent of SRL. Why? For me the strength of the current reflection is that it has color back up and great mouse and TPA sorting functions from the SRL include. Why in gods name would you want to start over when you have such a great base to work from.

Also, how can we trust a member who has created a second account due to a previous permanent ban? o_O

Quote:

---

Originally Posted by Timer

In the includes current state, it is licensed under a very restrictive license to outside modification (CC BY-NC-ND 3.0), this is for reasons obvious to ensure the includes success.

---

Sir, you have a lot of nerve insulting a lot of us.

I'm really not sorry that most of us are in university and can not associate hours of time to projects out outside of school.

Sounds good :) I find it a bit weird you guarantee that there are no memory leaks, though. Also, from quickly glancing through your code, I found this:

Simba Code:

finally
    try
    except
      SmartFreeObject(InventoryInterface);
    end;
    try
    except
      SmartFreeObject(TheSlot);
    end;
  end;

Which is a bit of a weird construct? You basically never call SmartFreeObject?

Quote:

---

Originally Posted by nielsie95

Sounds good :) I find it a bit weird you guarantee that there are no memory leaks, though. Also, from quickly glancing through your code, I found this:

Simba Code:

finally
    try
    except
      SmartFreeObject(InventoryInterface);
    end;
    try
    except
      SmartFreeObject(TheSlot);
    end;
  end;

Which is a bit of a weird construct? You basically never call SmartFreeObject?

---

finally is called in the event of an exception or success, no?

Finally is called whenever you leave the body of the try clause (whether it's through an exception, exit, or just just successfully running through the code). Except, however, is only called in the case of an exception. But as you can't generate an exception out of nothing, the exception clause will never be reached.

Simba Code:

program new;
begin
  try
    WriteLn('Hai');
    Exit;
  finally
    WriteLn('There');
    try
    except
      WriteLn('Oh');
    end;
    try
    except
      WriteLn('Noes');
    end;
  end;
end.

Even when you do generate an exception, it never gets called:

Simba Code:

program new;
var
  i: Integer;
begin
  i := 0;
  try
    WriteLn('Hai');
    WriteLn(100 / i);
  finally
    WriteLn('There');
    try
    except
      WriteLn('Oh');
    end;
    try
    except
      WriteLn('Noes');
    end;
  end;
end.

I agree with Nava2, this is a slap in the face to the reflection developers that have already spent a lot of time making reflection a great asset in script writing. Sure, reflection has some bugs. More people just have to step up and be willing to help out the reflection team rather than going off and trying to put it to shame with their own include.

Good initiative, some competition can never hurt ;-).

Quote:

---

Originally Posted by nielsie95

Finally is called whenever you leave the body of the try clause (whether it's through an exception, exit, or just just successfully running through the code). Except, however, is only called in the case of an exception. But as you can't generate an exception out of nothing, the exception clause will never be reached.

Simba Code:

program new;
begin
  try
    WriteLn('Hai');
    Exit;
  finally
    WriteLn('There');
    try
    except
      WriteLn('Oh');
    end;
    try
    except
      WriteLn('Noes');
    end;
  end;
end.

Even when you do generate an exception, it never gets called:

Simba Code:

program new;
var
  i: Integer;
begin
  i := 0;
  try
    WriteLn('Hai');
    WriteLn(100 / i);
  finally
    WriteLn('There');
    try
    except
      WriteLn('Oh');
    end;
    try
    except
      WriteLn('Noes');
    end;
  end;
end.

---

I'll look into it at home.

Quote:

---

Originally Posted by Frement

I would gladly help you by lending accounts in randoms, but I'd rather give them to a more trusted member. Thats just my opinion, the work you have done on this include is great, but shouldn't you rather work on SRL's reflection? I read that you said it was messy, but make this a new base?

---

They dont let him work on *SRL's* reflection (which is really just reflection, not SRLs, because SRL doesn't want reflection in the include) iirc, ask around for why. That being said, he obviously has the time and skill to create this, and should be praised for it.

Also, Timer was once an SRL Member, banned for disrespect iirc. You were banned for account stealing and then came back. who was banned for worse? I trust both of you with any accounts that I would have.

Quote:

---

Originally Posted by Daniel

Also, how can we trust a member who has created a second account due to a previous permanent ban? o_O

---

You trust iroki's random solvers. You trust MOB to be SRL Members. How is this different? Especially since Timer never stole accounts, he was banned for other reasons.

Gratz Timer, good job :)

Definitely dont put him down for the work he is putting into his own include. When he showed me the include, I asked him alot of the same questions, but it is his choice. I also am slightly put off that he was permanently banned as an include can be changed easily to steal information.

I don't know why he was banned though, and his include seems very well put together.
If I remember right, someone stated recently that there are 0 active reflection devs. I cant say that I would choose to fix something extremely messy or go work on something new considering I would be doing all the work myself anyway. It seems that fixing others messes is sometimes harder than starting over.

I am in no way trying to put down the people that have worked hard on SRL-Reflection, but it leaves much to be desired.

Quote:

---

Originally Posted by 3Garrett3

They dont let him work on *SRL's* reflection (which is really just reflection, not SRLs, because SRL doesn't want reflection in the include) iirc, ask around for why. That being said, he obviously has the time and skill to create this, and should be praised for it.

Also, Timer was once an SRL Member, banned for disrespect iirc. You were banned for account stealing and then came back. who was banned for worse? I trust both of you with any accounts that I would have.

You trust iroki's random solvers. You trust MOB to be SRL Members. How is this different? Especially since Timer never stole accounts, he was banned for other reasons.

Gratz Timer, good job :)

---

Well, you got some good points in there. But still, I must say that I was away for 3 years, and comparison to Timer, he was away like, how long? And I didn't know the reason of the ban, so sorry about that. Still, EvilChicken! is the only one that currently has my password for my accounts. And random developers have the password for my army. People can change, but it takes time. And yes, now that I think of it, I would probably trust my army's password for Timer, but not my main.

The argument that anyone "should" have to go back and fix someone else's short comings is laughable at best.

Edit:
Sorry, I just spotted out my own idiocy. I was on my phone earlier, they should be in the try, no the except.

The "SRL" reflection was maintained by people who did not know what they were doing for to long. If you maintained a include that relied on SMART, one would think you would know you have to free smart objects to prevent memory leaks...

Quote:

---

Originally Posted by IceFire908

The argument that anyone "should" have to go back and fix someone else's short comings is laughable at best.

---

Thank you.

Quote:

---

Originally Posted by 3Garrett3

They dont let him work on *SRL's* reflection (which is really just reflection, not SRLs, because SRL doesn't want reflection in the include) iirc, ask around for why. That being said, he obviously has the time and skill to create this, and should be praised for it.

Also, Timer was once an SRL Member, banned for disrespect iirc. You were banned for account stealing and then came back. who was banned for worse? I trust both of you with any accounts that I would have.



You trust iroki's random solvers. You trust MOB to be SRL Members. How is this different? Especially since Timer never stole accounts, he was banned for other reasons.

Gratz Timer, good job :)

---

Thanks brother. <3

Quote:

---

Originally Posted by kitchenrange

Definitely dont put him down for the work he is putting into his own include. When he showed me the include, I asked him alot of the same questions, but it is his choice. I also am slightly put off that he was permanently banned as an include can be changed easily to steal information.

I don't know why he was banned though, and his include seems very well put together.
If I remember right, someone stated recently that there are 0 active reflection devs. I cant say that I would choose to fix something extremely messy or go work on something new considering I would be doing all the work myself anyway. It seems that fixing others messes is sometimes harder than starting over.

I am in no way trying to put down the people that have worked hard on SRL-Reflection, but it leaves much to be desired.

---

It's not that I don't want to fix the mess, it's that they wont let me be a dev.

Quote:

---

Originally Posted by mastaraymond

Good initiative, some competition can never hurt ;-).

---

;)

Quote:

---

Originally Posted by Echo_

I agree with Nava2, this is a slap in the face to the reflection developers that have already spent a lot of time making reflection a great asset in script writing. Sure, reflection has some bugs. More people just have to step up and be willing to help out the reflection team rather than going off and trying to put it to shame with their own include.

---

Not to be arrogant, but this should be a slap to the face. Nava2 along with others shot me down when I asked to be allowed to be on the SRL-Ref team, and said the include "turned to shit" when I had some control.

Quote:

---

Originally Posted by Nava2

Sir, you have a lot of nerve insulting a lot of us.

I'm really not sorry that most of us are in university and can not associate hours of time to projects out outside of school.

---

I'm sorry that life's not fair.

Quote:

---

Originally Posted by Daniel

Also, how can we trust a member who has created a second account due to a previous permanent ban? o_O

---

Your own choice. I wasn't banned for account stealing of any sort.

Quote:

---

Originally Posted by ReadySteadyGo

I completely agree with frement and marpis. This seems ridiculous to me when RRL will use SRL anyway. Why would users want to download two includes rather than one. I've had a quick look through RRL and it looks fantastic, it's a shame that you are not developing it on top of/as part of SRL.

Edit: I just reread and I see RRL plans to be independent of SRL. Why? For me the strength of the current reflection is that it has color back up and great mouse and TPA sorting functions from the SRL include. Why in gods name would you want to start over when you have such a great base to work from.

---

RRL will not use SRL.
RRL would be restricted by using SRL, as I do not have SRL developer access.
I don't see this "great base to work from".

Quote:

---

Originally Posted by marpis

I really don't see why you would want to make this your own include instead of fixing SRL's reflection.

---

No one allowed me to. :duh:

Quote:

---

Originally Posted by Frement

I would gladly help you by lending accounts in randoms, but I'd rather give them to a more trusted member. Thats just my opinion, the work you have done on this include is great, but shouldn't you rather work on SRL's reflection? I read that you said it was messy, but make this a new base?

---

They wont accept this as the new base, for two reasons:
I wont allow any of the current reflection developers (or past developers, for that matter) to touch the official include, they would be restrained to a fork--if SRL makes one.
They wont throw out all the work in simba-reflection.

I apologise, I misunderstood your reasons for making it separate. Good on you for showing the direction reflection needs to be taking.

Ideally I would love to see this in SRL, which you have said will happen anyway when you change the license. I will be following with interest.

Quote:

---

Originally Posted by ReadySteadyGo

I apologise, I misunderstood your reasons for making it separate. Good on you for showing the direction reflection needs to be taking.

Ideally I would love to see this in SRL, which you have said will happen anyway when you change the license. I will be following with interest.

---

When I change the license, it will be up to SRL if they wish to adapt and modify RRL to include SRL and/or other modifications. Other than that, they could include it with Simba in it's current state, just without any modification.

Nice Timer :)

Quote:

---

Originally Posted by Train

Edit:
Sorry, I just spotted out my own idiocy. I was on my phone earlier, they should be in the try, no the except.

---

They should be in the finally clause, just not in another nested try..except.

EDIT:

Quote:

---

Originally Posted by Train

When I change the license, it will be up to SRL if they wish to adapt and modify RRL to include SRL and/or other modifications. Other than that, they could include it with Simba in it's current state, just without any modification.

---

It's not up to the Simba developers to include it with Simba. It's up to the scripters and users to use it.

@They should be in the finally clause, just not in another nested try..except.
I accidentally had
try
except
code
end;

instead of
try
code
except
end;

@It's not up to the Simba developers to include it with Simba. It's up to the scripters and users to use it. :
I meant SRL as a community.

Quote:

---

Originally Posted by 3Garrett3

They dont let him work on *SRL's* reflection (which is really just reflection, not SRLs, because SRL doesn't want reflection in the include) iirc, ask around for why. That being said, he obviously has the time and skill to create this, and should be praised for it.

---

That's complete bull. Patches are obviously accepted, Timer is making this for other reasons. (Some of which I find obvious, some I don't really understand. If he's not ``allowed'' to commit to SRL Reflection then I still don't see why you'd want to remake SRL as well)

Quote:

---

Originally Posted by 3Garrett3

Also, Timer was once an SRL Member, banned for disrespect iirc. You were banned for account stealing and then came back. who was banned for worse? I trust both of you with any accounts that I would have.

---

Inciting hatred is not the same as disrespect.

Quote:

---

Originally Posted by Wizzup?

That's complete bull. Patches are obviously accepted, Timer is making this for other reasons. (Some of which I find obvious, some I don't really understand. If he's not ``allowed'' to commit to SRL Reflection then I still don't see why you'd want to remake SRL as well)



Inciting hatred is not the same as disrespect.

---

I was turned down before reflection was hosted in git. Nava2 also insulted me.

Quote:

---

Originally Posted by Train

I was turned down before reflection was hosted in git. Nava2 also insulted me.

---

I suppose I don't have to tell you how many times others (including you) have insulted me? Hear me crying? I've also told you I'm not just giving access to the SRL Reflection repository because you're not a trusted member. Simple, no matter how you or others twist it. I don't trust you, and I'm not going to give you commit access especially since one of the purposes of git is to NOT give everyone access to one central repository.

Enough off-topic-ness.

Looks promising, good job!

I insulted you because you are immature and, quite frankly, have awful code.

Are you aware that you actually have MORE memory leaks thanks to what nielsie posted? Again, you are looking for ways to seem better than everyone else. As I've stated in other places, you are not above everyone else and you way of doing things is inferior.

I've actually told you that I am more than willing to pull from you with SRL, but I am not willing to give you full access. You had it in the past and forced me to spend over 10h cleaning the include after your ridiculous modifications. Method and others can verify this. We ended up removing you for it.

Case and point, we do things for a reason. Please stop trying to get pity and create spite.

To reiterate:

Quote:

---

Originally Posted by Wizzup

I suppose I don't have to tell you how many times others (including you) have insulted me? Hear me crying? I've also told you I'm not just giving access to the SRL Reflection repository because you're not a trusted member. Simple, no matter how you or others twist it. I don't trust you, and I'm not going to give you commit access especially since one of the purposes of git is to NOT give everyone access to one central repository.

Enough off-topic-ness.

---

Quote:

---

Originally Posted by Nava2

I insulted you because you are immature and, quite frankly, have awful code.

Are you aware that you actually have MORE memory leaks thanks to what nielsie posted? Again, you are looking for ways to seem better than everyone else. As I've stated in other places, you are not above everyone else and you way of doing things is inferior.

I've actually told you that I am more than willing to pull from you with SRL, but I am not willing to give you full access. You had it in the past and forced me to spend over 10h cleaning the include after your ridiculous modifications. Method and others can verify this. We ended up removing you for it.

Case and point, we do things for a reason. Please stop trying to get pity and create spite.

To reiterate:

---

You're hilarious.

@You had it in the past and forced me to spend over 10h cleaning the include after your ridiculous modifications. Method and others can verify this. We ended up removing you for it. : Oh, you weren't a noob once?
--

Quote:

---

Originally Posted by Naum

Looks promising, good job!

---

Hey, thanks man. :)

I lent timer my account twice(It just loves getting randoms...), nothing was stolen.

You can trust Timer. I've known him for a while, he knows my entire army's passwords and he hasn't done anything with them. He is also lending me 10 mil. He really does mean well, and he's trying to do a good thing.

~King of the Nites

Drill demon confirmed working. :)

Are you ever planning to make this open source? By the way, I'm kinda going more along with what Wizzup and Nava2 posted, given the past can you really blame them for being cautious? I'm glad they're this cautious, it's nice knowing that my passwords are safe using Scar or Simba, and we have the SRL developers to thank for that. But don't get me wrong, it looks like you've put a good deal of work into your include and I've nothing against it, but I still think until you work with the community on development, you should keep this private for yourself, it's just not worth the risk of everyone IMO.

It's completely open source--has been...
https://github.com/RRLibrary/RRL
Your post made absolutely no sense to me.

Quote:

---

Originally Posted by Train

It's completely open-source--has been...
https://github.com/RRLibrary/RRL
Your post made absolutely no sense to me.

---

Don't act stupid...

Quote:

---

Originally Posted by Wizzup?

It's not listed on the Open Source license list: http://www.opensource.org/licenses/alphabetical so I'm not going to call it open source. More like read only source.

---

It makes perfect sense. He says "I think you should work with the community or keep it yourself".

It's technically "open source" to "his" definition. He can read through the code all he wants.