Search results

I have to say, I definitely think the thread moved. I just wanted a one-click "Summon Tome Items", like it makes pies in the background. I think it'd be a common enough request that it's reasonable to put it in for people who aren't making kingLiberated scripts, etc.

Pretty much as the title sounds. Beat the NS, free the king, and you get to re-summon tome items. It would be good to have that reminder.

I was going to, but the data files are used by the PHP element of the script as well, so they need to be stored in a place that the site can easily access them.

Oops, forgot to actually commit the changes. That should work now.

Make a lot of sense. I can do that and keep it all in one SF repo.

*Zing*

Excellent! In the interim, I'll make some sort of temporary thread linking all of those scripts that have moved to SVN so that we'll have a clear index of larger scripts, etc.

You make a fair point - I hadn't considered that. You'd recommend that rather than have: A https://svn.code.sf.net/p/bumcheekascend/code/bUMRATS/relay/ocean.ash A https://svn.code.sf.net/p/bumcheekascend/code/bUMRATS/relay/topmenu.ash A...

With the update to mafia now allowing SVNs, we can update all our relay scripts at once, and I think it'd be a great idea to have a single SVN holding updates to each relay script. Kind of like what I saw bUMRATS as being, but without it turning into one horrific and unmanageable file. I'm...

Maybe in the last 17 pages this was mentioned, but is it the intention for us "scripters" to be able to register our scripts with some sort of central database or data file, and have the SVNs registered with mafia (in some way), so there's some sort of GUI for "major" scripts in some way? That...

Like I just checked out bumcheekascend and went to immediately run it, but I had to click "Scripts->Refresh Menu". It's not a massive issue, but might confuse a person new to mafia.

One very small recommendation: probably best to refresh the list of scripts after a checkout command.

That's a pretty reasonable solution. So include a dependancies.txt file with a something like a comma separated file of: script1name, http://svn.com/code/repo1 stript2name, http://svn.com/code/repo2 etc.

How would one suggest we declare dependancies?

I'm going to update the folders to account for the new SVN structure.

Wow, this is amazing! Thanks, roippi, I'm sure this will be ridiculously helpful to many scripters and end users. I'll update the bumcheekascend SVN repo immediately. If anyone has a script that they want to use and open up to contributions from others, then feel free to make a subfolder in...

To be honest, I don't think having the same script names will be a massive problem. Presumably just scripters will have to make sure not to use existing names.

The reason the various projects are hosted in an admittedly entirely-ridiculous way is because the vast majority of people would'nt update via SVN so we could use the SVN to update them, and then spin a new release via a copy-paste into the forum thread of a separate version. It wasn't a great...

Would you recommend that we split our scripts so that they're in separate repositories. For example I was just planning on having all my scripts under my single bumcheekascend sourceforge page, in separate subfolders as we noted in the previous page, but then it seems that it would be tricky...

Ah, I didn't see that there. Either way, I don't think it's an issue based on the above posts.