limits?

Hey Nick or anyone else interested, I currently have just under 300 aliases (I kid you not), 30 variables, over 100 triggers and huge amounts of vbs script using vers 3.26

The mud I operate on is built to encourage groups more than solo gameplay, and I'm looking at writing a script that members in a group can type a command so I start taking stats for them for the duration of the group. The stats would be in the form of how many blinds, webs, trips, bashes, chops, decapitations and a few other things that each player does in a group, and then keeps running totals for each player of each action so they can grouptell 'score' at anytime to get their group stats. They could also type 'scores' and ideally the script would then assign points for different actions so you can then get a total point score for each group member and see who's doing the most work / damage etc rated top to bottom.

The point of it is not just an excuse to spam the crap out of the group, but to stop people from botting and get them more into participating in the group rather than just kicking back and sponging the exp points. Possibly awarding small equipment prizes at the end even.

This would be a major effort to do I think, but before I even start, I want to know if there is any limit as to the amount of variables triggers and aliases I can have on vers 3.26, and if anyone has any brilliant suggestions how to do this other than the obvious of having a huge amount of variables.

cheers.

I am unaware of any limits to the amount of variables (or other things) in Mushclient. Can only say that I currently have 438 triggers, 222 aliases, around 30-40 variables, a 57k vbs script and have no problems with all those - not even when all my triggers start firing all at once (which does happen in the world I play at:)

The only advice with variables I can give you is: use script variables instead of Mushclient internal ones. Don't know if this will be more efficient, but it will save you a lot of hassle when you need to check the spelling of the variable and such so. Just make sure you declare all your vbs variables, that you want to be shared throughout the script, outside of any subs or functions. Then you can use a text file to save the state of those variables (which would be Score in your case I guess). Or perhaps have a few mc variables to store the final results of calculations done by your script routines on the contents of vbs variables, though I like the idea of using a text file better if you are planning on holding week-long bashing events, with scores running throughout the entire event.

P.S. I gave up using internal mushclient variables for things other then db numbers of crucial eq items and so on. If it doesn't need to be saved between sessions it would seem wiser to do it directly in vbs, rather than clustering the list of mc variables.

There are no inbuilt limits as such. I read somewhere that there is a limit to how big VBscript scripts can be but I have not personally hit that, and in any case you could break your project up into multiple plugins if that was a problem.

You would eventually run out of memory, or things would slow down, if you had thousands of something, but for reasonable cases all should be fine.

thank you :) I vaguely remembered a thread ages ago about there being a limit on the number of variables or something, probably on an old version release, thought I'd better check. cheers.

and thanks Grateful. Fortunately the data will only be for the duration of the particular group, so internal will probably suffice, although good point about "If it doesn't need to be saved between sessions it would seem wiser to do it directly in vbs, rather than clustering the list of mc variables."

"week-long bashing events" made me grin, but in retrospect it's actually sparked a few ideas, so thanks again.