[1] - Insert file as a child of Workspace, ServerScriptService, or any location seen by the server. [2] - Enable all options within game settings [3] - Move admin tools within the Customs → Tools
Nexus Dynamics is licensed under the Mozilla Public License v2.0.
This system is available for use at no cost. However, proper credits to the original source is required—such as linking to the DevForum post or the official YouTube video. Additionally, any substantial modifications to the source must be open-sourced, in compliance with the licensing terms.
Add a version that is not loaded by a require(AssetID). I mean the actual module itself so the developer (Consumer) has to put everything in its own place.
That way we can take advantage of that and customize it.
Also it will be easier for you to get bug reports since can inspect components in studio mode.
best admin panel ever, its like cmdr and most modern admin panels combined but with 10x more features. highly recommend this. Few things I think should be changed about this:
From what I could tell, the UI itself is constructed with 11k UI elements, everytime I move the ScreenGui it takes time. The entire panel is pre-designed unlike typical panels.
When we decide to add Themes, I do plan to reduce the number with script generating for things like UIStrokes, UICorners, etc.
Could i suggest loading in parts of UI elements as n needed?
For example:
When you press the button at the top, it opens a circular/radial menu. At this time only open the necessary UI elements and events for functionality, nothing else.
Once any of the buttons are interacted with, load said page but unload any others that are not being used.
It’s an extreme optimization for a UI, but with 11k elements it’s definitely looking like it’s necessary.
I went in with the usual skepticism on admin systems, but the attention to a beautiful and useful interface is simply put: impressive
I question the value of this really fleshed-out terrain & environment tooling, given that there’s no import/export feature. All changes would be temporary and lost on server closure. Being able to save changes and load them later on would open up a lot of use cases for these great tools.
It’s a great first start however. I haven’t read the code yet but as you mentioned having 11 thousand UI elements, are you considering implementing a framework like Fusion?
It would make your life a lot easier, especially with reusing components and theming. Would recommend to check it out!
I’ve tried to find a good optimized solution to import/export terrain but haven’t found one myself yet. Currently it’s just temporary for fun and experimenting with your maps like concept art.
I’ve not heard of Fusion and will give it a look, thanks for suggesting this framework!
I appreciate the recommendation, but NeoHotbar’s codebase is pretty messy and outdated. If you’re looking for a quality reference, I’d rather point you to this:
