Ohh ok. Thanks! Didn't know it would be at player instead of tile.
I hope I could just run an updater to update all the hooks every Thursday since its "update day"
Krazy seems to me is a busy guy and he's not paid to do all these, so can't be active 24/7. I understand that but maybe he can have more people to help on the dev team and updates.
The Include has been updated, please post if there are any problems with the hooks
The banking function was interesting ineedbot, Interaction and AntiRandoms will be updated soon but Interaction won't be getting those exact functions (adding an offset variant of R_MouseTile has been intended for some time though).. Those solvers were made a while ago and Frement will likely want them to have some more failsafes when they are merged with the include.
It's great that quite a few people are willing to contributeLooks like this project is really turning into something!
Guys I'm available for some extended hours next week. Let's write an actual include, not this mess of code someone upchucked.
Current projects:
[ AeroGuardians (GotR minigame), Motherlode Miner, Blast furnace ]
"I won't fall in your gravity. Open your eyes,
you're the Earth and I'm the sky..."
I just want to bot without babysitting to see if im logged out or not from a failed randomJust delete everything to do with f_antirandoms from the script.
Thanks for inputI'm having trouble with a lot of the functions beginning with the one, "R_GetWidget," and multiple ones under that. The full error is "[Error] C:\Simba\Includes\F_AntiRandoms.simba(120:10): Duplicate identifier 'R_GETWIDGET' at line 120"
Next after that is "R_GetWidgetText," full error being "[Error] C:\Simba\Includes\F_AntiRandoms.simba(130:10): Duplicate identifier 'R_GETWIDGETTEXT' at line 130"
I'll list one more - "TInventoryItem," full error being "[Error] C:\Simba\Includes\F_AntiRandoms.simba(855:3): Duplicate identifier 'TInventoryItem' at line 855"
Last edited by klew1102; 07-26-2014 at 01:26 PM.
There are several very important reasons its not a good idea.
1. The game engine is slightly different in some areas and causes structural changes to some of the files that make them ugly with a direct port.
2. SRL-Reflection-2 was supposed to be a stepping stone towards a great include that was named SRL-Reflection-2.2, and as such it has very inefficient data accessing features.
3. As a developer, we scrapped SRL-Reflection-2 a long time before even starting a different library, but I personally tried to keep it functional for everyone to use while we discussed what we were going to do differently in the next alteration.
Here are some ideas that I would like to use:
Structure the scripting-used procedures around quasi-objects. This would allow us to save the loaded object in a global array of loaded smart objects(for a farce of memory control to keep the leaks at a minimum). The objects could be the same as in the rs client or they could have a completely custom structure that we decided made more sense seeing as we are not coding with all the features of java. Here is one I started a while back but didn't finish because I ran out of time and no one I asked wanted to continue it: https://github.com/tlsdude/OSR-REF
I believe that it is imperative for any of our includes to incorporate some sort of object control and force the scripter to create, use, and delete objects....BUT there will also be procedures for those who don't won't to explicitly free their objects with global object freeing.
Another idea that I think is important, is overloaded functions. There is no need to make a lot of different names for functions like getnpc and getnpcex and getnpcexcustom. That can all be overloaded. They should only have separate names if the functionality changes, not the parameters.
Lastly, there needs to be specific people in charge of changes/additions to the include...as you might have noticed several things have been added to this version that just weren't up to par. Things must be vetted before given to the public. That's fundamental in all programming.
If you want to reduce memory leaks entirely, Simba would need classes which in Obj-Pascal has destructors OR RAII containers such as ScopeGuards that automatically delete a resource or calls a cleanup function when it goes out of scope.
How do you plan on doing these things without those OR without modifying SMART?
I am Ggzz..
Hackintosher
There are currently 1 users browsing this thread. (0 members and 1 guests)