Project Source 1.4 - Support(Hiatus for a bit)

Seek me out via CLANHELP PS or via the DISCORD

Message me in Aetolia (messages get redirected to my email) if you can't get ahold of the system. It's still being updated and the update is taking a long time, but it's coming! If you want to be part of the team, that'd be great. I need coders! Message me!

Post edited by Aoi on February 1

6

Comments

Thank you sir for all of your hard work on this. As someone returning going, "Wow this web client is unwieldy, unuseful, and has a tendancy to make it so my space bar turns into an attack and I have no idea of knowing when it'll do that and if I accidentally press tab I'll apparently target something and then BAM, I'm attacking orphans in Shallam." Of course this is entirely fictitious, save the fact that tab does change your target and the space bar will randomly turn into "KILL".

First and foremost, this step makes NO SENSE:"9.) Now that you have a new profile, locate your profile directory. It should be at: C:\Users\_____\.config\mudlet\profiles\ '. Where '_____' is your computer usename/profile name. Once you find it, you will want to move that 'ps' folder to the folder of the profile you just created. If you used my suggestion, the folder will be called 'Source02272017(or whatever date you made it)'."

- What is this 'ps' folder? Where do I find it? When was it made? I'm very confused.

Second:You may want to include a step where you enable GMCP when you're in the settings page. A fresh install of Mudlet does not come with GMCP enabled, and it will yell at you that you need GMCP enabled for the system to work. In all of my sheer idiocy I was able to figure it out, but as either a time saver or a kinder gesture to people who have no idea what GMCP is and how to enable it it could be a good subsection to add while we're clicking things in settings.

Third:How do I wield a fishing pole? Pausing my system doesn't help. It demands to know where my weaponbelt is, and I don't have one.

I'd argue making those optional, because I still use Mudlet 2.1. (Mudlet 3.0 won't scale down from my 4k TV to my 1080p monitor.) That said, I may just be a fringe case that doesn't really require extra effort to support :P

I seem to have a problem where the system is constantly trying to stuff a pipe full of elm, which apparently doesn't exist anymore. The scripts seem to recognize that 'willow' is the replacement, and upon filling a pipe with willow, tries to do so again over and over and over. Even after having already filled the pipe.

Essentially it is trying to 'cout elm' and put it in the pipe, takes out willow, and tries to put it there instead. I would imagine it has to do with being unable to find elm, and so some variable is not being triggered.

Not being the best at coding, I am not sure what I need to alter in order to fix this.

My god.. spent the past hour trying to find out what was wrong, and messing with the setting pipes.. Turns out.. Setting elm off.. I thought I had tried that too already. x0x well.. anyhow.. It at least stopped the spam.. xD