Originally posted by gtownsbadass
That's fine and for the most part you are right most of the mods were copy and pasted as I said before I knew nothing about gsc and used other peoples menus and functions there are 3 threads full of them why would I try to recreate whats already been made if there is no problem with it however in the next version I got a little more in depth with adding and changing scripts because im learning more and more and my goal is not to have the best menu with the most mods my goal is to have the most stable menu with as many mods as possible to keep stability. As far as people having problem with load not sure what there problem is ive used this menu along with three of my friends with no problems so if they want to pm me with the problem they are having I would be glad to assist with it or even fix this issue but I cant fix an issue if I don't know what it is how it happens etc.
If you know little about GSC; why did you post an unstable menu with mostly copy and paste functions with out crediting anyone? It is ok to use common community functions such as god mode, no clip ect. It is ok to dive though peoples sources and use a few of their functions. They are there to give everyone a basic set to work with and learn from. What is not ok, is when the project/menu is mostly those functions and you decide to post. The wrongness of the act becomes greater is you don't credit the people you took from and don't post the source. Being new to GSC doesn't give you any excuses free pass on not crediting people.
My point is that you need to need to clean house on your post and your project.
1) Add credits, everyone whose work you used and/or the source of the work needs to be listed. Its just like submitting a paper for school and not citing your sources.
2) Add a download link to your source, you admitted that your menu is mostly copy and paste (thanks for being honest), there is nothing to hide. Its offensive to everyone you copied and pasted from to have their code locked behind a compiled file with out much original work put in.
3) Once you have gotten more of the basics of GSC, add in some more custom coded functions.