Project Source Support - Version 1.1 Update - 6 JUNE
Project Source
** UPDATED 6 JUNE**
To install, close mudlet and replace the existing source.xml
06JUN2015 V1.1 -
Click here to see change log -
Click here to download05JUN2015 v1.01 Bug Fix -- Changes to Aetolia's pathing system resulted in some unwanted doubling. This has been addressed.
31MAY2015 v1.0 Released
We're happy to be releasing v1.0 of Project Source.
- Large team of developers and testers.
- First Aid based curing for improved speed.
- Full GMCP support and tracking.
- Standardized hooks and global variables for easy expansion using modules.
- Integrated map using Aetolia's pathing system for increased speed. Favorite location system included.
- and Much More.
We will continue to refine existing systems and add new features. If you would like to be involved in Project Source, please contact a member of CLANHELP PS.
If you need support with the system, please reply here, or ask in the clan. The clan is open to anyone who would like to use, support or develop this system.
0
Comments
Installation
Click here for initial installation download
It is recommended that you do a clean installation of Project Source, even if you currently use Tripwire on your first installation. If you are updating, see the top post of this thread.1.) In Mudlet's select a profile screen click the +New button. Name the profile whatever you wish and use Server Address: Aetolia.com Port: 23.
2.) Once you've selected your new profile, unzip the contents of the link below to the profile directory. This can be found at C:\Users\\.config\mudlet\profiles\
* We recommend dragging this folder over to the left and adding it to your Favorites tab to make navigating to this folder easier in the future for updates.
3.) In mudlet, navigate to the menu - Options|Preferences
a.) On the first panel, check the enable GMCP tick
b.) On the last panel, check the top and bottom ticks
c.) Click save
4.) Now that the files are in place, double click the profile to enter the game, however do not connect yet. At the top, go to Toolbox|Module Manager and add the Source.xml and Personal.xml file that you unzipped to your profile directory.
Set the priority of source.xml to 1 and click the sync button. Set the priority of personal.xml to 2 and click the sync button. Restart mudlet.
5.) In mudlet, navigate to Toolbox|Script Editor, on the left, in the Triggers, Alias, Scripts and Macros sections, delete the mudlet-mapper folder, it is not needed with this system.
6.) Once you are logged into Aetolia, type "setupfirstaid" without quotes. This will set your first aid up to the default settings for Project Source. This only needs to be done once. You are now ready to use the system.
Be sure to explore the 'setting' command to set all of your mount's, pipe's, syringe's etc. IDs to work with Project Source.
** New Users **
Ensure any Alias, macros or other additions you add go in the personal folder, otherwise they will be lost when updating to a newer version of Project Source.
If you come across a room that is unmapped, such as the Wings or Amulet artifact rooms, simply type MAP HERE.
** Note for Developers & Advanced Users **
If you wish to retain the settings you had in a previous installation of tripwire, simply move all files that start with tw. to the new profile folder and change the tw. at the beginning of those filenames to ps.
**Developers** All variables have been changed to the ps. prefix. If you need to convert existing personal modules, simply open the xml in an editor such as Notepad++ and use the find and replace feature to change all instances of tw. to ps. and you're good to go.
@Dragos yeah had already changed it. Also I added raiders to clan list for it to announce the foci collapse in the clan.
I am having some double outc of slices, that could be my stuff not sure and I am still checking that.
1. While trying to do leylines with TW, I had a few spots say that a destination was unknown but it'd still go ahead and take me there. However, I only got maybe five places into the LEYGO when a destination wasn't recognized and it refused to take me. I couldn't seem to skip trying to go to that location so apparently my leylining will never be able to proceed past that point. Wondering if there can be a feature for forcing travel onward or simply skipping to the next location in the list?
2. When disabling web Listening, TW announces quite the opposite in Web despite actually succeeding. (The "Listening To:" visual on the right side updates to reflect none, at least.) Also, there is a typo. This all happened yesterday so I ran another test tonight with someone else this time and the issue still occurred.
3. With gags off (I dislike being unable to see what things are doing), I've noticed that some commands I'm sending such as the one above for disabling weblistening are actually being sent to the MUD, provoking a 'That is not a valid command' response despite working. Is this intentional?
4. Apparently rebounding doesn't like to work on it's own because the pipe isn't lit. I checked the pipes under setting to see if they are assigned and they are, yet the command being sent to smoke isn't using the ID numbers anyway. Also, despite failing to smoke since the pipe isn't lit, a false positive of having smoked is being sent to TW.. triggered off the command itself rather than the success or failure. This wastes time as the defs have to catch up and correct themselves when it's noticed that there is no rebounding going up.
Abhorash says, "Ve'kahi has proved that even bastards can earn their place."
New Features:
-- Hidden Affliction tracking, the system will now track and diag hidden afflictions.
-- Semi-Automated Bashing. Simply turn bashing on, toggle SETTING AUTOBASH and enter an area. As you walk around the target will change, using the mobs specific number, and attack until it is all dead. This works off of the mob_tables, so if the area you're in isn't working, check the tables. You can post the name of the area, and all of the mobs in that area here and it will be added in next version and I will provide something to paste in to Source to make it work in the mean time.
** Ensure you have read and understand HELP AUTOMATION before using the above system.
-- Area runner, run all the rooms in an area automatically. Go to an area and type RUNSTART and RUNSTOP to stop. It will then move room to room until you have visited all rooms. (or run into something that blocks you, i'm still working on that, consider the feature a beta, it works most places) ** Will not work in instances **
** Ensure you have read and understand HELP AUTOMATION before using the above system.
-- Basic AI setup has been established inside of Source. This is still in the early stages as we continue to flesh out enemy affliction tracking. A couple basic AIs have been included as examples, though they are very old, so don't expect them to work without modification. Use ENGAGE, F1, or click the PVP button to start attacking your target with AI.
-- Changed clan_list settings. Search for clan_list for instructions on how to keep your clan alias' between updates without having to repopulate them.
-- Multiple minor bug fixes have been implemented, if you notice the system throwing errors in the error box of the system window, please let us know about them here.
*** Secret Sauce Users ***
With the new changes to the Source, SS is now deprecated and can be removed. If you notice something missing, please let @Paithan know, or move it to your personal xml.
If you have any questions, comments, bugs or feature requests, please leave a note here or join us in the Project Source (PS) clan!
1. The DEF list appeared to not be automatically resetting after a death - Defs show as applied in DEF list so none will apply when DEFUP is entered. When the Mudlet trigs are disabled with the bomb icon, DEF in game shows that there are, indeed, no defenses up. After puzzling over the issue and updating to the new release to see if it fixed, I discovered that the system is simply not unpausing itself when returning back to life after dying. Unpausing to clear defs so one can start to def back up could be triggered for efficiency, like in Entropy.
2. Deffing up gets stuck in an loop of continuous attempts if a defense fails to be applied, and will not advance to the next defs.
3. -- particularly Mindseye if you use an Allsight earring instead. Can we have an option built-in for that? I've currently got it working for me but it doesn't feel tidy.
4. Leylining mapping - Some locations still not working properly. Last release, it was 'Tiyen Indoron Inner Sanctum' that the leylining would stop on. This release it was 'Birka Mire', but I managed to add it to the ignores lost. However, I then got stuck next on "the Academy of Duiran" which the leylining refuses to ignore despite me adding it to the ignores list too.
edit: Apparently I left off part a sentence on accident! Fixed.
The mindseye thing can be fixed with SETTING MINDSEYE EARRING, or SETTING MINDSEYE MINDSEYE. It is under SETTING DEFS, iirc.
ps.settings.defs.mindseye = "allsight"
Now when the defup trigger queries the defaults for what to touch for the Mindseye tattoo, it touches Allsight instead, which is a nicely workable situation as that is my earring. The only downside is that Mindseye stays listed under current tattoo defs but it works! Hope this info helps others too.
I remember, involve me and I
learn.
-Benjamin Franklin
levitation = {
action = "hover",
balances = {"balance", "equilibrium"},
reqs = function() return ps.race and ps.race:lower() == "azudim" end,
redef = true,
Maybe not the perfect way to do it but it works.
@Isande allsight defence line is MINDSEYE that's why it shows up as a tattoo on DEF just like Ishin said but it just means your allsight is up/working
and, ps.settings.defs.mindseye = "allsight" - every since the new enchantment it seems touch earring doesn't always touch allsight it touches the earring. If the first earring ran out of allsight then it doesn't do nothing so it is better to 'touch allsight'
I remember, involve me and I
learn.
-Benjamin Franklin
Also, looks pretty good! I had to put my wrapwidth to 92, because it was cutting words off. Is that going to bork the system?
Finally, I'd be happy to offer what little I know about programming. My new "job"/"occupation" has had me start doing some programming, and now that I have a vague idea of what I'm doing I actually kind of enjoy it. Not sure how much I can contribute, but I'm pretty good at breaking things!
Hello!
I suspect that the download link for 1.1 version is still leading to 1.01 instead, as I replaced the source XML with it twice now and all it runs is 1.01 still. Typing CHANGES shows only the changelog entries for 1.0 and 1.01, and searching in settings for RUNSTART brings up nothing.
Can we get an updated link to 1.1, or perhaps a directory that includes it?
-All good, got it figured out. Was taking directions too literal this whole time and only replacing the XML as stated instead of also going in and adding it afterward under Package Manager. Once I did that, I had two copies of Source settings but the second set was 1.1 stuff so I'm on a roll now.
waterbreathing = {
action = {"outc pear;eat pear", "outc pancreas;eat pancreas"},
balances = {"herb"},
consumes = {"herb"},
reqs = function() if ps.living then return checkCache("pear") else return checkCache("pancreas") end end,
redef = true,
},
To make firstaid turn on/off make an alias like this:
if faid then faid = false send("firstaid on") cecho("\nFirstaid: on!") else send("firstaid off") cecho("\nFirstaid: off!") faid = true end
Then type "aid" to switch it on and off. I do this on my phone to stop some issues with firstaid overriding my things. You could make the cecho stuff nicer with colours I think??? Ask around.
Also try these triggers
^You close your eyes, curl up in a ball, and fall asleep.$
send("firstaid off")
send("pause")
^You open your eyes and yawn mightily.$
send("firstaid on")
send("unpause")
Abhorash says, "Ve'kahi has proved that even bastards can earn their place."
I remember, involve me and I
learn.
-Benjamin Franklin