Spring RTS Engine

I've finally figured out how to shut down non-mod Widgets (I think) and just load game Widgets, in an easy-to-install package for game developers.

This is obviously a big step up in security from WhiteList, and will probably not be suitable for everybody's project (in which case, use WhiteList, or reverse its logic to make it a blacklist application, and remove the part where it shuts down the Widget Selector- sometimes all you'd want is to shut certain things off by default, and obviously this is a lot more rigid- if it's not in you mod/game, it just doesn't load at all).

This must be added as a dependency to your mod / game in order to work. I.E., go into modinfo.tdf, and add it in there. If somebody is clueless and wants an example, lemme know, it's pretty straightforward imo.

100% of the credit for this code goes to Lurker, Trepan and Regret. This version uses Regret's suggested changes, which were based on Lurker's comments in the White List thread and Trepan's original source. I just typed some stuff and copy-pasted.

Please let me know if my fumble-fingered programming broke anything really permanently. Thus far, it seems to be passing all tests- my Widgets load, nothing else does. And it finally works with World Builder!

So, the next step is deciding on a list of non-cheating-but-useful Widgets that may be run with my game, and throwing them into an archive, or into World Builder (might be handy to just make a compilation of stuff that's useful, isn't a cheat, and doesn't break UIs).

Here's the file.

How to force loading of only mod widgets.

1) Place a file named LockLuaUI.txt into gamedata

2) Copy widget.lua into your mods LuaUI folder, delete the segment that has a comment "-- stuff the raw widgets into unsortedWidgets"

3) Copy main.lua into your mods LuaUI folder
replace the line "include("widgets.lua",nil,VFS.ZIP_ONLY) -- the widget handler"
with "loadstring(VFS.LoadFile(LUAUI_DIRNAME .. 'widgets.lua', VFS.ZIP_ONLY))()"

4) Create a luaui.lua directly in your mod folder
luaui.lua contents:

Lemme test that, it would be less messy than this is, and probably vastly easier to maintain going forward.

[EDIT]Step 3 doesn't apply to current widgets.lua, but I'll try the replacement.[/EDIT]

Argh wrote:[EDIT]Step 3 doesn't apply to current widgets.lua, but I'll try the replacement.[/EDIT]

Step 3 is about editing main.lua, not widgets.lua.

Ok, it works. Archive has been updated, and isn't full of irrelevant code. I'm keeping it as an add-on module, like World Builder, so that I can have mutator versions of P.U.R.E. that allow Widgets to operate, etc., so that everybody's happy. If people want to play with stuff that may be a cheat, that's great, I'm actually ok with that, so long as everybody knows that that's what they're doing... but they can run "pure mode" for competitive play, etc.

Do we actually need this line? I mean... nobody is ever going to run P.U.R.E. with 0.74b3...
[EDIT]No, we don't. I guess that was left in for older Widget support. Removed it in my version, I'll update the archive.[/EDIT]

I can't even get 2 (per)cents of credit for flat-out telling you to do this in your whitelist widget thread?

Absolutely. My fault, fixed.

On the bright side, basic no longer has to try to do this himself as I, distracted by other programs, don't quite help in pm.

This is excellent. Would be nice if via modrules we could just tell the mod to override the user lua. Why it is the other way around is stupid.

Oh btw, to anyone who uses this, extract it and put it in an sd7 Using 7Zip. Windows IE likes to rename files. Additionally, calling this "No Cheat" is silly. It has a lot more uses.

Yeah, it would probably be more appropriate to call it "GameOnlyWidgets" or something.