Lord_Greywolf
Lord
Here is a couple for you
some hopefully simple but usefull suggestions:
1) if the scripts are cached, also skip the verifying, since they where verified before - will save a few moments on start up of shards with lots of custom scripts
2) a setting to show warning, but not stop because of them?
not sure if possible, but to have it show all warning generated, but still compile and run
this is usefull, because even though your script may have compiled, could have warning in it
3) a setting of "forced cache" - i.e. even if no scripts present or script changes, it will not try to compile, but use the cached dill's instead
also good with #1 above
this can be very usefull, specialy for those scripting on the same machine as the server is, that they know there is problems with the scripts, but need to do a restart
or for remote servers - so if they are hacked, scripts can not be had, just the dll's
and if i remember right, the dll's do not work right if not compiled by that same "runuo.exe" file (had that come up by accident when copying over files from one machine to the other)
so basicaly the dll's do them no good (can copy scripts up - run once to get dll's, set to force cache, and delete scripts, and hacker safe)
4) maybe some backwards compatability
i.e. you change the way something is called
keep old method also, setting it up to do the new way of calling from it
(can place in warniong about it being an older method also maybe? - work great with #2 above)
I know now - this may be hard to put in for older stuff, but at least for newer stuff might be good
5) have a way to modify the "time out" when compiling
i.e. it is a default to about 9 or 10 minutes i believe
well testservers many times do not have the power to compile the scripts up real fast, and hitting that time limit happens a lot - specialy if some windows/antivirus/etc function kicks in while it is going on, and steals 2 minutes from it
6) not sure if possible - but a "quick compile" setting
it would stop before ferivy and say if good or bad
what this does is use the cache and try compiling only new or changed scripts in
this would be usefull for quick script checking to see if any "syntax" errors, etc
but can not be used "live" because was not a full compiling, and other parts may not interact fully with it, until full compiling
thanks fro looking at these,
hope you do not laugh to hard at them
and maybe use 1 or 2 of them
some hopefully simple but usefull suggestions:
1) if the scripts are cached, also skip the verifying, since they where verified before - will save a few moments on start up of shards with lots of custom scripts
2) a setting to show warning, but not stop because of them?
not sure if possible, but to have it show all warning generated, but still compile and run
this is usefull, because even though your script may have compiled, could have warning in it
3) a setting of "forced cache" - i.e. even if no scripts present or script changes, it will not try to compile, but use the cached dill's instead
also good with #1 above
this can be very usefull, specialy for those scripting on the same machine as the server is, that they know there is problems with the scripts, but need to do a restart
or for remote servers - so if they are hacked, scripts can not be had, just the dll's
and if i remember right, the dll's do not work right if not compiled by that same "runuo.exe" file (had that come up by accident when copying over files from one machine to the other)
so basicaly the dll's do them no good (can copy scripts up - run once to get dll's, set to force cache, and delete scripts, and hacker safe)
4) maybe some backwards compatability
i.e. you change the way something is called
keep old method also, setting it up to do the new way of calling from it
(can place in warniong about it being an older method also maybe? - work great with #2 above)
I know now - this may be hard to put in for older stuff, but at least for newer stuff might be good
5) have a way to modify the "time out" when compiling
i.e. it is a default to about 9 or 10 minutes i believe
well testservers many times do not have the power to compile the scripts up real fast, and hitting that time limit happens a lot - specialy if some windows/antivirus/etc function kicks in while it is going on, and steals 2 minutes from it
6) not sure if possible - but a "quick compile" setting
it would stop before ferivy and say if good or bad
what this does is use the cache and try compiling only new or changed scripts in
this would be usefull for quick script checking to see if any "syntax" errors, etc
but can not be used "live" because was not a full compiling, and other parts may not interact fully with it, until full compiling
thanks fro looking at these,
hope you do not laugh to hard at them
and maybe use 1 or 2 of them