[seanny]

Quote:

Originally Posted by ColeMiner I've written a tutorial on this in the past, the short answer is "YSI": https://sampforum.blast.hk/showthread.php?tid=296907 Basically, you split your mode up in to logical pieces, such as streamer, vehicles, fishing job, etc. Each of these systems is in a separate file and all are included in to the main mode. However, you also include each system in to a separate filterscript and compile those individually. If you wrote your mode well (with minimal coupling between independent parts) this should be easy. Anyway, the key to this is y_master, so you declare a function as: pawn Code: global MyFunc(whatever) {     // Do the code here... } And have a header include in which you "forward" all those functions (but not using "forward"): pawn Code: foreign MyFunc(whatever); Your other scripters are given this header file and the compiled filterscript (which can also use "y_lock" and other script protections). The header means that they can include and call the functions, but the use of a filterscript means that they don't actually have the source of the functions and the use of "y_lock" means that they can only run the script on localhost. The other advantage of this method is that when they send you their code, you can compile all the separate parts in to one huge script and not need to use the filterscripts and remote calls at all - without altering ANY code. These links might also help: https://sampforum.blast.hk/showthread.php?tid=194509 (old) https://sampforum.blast.hk/showthread.php?tid=475106 (new)

I think that ColeMiner (Y_Less) has a point, YSI is probably yhe best system to use for script security, but I have another question, is there another way to give my script source code to 'developers' w/o having to email it/upload it to mediafire?