1.9.2 "My Top / Main" Content Suggestions.

Published by Aubarino on
Status
Resolved
Issue description

Hello,
I am a indie game developer and a general veteran at visual coding and logical thinking.

I am requesting possible content you could add to 1.9.2 or above, preferably sooner..
 

 

All requests in this list are sensible / should not be that hard to create.

Here is my request list, Please refer to the numbers when commenting so its easier.
If one is hard / already accepted, please note that, tell me and then read the rest, please don't reject this entire list.

  1. Add a set Shader Effect block with a drop down that refers to inbuilt shader effects from the "Super Secret Settings" minecraft demo. "as seen in recent spectator gamemode reusage."  with a ( true - false ) insert at the end, kind of like your Allow Flying block. (could be used with procedures used with potions or entity based procedures in the player tab)
  2. Add support for a slab block preset.
  3. Add support for model replacment for parts of a block preset, such as a CUSTOM preset block that would have a new page at the end appear that would have options to select a premade connective preset; model - texture drop downs for each normal model used in *for instance "stairs" and perhaps an ability to create a entily new connected model.
  4. Add new folder creation support (non file overwrite) so Mcreator does not delete new folders created inside the "src" folder of Mcreator, so other mods that have other mod support with strange other functions can be optimized to be used with Mcreator made mods, for instance "better achievements" "quests" "advanced obj rendering helper mods" and alike. "within reason"
  5. *NOTE FOR 4. also add a new button on the top right to allow for (repair) that would rebuild everything of a selected asset, unlock code or reset a entire folder, to allow for ANTI CORRUPTION
  6. Add structure fire based sensory support, so you can use a structure file executed in a certain X -  Y - Z  to detect a complicated portal frame, large custom multi block machine, area of empty space and more.
  7. Add test_for style functions to allow for the ingame test_for command to output a True - False signal in a procedure! ( block can be executed at X - Y - Z ... )
  8. Add the ability to replace a (selected texture) a block is using with another texture, for instance "i create a model in blockbench that uses more then one texture, and then make Mcreator select the 2nd texture and set it to something else, like a custom item frame" Also add texture detection for block models and alike so multi texture models will work. "can also be used for animated fire on a demon entity while the body is one texture and etc..." ( perhaps also make entity / item variations )
  9. *NOTE FOR 8. Add the ability to snag the texture id / filename of a item / block and then output as a string value, can then be used with *8. to allow for custom item frame style blocks, displayable chests and more! "would be semi simple to setup code wise and would DESTROY a big limitation of Mcreator"
  10. *TAKE INTO ACCOUNT *3. and *8. - Add a function for setting the model of a block "perhaps as a temp instance of that block that is customized via some sort of NBT data change or temp added block saved via map??? idk"
    that allows you to set the model of a block to any other block supported model, can also have a string input option?
  11. *SAME AS *NOTE FOR 8. [9.] BUT FOR *10. -  Add a function to get the Minecraft, Other Mod or Mcreator model from any item / block / perhaps entity? and output it via a string value that could possibly be used for *10. Or entity / item variations with added settings according to what is needed via your expert opinion (Mcreator devs) ;) .
  12. Add some kind of Custom Particle creation ability. Whatever you do is fine by me lmao.. it can be a fake particle via a entity with a lot of background scripting, a particle simulation, rendering edit or other... if it works, good enough. "i know how hard it is to create custom particles via forge being horrible with custom particle effects, gg"
  13. *POSSIBLE ADDED NOTE FOR *1. - Add a new ability to create a shader effect, via simply changing some random values in the "Super Secret Settings" shader effect presets, set to things like little hue changes and etc..
  14. *POSSIBLE FEATURE TIED TO *9. Add the ability to "temp?" download the skin of a player and then output that as a string value, via inserting the entity display name of a player into the input slot and the output being a string value that can possibly be used with *8. ( could do some really cool things )
  15. Add block direction sensing / Most likely already suggested by someone else. add it already lol.... it should not be that hard to do... and there is HIGH demand. 
  16. Add the ability to sense the relative direction of a player in X - Y - Z + 1 block in direction, similar to the F3 Overlay ( facing block ) value... if anything... just snag that value and allow for us to sense it lmao.
  17. *IDEA RELATED TO *16. - Allow us to detect a string value from the output of any value in the F3 menu. "useful in general!"
  18. Add the ability to display custom block / player NBT data values as text labels in the GUI of a block / ability to display NBT data of (only) the player in a gui not bound to a block.
  19. *LATE NOTE RELATED TO *2. Add a new drop down when selected that would allow you to pick the block that the 2 slabs would change into when combined together.
  20. Add vision detection of entities, with a drop down for entities.. that would output a true - false if that entity is viewing another entity / if the player is rendering that entity within its screen. " could be very cool for reality breaking hallways, monsters, nighmare mods and more! "
  21. Fix java based model import functionality around importing models that contain mirrored textures "i have had problems aka horrible crashes and errors. contact me for more info if you want.."
  22. add most normal procedure functions to the AI editor! so you can toggle / edit the AI of a entity LIVE via NBT, the entity name and more. via turning AI functions on and off with if statements or just inputting a value into a value slot of a AI attribute via a global value or custom NBT entity values.
     

There is a lot i have missed in this, but i will try to keep it short.

These are my current TOP suggestions of content you could add.
Looking forward to a "descriptive" reply.. if possible

<3

 

Also, i will attach some screenshots of interesting things i have managed to do in the current build of Mcreator. :P
 

Issue comments

Also, What do i need to do, to apply to join the Mcreator developer team? ;) (separate question.)
I will so whatever it takes..

I see alot of potential in your tool and wish to help make it better as best as i can!
Unlike other platforms / programs i have used, your actually responsive!
So i was thinking i may have atleast a tiny chance.. of even talking to anyone here about the possibility.

*NOTE - I can pickup any language semi easily and if you admit me onto your developer team i will do whatever it takes to learn whatever language! ...
Infact now that i think about it... i should probably actually learn java instead of just re'editing the java of the output of your templates in mild ways and stuff like that XD
lol.

These are some nice ideas, but such idea lists belong to forums more than here (check the instructions on the top of the issue tracker form). We then pick the ideas that are possible in the short term to be realized and these belong on the issue tracker. This way we keep the tracker clean and readable after issues are fixed, more are added.

Thank you for your interest in being a developer! :) At this point, we do not accept new developers unfortunately as we have a closed system for development that is local to our headquarters. If we consider expanding this in the future, we will let you know ;)

Add the ability to display custom block / player NBT data values as text labels in the GUI of a block / ability to display NBT data of (only) the player in a gui not bound to a block.

This one can be done by copying NBT value in tick event in a global variable and displaying this variable in a GUI.

That is not possible in some contexts,

For instance "i make a custom furnace using NBT data and a GUI, it sets the fuel display client side variable to the fuel NBT data contstantly so it can display the fuel, but if you have more then one burning, it glitches out.
You cant set a variable constantly via only when your in a GUI, this would require a procedure event to trigger a procedure for this action every tick of the GUI usage per client, this is not possible currently."

Understand the problem?
This feature is needed for more complecated GUI based functions.
I also recommend adding the ability to add a animated texture that's frame is controlled via block NBT or some kind of temp GUI variable.  so we can create detailed flame effects like in normal furnaces and brewing stands.

I made a post in the past on a forum,
But i got a message to post it as a issue tracker post or vote on each individual post that other people have posted in the issue tracker already,
I could not find sources for most of my idea's so i created a issue tracker post for all of them added together in a list.

So what do i do?
Issue tracker? - go to forums :|
Forums? - go to issue tracker...

Can you just take into account this suggestions independently and then
Think about them as they are, as a idea or concept for future potential.. 

<3

 

Also thanks for the update on that info about your new developer status.
Feel free to update me on any new info about the ability to join your developer team or help with Mcreator in any way i can.

 

I see what you mean with GUIs and NBT tags. I will consider improving this in the future.

So what do i do?
Issue tracker? - go to forums :|
Forums? - go to issue tracker...

I think the rules on top of the issue tracker are quite clear:

Make sure to post only one feature request or bug report in each ticket, so each separate item can be tracked by our issue tracking system. Issues with multiple requests will be removed. The tracker is not a place for large lists of feature requests. Such lists belong to Feature requests and ideas for MCreator forum section and we will pick most requested features from there.

As I said before:

Idea lists belong to forums more than here (check the instructions on the top of the issue tracker form). We then pick the ideas that are possible in the short term to be realized and these belong on the issue tracker. This way we keep the tracker clean and readable after issues are fixed, more are added.

Only this way we can keep tracker organized, otherwise, I would drown in issues and the tracker would lose its point. Thank you for understanding :)