It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Great! thanks. It can be perfect, he is the guy behind some good quality hacked modules.
avatar
Gudadantza: Great! thanks. It can be perfect, he is the guy behind some good quality hacked modules.
I think they are "French vanilla", btw, so they do use new pictures and icons, but just to the extent that the original game allowed importing them, no UASHELL needed.
avatar
Gudadantza: Great! thanks. It can be perfect, he is the guy behind some good quality hacked modules.
avatar
Leroux: I think they are "French vanilla", btw, so they do use new pictures and icons, but just to the extent that the original game allowed importing them, no UASHELL needed.
Thanks for posting this thread, Leroux! I will eventually start messing around with FRUA, so in preparation for that, I started reading your initial posts. You talk about Windows and Linux installation for UAShell, I believe. I am a Mac user. Is there any special installation for us Mac people? Thanks!

EDIT: Just saw your disclaimer in the italicized section! No experience with our beloved Macs, I see. ;-) Do you know of any other thread at the FRUA forums that may have Mac instructions for UAShell?
Post edited January 09, 2018 by sumernivek
avatar
sumernivek: EDIT: Just saw your disclaimer in the italicized section! No experience with our beloved Macs, I see. ;-) Do you know of any other thread at the FRUA forums that may have Mac instructions for UAShell?
Unfortunately I don't. I can't think of a member of the FRUA community who's using a Mac, but you could try posting your question over there on the forums and see if there's anyone who knows more about it than me.
Mac directions: copy/pasta with edits
Running Hacked designs

1. Download uashellc.zip from the UA archive and extract its contents to your main UA directory 'D&D Unlimited Adventures.app/Contents/Resources/game' (Right-click Show Package Contents on the App to browse from Finder).

1b. OPTIONAL: Code check removal (Pt. 1): If you want to permanently remove the obsolete codeword check from your legit copy of the game, also download ckit-crk.zip and extract CKIT-CRK.COM to your main UA directory 'D&D Unlimited Adventures.app/Contents/Resources/game'.

2. Edit script_alt.sh at 'D&D Unlimited Adventures.app/Contents/Resources' with a text editor. Change lines 5-6 to:
#run game
./dosbox/MacOS/DOSBox -conf "game/dosbox_ua.conf" -conf "game/dosbox_uashell.conf"
3. Make a copy of the file dosbox_ua_single.conf in the same directory, 'D&D Unlimited Adventures.app/Contents/Resources/game', and rename it to dosbox_uashell.conf. Open dosbox_uashell.conf with a text editor. Find the line that says „start“ and replace it with „CALL uashell“.

3b. OPTIONAL: Code check removal (Pt. 2): Insert a line above „CALL uashell“ and put „ckit-crk“ in it (it's very important that your config file runs ckit-crk.com before calling uashell or it won't work!). You can also remove GOG’s copy protection notice by deleting all lines from „@ECHO OFF“ to „pause“.
Rest of the directions are the same. Hold down <ALT> while launching the game to run UAShell.
You can swap the contents of script.sh & script_alt.sh to have it default to UAShell vs Standard. You can also do all this from Terminal if preferred.
Post edited January 15, 2018 by Gydion
avatar
sumernivek: Do you know of any other thread at the FRUA forums that may have Mac instructions for UAShell?
avatar
Gydion: Current Mac version is also using DOSBox. So, similar to Linux directions just different paths:

Right-click Show Package Contents on the App
Main directory is 'D&D Unlimited Adventures.app/' 'Contents/Resources/game'

Edit script_alt.sh at 'D&D Unlimited Adventures.app/Contents/Resources'

#run game
./dosbox/MacOS/DOSBox -conf "game/dosbox_ua.conf" -conf "game/dosbox_uashell.conf"
avatar
Gydion: Rest of the directions should be the same. Hold down <ALT> while launching the game to run UAShell.
You can swap script.sh & script_alt.sh around to have the default to UAShell vs Standard. You can also do this from Terminal if preferred.
Wow, thanks for the reply! I really appreciate it.

Leroux, you may want to link to this post from you initial post for future Mac people! :)
EDIT: nevermind, figured it out :)!
Post edited March 23, 2018 by 01kipper
Another question:

Does anyone know why the GOG mac version of FRUA is using DOSBox instead of the immensely superior Boxer?

I downloaded the game, installed UAShell according to Gydion and Leroux's instructions, and then moved the game folder into Boxer. I had to delete the *.conf files, but after that it worked. I've loaded up UAShell and a "Hacked" module in my Boxer version and it seems to be working fine (I only created a test character, started the game, saved my progress, then loaded my progress).

However, I don't want to get too involved in a game if I'm going to run into problems down the road. So is there any reason why I should not use Boxer?
avatar
01kipper: Does anyone know why the GOG mac version of FRUA is using DOSBox instead of the immensely superior Boxer?
I don't know about immensely superior Boxer. GOG's DOSBox setup seems all nice & pretty. Earlier GOG installer, dd_unlimited_adventures_2.0.0.1.dmg, used Boxer until they switched to DOSBox. Could be related to this, but I'm not sure. I don't recall a changelog about it.
Post edited March 26, 2018 by Gydion
avatar
Gydion: I don't know about immensely superior Boxer. GOG's DOSBox setup seems all nice & pretty. Earlier GOG installer, dd_unlimited_adventures_2.0.0.1.dmg, used Boxer until they switched to DOSBox. Could be related to this, but I'm not sure. I don't recall a changelog about it.
Thanks for the reply. I just tried creating a new design to test my Boxer version, and it seemed to work OK (no crashing). I've been playing the game for short while now (hacked module) with Boxer and I haven't had any problems yet, but I still haven't done much. I'll report back here if I have any major problems, for future users.

I guess "immensely superior" is subjective, I just mean Boxer is superior for me personally. I prefer Boxer because of the ability to easily resize the play window at will, free the mouse from the play window, simulate a numeric keypad, etc. (Or at least if DOSBox has these features they are sufficiently hidden that I am unaware of them, Boxer has them right at the front and easy to use).
Post edited March 26, 2018 by 01kipper
I´ve ever had a doubt, maybe not important, but:

Once a hacked module is applied from uashell, is convenient running that hacked module through uashell frontend every time or is it safe running it from the vanilla UA?
I make the question because I see that every time uashell does run, the last applied module is "applied" again and I do not know if this makes something wrong with the default installation.
I also make the question because I was testing the Ray module Temple of elemental evil and the first time I applied it the fonts were green but now It turned to brown fonts and I do not know if something can have been messed up or if it is messed up at all :)

Greetings

EDIT

And one more question:

What is the most convenient way to change modules in uashell, restoring default and then applying the new module or is it safe applying the new module over the last one directly. Does it matter?

Greetings
Post edited April 24, 2018 by Gudadantza
avatar
Gudadantza:
Hey there, sorry for the late reply! I don't check this forum or this thread that often or at all anymore, I only found your post by coincidence. (If anyone would like to draw my attention to questions like these, quoting my posts or sending me a PM will work much better, as GOG will alert me about it.)

Anyway, about your questions:

Once you have applied a design with UAShell, you don't need to run UAShell anymore until you want to apply another one. But you *can* keep running it through UAShell without causing harm, too. I usually do it this way, because I consider it a bit safer. How you can mess up things is if you've applied a design with UAShell and then switch designs in-game, without UAShell (IIRC, there's an option for that in the start menu - best leave it alone!).

The thing is, if you mess things up while running the design from UAShell, at best UAShell will store the changes in the design, but never in your default vanilla installation. That means once you apply a different design, the game should go back to normal. On the other hand, if you mess things up while running vanilla UA after applying a design with UAShell, the changes might get stored in your default vanilla installation, I think. UAShell always restores everything back to the vanilla installation before applying another hacked design, but it might mistake the new messed up vanilla installation for the default one and install the new design on top of it. In that case you might be better off to re-install the whole game and UAShell. So IMO it's safer to always use UAShell, just in case, even if it's not strictly necessary.

And UAShell will automatically restore the default installation for you before it applies a new design, so you can quickly switch between designs just by "applying" them, no need for manual restores.
avatar
Gudadantza:
avatar
Leroux: Hey there, sorry for the late reply! I don't check this forum or this thread that often or at all anymore, I only found your post by coincidence. (If anyone would like to draw my attention to questions like these, quoting my posts or sending me a PM will work much better, as GOG will alert me about it.)

Anyway, about your questions:

Once you have applied a design with UAShell, you don't need to run UAShell anymore until you want to apply another one. But you *can* keep running it through UAShell without causing harm, too. I usually do it this way, because I consider it a bit safer. How you can mess up things is if you've applied a design with UAShell and then switch designs in-game, without UAShell (IIRC, there's an option for that in the start menu - best leave it alone!).

The thing is, if you mess things up while running the design from UAShell, at best UAShell will store the changes in the design, but never in your default vanilla installation. That means once you apply a different design, the game should go back to normal. On the other hand, if you mess things up while running vanilla UA after applying a design with UAShell, the changes might get stored in your default vanilla installation, I think. UAShell always restores everything back to the vanilla installation before applying another hacked design, but it might mistake the new messed up vanilla installation for the default one and install the new design on top of it. In that case you might be better off to re-install the whole game and UAShell. So IMO it's safer to always use UAShell, just in case, even if it's not strictly necessary.

And UAShell will automatically restore the default installation for you before it applies a new design, so you can quickly switch between designs just by "applying" them, no need for manual restores.
Hi, thanks for the detailed answers. I had forgotten this post as well... :)

So, as a resume, It Is completely correct switch designs. It is not needed to restore default manually and then apply the other design.

I See that is harder messing things than I considered before... :)

Greetings
Having a problem with the game crashing anytime I select "CREATE A NEW DESIGN." After naming the module and hitting OK, the entire game crashes to the desktop. I've tried loading Skull Crag or the Tutorial modules and THEN creating a new one but that doesn't stop the whole thing from crashing.

Anyone else had this problem as well?
avatar
rangereric18: Having a problem with the game crashing anytime I select "CREATE A NEW DESIGN." After naming the module and hitting OK, the entire game crashes to the desktop. I've tried loading Skull Crag or the Tutorial modules and THEN creating a new one but that doesn't stop the whole thing from crashing.

Anyone else had this problem as well?
I don't think that ever happened to me, but I haven't tinkered with the editor in a long time, and never with the GOG version, I believe. I'd suggest creating an individual question thread for your issue, so that your question is more exposed than here in the sticky, and/or contacting support about it. An important information for whoever might be able to help you is whether you use UASHELL or not.