With Cheffe's decision to stop updating EasyUO, where does that leave us as a community?

From my standpoint, I think this site has grown to be much more than just EasyUO.  Sure that's what we all originally came here to do.  I needed a place where I could distribute ScriptUO(the program) and we all needed a different place to chat about things that were and WERE NOT about EasyUO.  

We've allowed for discussion about the darker parts of UO automation and also pushed different projects such as Stealth.  For me personally, I've had a love/hate relationship with EasyUO for a long time now.  I love the fact that it's just so darn easy to implement things.  My hate comes from the fact that it's so slow and we are stuck at the mercy of one developer and his mood on any specific day.  I completely appreciate Cheffe and his efforts all these years, but perhaps it is time to change.  

I've been messing with Stealth for quite a while now and I have to say that we certainly do have a viable alternative finally.  There have been lots of project that have come and go, but because EasyUO has been around so long, there really hasn't been much of a reason to push any of the other projects.  So without a user base, the developers seem to just fade away.  However with Stealth, they seem to have developed a pretty robust core that doesn't seem to require the same kind of maintenance as EasyUO does.  I've done some pretty interesting things with it from the C# perspective, but really the only way to appreciate it is from doing development in Delphi.

So anyway, Cheffe might be willing to throw in the towel but I'm not ready to do so yet.  I still love this game (and this community) but will always need a way to make my character wiggle while I'm off hiking.  So for me, it's time to just say goodbye to my EasyUO support and finally embrace Stealth or even try to contribute with UOMachine.  There's lots of possibilities out there, but one thing about this site, we've always tried to keep an open mind with regard to the various tools available.  Hopefully with losing EasyUO, one of these other projects will finally get the traction it needs to become a worthy successor.

This topic has been moved to RebirthUO.

http://www.scriptuo.com/index.php?topic=12772.0

I was so happy to have bought this car.  I bought it used on Ebay with only 14K miles on it and have owned it for almost 5 years now.  This has been the 1st car I truly LOVED.  Having visited Germany on many occasions and rented turbo diesels, I loved the combination of the diesel engine and standard transmission.  So I wanted to have that same experience here in the states.

I personally couldn't care less about auto emissions, but I bought the car knowing I'd get stellar gas mileage (which is no joke!) and extraordinary torque.  The car is absolutely amazing to drive.  But these promises were baked into my understanding that the car I'd buy would be able to easily pass VERY strict California emissions compliance.

Then the LIES surface.

After selling these cars for years based upon faulty engineering, software coverups, and corporate arrogance, we TDI owners are now left with cars (in California especially) that can never be legally registered because they will never pass emissions mandates of CARB.  There are fixes being proposed, but frankly none will actually solve the problem without impacting mileage, performance and upholding the promises that were originally made and have been promoted since 2009.

I have never been so shocked by the level of corporate deception than I have by what Volkswagon has done.  I can accept a mistake in data or a faulty mechanical part, but when it comes down to deliberate and deceitful lies, this can never be justified.  How long did they think they could get away with lies of this scale?  How arrogant can a company be to allow something like this to propagate?  Finally, having been exposed to the corporate work ethics of many German companies like I have, I'm even more mystified that this could happen.  I expected much more from my German friends; what Volkswagen allowed to happen is truly capitalism at its worst (and this is coming from someone that appreciates capitalism).

At this point, I don't even trust VW to "fix" the problem.  Since they are so interested in their bottom line, it would make more sense from their perspective to sabotage my car to get it off the road, and how better to do that than by introducing a destructive patch to my ECU.  But they wouldn't do that?  Would they?  Now I'm not so sure.  It sounds pretty conspiratorial to propose that.  However, it sounds just as conspiratorial to propose that a company would try to cheat the world for years because they couldn't live up to their promises, so they decided to cheat and deceive to cover it up.

VW got caught.  But then I started to wonder, how many others are doing similar things.  We'll see.

Note: this is a working blog as I try and figure out my woes.

So I have been slowing upgrading my systems across the house to Windows 10.  I first started by upgrading my Windows 8.1 box because 8.1 was so pathetically bad.  From there I was able to make sure most of the things I normally do work OK.  So after that I decided to try a Windows 7 computer that I do my bill paying on.  That computer upgraded easily as well.  Feeling frisky, I felt the next possible candidate was my older work laptop that was also Windows 7.  This was a bit harder because it was behind its patching schedule.  So I patched up and was able to force the update to start.  Finally this computer also worked well.  My last success was my latest laptop (Dell Inspiron 13 7000).  This came with 8.1, so I upgraded to a 500GB SSD and reinstalled the OS to upgrade.  No problems here as well.

So with the success so far, I decided it was time to give my main rig a try.  Because I would cry crocidile tears if it were do die, I decided to try it first on an image of my system drive.  However, this system has quirks.

1) I have split the Programs File installations over 2 drives
2) I have relocated the C:\Users directory onto a RAID0 array external from the boot SSD
3) I haven't patched for a while.

So any one of these issues has caused MAJOR headaches.  So far the problems have been:

1) Impossible to get Windows 7 recovery to acknowledge the cloned system drive
2) Patching Windows 7 all the way fails without solution (need errrors)
3) Impossible to get Windows 7 image to boot after cloning
4) Attempts have been made to upgrade to Windows 10, but always fail with an OS revert back to Windows 7.

So far I have successfully:
1) Gotten the cloned image to boot (from Win10 DVD - CMD prompt - active partition - DISKPART - bootrec /fixboot (cloned with EaseUS) (Win7 boot DVD doesn't recognize partition)
2) Redirected the /Users directory back to C: (needed to enable administrator account - "net user administrator /active:yes"
3) Cleaned system with CCleaner
4) Attempted to fix system with "sfc /scannow"
5) Attempted Windows 10 upgrade using Windows Update
6) Attempted Window 10 upgrade using downloaded DVD + patches

I have to go through the logs carefully (there are ALOT!) but this system still doesn't update.  I'll keep this post updated with information.  Be interested to see how people are faring with the powergaming rigs and upgrades to Windows 10.

In order to get to the point I have, you can only imagine the number of iterations of installations, and retrying by tweaking parameters.  Things like giving up on the Win7 boot disk when I found the Win10 disk actually worked instead for disk maintenance, unplugging RAID drive before boot otherwise the system "clone" wouldn't boot, downloading over and over and over again, installing up to 99% only to revert back to Win7 because of some unknown failure.  This process has significantly slowed down now that I'm making changes to the non-SSD clone.  Bleah.

Thank you Microsoft for the reaffirmation that you waste my time more than any other company!

Here's an album of my pictures I collected this year at ComicCon.   Enjoy!

https://goo.gl/photos/voX1DiPbT59PmYT18

So we're looking to accumulate information regarding the new dungeons.  Since I haven't played forever, and probably really don't have the gear to be able to handle the new changes, what are some of the interesting things you've found out about Shame or Wrong?  High points, good items, special items, etc.  I'll do web searches too, but I did want to get people's input regarding what they like (and what they don't).

;=================================================================
; Script Name: TrailMyx's Skill Monitor
; Author: TrailMyx
; Version: 1
; Shard OSI / FS: OSI / FS OK
; Revision Date: 9/29/2007
; Purpose: Adjust %skill with skll value you'd like to monitor.  Watch the Gain and estimated time to max (%target_skill)
; Globals:
; Special Thanks:
;
;=================================================================



Yet another one of my silly helper scripts I use all the time.  When I'm building a skill, I just change the %skill value and the %target_skill value and run.  One nice thing is the 3rd number which give an estimate on the time needed to complete the value raising to  %target_skill value.  This is a total swag at lower values, but tightens up to actual time the closer you get to the target value.  

The %skill value follows the 4 character reperesentation of skill as posted on EasyUO.com:
http://wiki.easyuo.com/index.php?title=ChooseSkill

;=================================================================
; Script Name: TrailMyx's Magery trainer
; Author: TrailMyx
; Version: 1
; Shard OSI / FS: OSI / FS OK
; Revision Date: 9/29/2007
; Purpose: Trains magery. Use a mage weapon!  Gives a guess for how long to completion
; Globals:
; Special Thanks:
;
;=================================================================

This script simply builds magery.  It requires you to have an LRC suit.  Also you'll need to set your training target by setting the %target_skill variable.

This script takes into consideration whatever mage weapon you have, just be sure to equip it.  Should be a spell channeling mage weapon for the script to work correctly with it.

It also does a rough guesstimate on the time to completion.  This is a linear extrapolation, so it's not even close.